Microsoft Fabric data for business decisions
We connect and prepare data so your teams can use Microsoft Fabric for financial, workforce and operational reviews. Databasin supplies the source connections and workflow tools. Our team builds the measures, implements the recurring work and helps people use the result, with support available after launch.
Data your Fabric teams can use
Design, Build, Run
We take responsibility for the work from defining the outcome through implementation and ongoing support.
Design
We define the outcome, current processes and expected return with your stakeholders. A working example shows how Databasin would answer your business questions.
Build
We get your first use case live in 90 days. Communication, rollout, training and success measurement are included in the work.
Run
Choose the help you need after launch. We can run the solution for you, provide monthly support hours or stay on call.
Results from customer work
- 20+ systems unifiedDatabasin brought WashU Medicine's financial data together.
- Infrastructure costs at 1/3 of the traditional approachWashU Medicine's result from changing its data infrastructure.
18%
Higher grant proposal success
Measured at a research institution working with Databasin.
“What used to take weeks or sometimes even months now happens in minutes.”
Tools for the running workflow
Fabric destination
Use Fabric as the destination for the source records your review needs.
Source mappings
Apply local clinical rules and operational mappings when preparing the source records.
Historical values
Use Workday effective dates to select values for the period being reviewed.
Pipeline schedules
Arrange regular preparation around the time people need to use the data.
Run inspection
Find a failed table in the run record and inspect its logs.
Connection access
Establish the permissions and identity required by the chosen Fabric connection.
Example: Business reviews with Fabric
Financial performance
Examine a department's financial variance with its workforce measures, using records prepared for the same reporting period.
Research questions
Select Epic encounters for a research question, then examine the prepared cohort and the source records behind it.
Operational checks
Schedule a check after data preparation and send the resulting explanation and query evidence to the people using it.
What happens next
We would like to hear where your team wants to make progress with data and AI. We can discuss a project you have in mind or explore where Databasin could help with the work.
What happens next
Book a demo
Book a conversation about your organization and the work you want to improve. Questions about where to start are welcome.
Explore the opportunity
We show a working example that answers your business questions, then discuss what it would take to deliver it for your team.
Get the first result
After agreeing the first use case, we implement it with your team. We train the people using it and measure how it performs.
FAQ
Are Fabric data agents the same as Databasin agents?
No. Fabric data agents are Microsoft's tools for conversations over supported Fabric sources. Databasin agents run saved skills inside Databasin automations. We prepare the records and business views the work needs, then establish which tools will serve the questions and recurring tasks.
What can a scheduled Databasin agent do?
It runs a saved investigation and produces a finding with evidence. The LLM Agent task is in beta. Its production-source tools are read-only, with query budgets, row caps and turn limits. The workflow can send the output through email, Slack or Teams.
Which identity does the Fabric connection use?
The Microsoft Fabric entry uses Fabric Workspace Identity. Microsoft Fabric OneLake is a separate catalog entry using Azure Service Principal. We configure the route needed by the work, including that identity and the source and destination permissions its tasks require.
Can our Power BI reports stay in place?
Yes. We can implement the source preparation and measures that the existing report needs. That includes establishing how it reads the new views and how its calculations relate to them. The team can continue to use Power BI while the added data work runs behind it.
Can you help if we only need a source pipeline?
Yes. We can deliver the source connection, its model and the recurring pipeline into Fabric. We define the outcome around the people relying on that source. Preparation and monitoring are part of making it usable in their work, even when no new application is required.
Does Data Apps query Fabric directly?
Its supported engines are Trino, Databasin Sail and Databricks. We establish a supported data and query route for Fabric records before implementing a Data App. Fabric's availability as a pipeline destination does not mean that a Data App executes directly on Fabric.
Can this run inside our Azure environment?
Yes. Databasin can run in your Azure tenant alongside the existing Fabric environment. We configure source access and model endpoints for the deployment. The design follows the data, users and security requirements of the application being implemented.
Who supports the workflow after it goes live?
We can run the work for you, provide monthly support hours or stay on call. We agree that arrangement around the data products and workflows being delivered. It establishes how we help when source data, measures or business requirements change after launch.
Talk about your Fabric environment
We would like to hear how your teams use Fabric and what they want to do next. We can discuss a business question, an unfinished connection or a recurring process, and explain how Databasin could help deliver it.