Key Takeaways
- Only 1 in 20 large companies say their data is actually ready to support their AI initiatives, according to a 2026 Dun & Bradstreet survey.
- Microsoft Fabric and Azure Databricks can now read each other's data in both directions without copying it, a capability that reached general availability at Databricks' Data + AI Summit in June 2026.
- Running both platforms together lowers cost and speeds up reporting by removing duplicate copies of the same data, and it closes a real gap: 78% of executives don't feel confident they could pass an independent AI governance audit today.
- Mastercard, Novo Nordisk, and PepsiCo are among the named companies already building on this exact combination.
- The decision left for CIOs is where the next budget dollar goes: deeper into Databricks engineering, or deeper into Microsoft Fabric and Power BI reporting.
Every board is asking the same question this year: are we ready for AI. Most CIOs already know their honest answer, and it comes as a number, not a feeling. Nearly every large company already has AI initiatives running. Only 1 in 20 believe their own data can actually support that work.
That gap has a boring, specific cause: the numbers a data science team trusts and the numbers a board sees have rarely been the same copy. For any enterprise already running both Microsoft Fabric and Databricks, that copy problem closed this summer. What’s left now is a budget question: where the next dollar of data investment goes.
Why only 1 in 20 companies say their data is ready for AI
A recent survey from Dun & Bradstreet found that 97% of large organizations already have active AI initiatives running. Only 5%, about 1 in 20, say their data is actually ready to support that work. Cayetano Gea-Carrasco, the firm’s chief strategy officer, drew the real distinction: a company doesn’t need its entire data estate to launch a pilot or a single AI use case. It needs that discipline to run AI reliably across the workflows that keep the business moving, onboarding, compliance, risk management, customer operations. That’s a much higher bar, and it’s the one 95% of large companies haven’t cleared yet.
That has a real cost, and it’s measurable. Grant Thornton’s 2026 AI Impact Survey found that 78% of executives don’t feel confident they could pass an independent AI governance audit with ninety days’ notice. Two teams keeping two versions of the same number is exactly how that confidence disappears. A separate IBM Institute for Business Value study found that two out of three CIOs and CTOs are already being held accountable for AI systems they don’t fully control. The accountability showed up before the tooling to manage it did, and that’s exactly where a CIO’s own job gets harder, whatever the board deck says about strategy.
None of this is really new pressure, just louder pressure. Deloitte’s 2026 Global Leadership Technology Study found that 79% of IT leaders now list driving business outcomes, not keeping systems running, as their top priority. A CIO who used to get judged mainly on uptime is now getting judged on whether the business actually trusts what comes out of the data underneath it. That’s a harder thing to be graded on, and it’s exactly the grade the readiness numbers above are describing.
For a large group of companies, this gap has a specific, familiar shape. Databricks tends to be where a data science or engineering team does its real work, training models, cleaning up messy source data, building pipelines. Microsoft Fabric, and Power BI running inside it, tends to be where the rest of the business actually sees those numbers, in dashboards, in board decks, in reports a CFO signs off on. When the two systems don’t share one copy of the data, somebody in the middle reconciles them by hand, and that manual patch is exactly the pattern Kupriyanova describes.
That’s the version of the AI-readiness problem worth solving first, because as of this year, it has an actual fix behind it.
The ROI case for running Microsoft Fabric and Databricks together
Microsoft Fabric has been able to read data governed inside Azure Databricks for a while now, without copying anything. This June, the reverse became true too: Azure Databricks can now read data sitting in Microsoft Fabric’s OneLake, a capability that reached general availability at Databricks’ own Data + AI Summit rather than staying a preview. That’s the plumbing. What it’s actually worth is a different question, and answering it honestly means netting the benefit against what it still takes to get there, not just listing the upside.
For a company already running both platforms:
- Lower infrastructure cost, but only once both directions are actually configured and adopted, not automatically the day the announcement lands. The direction where Azure Databricks writes its own tables into OneLake is still in public beta, so full symmetry isn’t universal yet.
- Faster reporting, but only as good as the data underneath it. Zero-copy access moves a bad number to a board just as fast as a good one. This removes a delay. It doesn’t fix a data-quality problem.
- Lower audit exposure, but governance still has to be set up on both sides. One shared copy of the data doesn’t mean one shared set of permissions around it. Somebody still has to decide who can see what, on each platform, deliberately.
For a company that only runs one of the two today and is deciding whether to add the other:
- The cost of adding the second platform drops, since doing so no longer means re-architecting the first one or building a custom pipeline just to connect them.
- The switching risk drops too. Adding Microsoft Fabric doesn’t require pulling data science workloads off Databricks, and adding Databricks doesn’t require giving up Power BI reporting already built on Microsoft Fabric.
- The timeline drops, from months of custom integration work to whatever it takes to turn on a feature that already exists.
None of this is free, and none of it is automatic. It’s real, it’s tied to a specific announcement rather than a sales deck, and it still takes a deliberate decision on both sides before it shows up as actual savings.
Where Microsoft Fabric and Databricks matter most: banking, retail, healthcare
This is already real for the companies committed to it. At the same Data + AI Summit where the new interoperability got announced, Databricks’ own keynote lineup included Magesh Bagavathi, PepsiCo’s global chief data and AI officer, Federico Cohen Freue, Mastercard’s executive vice president for AI and data operations, and Sinna Lia Vange, a principal IT solution architect at Novo Nordisk. Mastercard specifically ran a live demo of the new data-federation capability on the summit floor. Three large, real companies, spanning payments, healthcare, and consumer goods, put their own data leadership on a public stage next to this exact technology. These are the customers showing up to say so themselves, which carries more weight for another CIO weighing this decision than any vendor’s marketing slide ever could.
That spread roughly tracks where the split matters most in practice. A bank or payments company needs its regulatory reporting to match the exact numbers its risk and fraud models use, down to the decimal, since a mismatch there isn’t a technicality, it’s an audit finding with a regulator’s name on it. A hospital system or pharmaceutical company needs clinical and operational reporting to move fast without loosening the controls on patient data, where the two goals usually fight each other. A retailer needs its demand forecasting and its merchandising dashboards looking at the same customer, not two different guesses about who that customer actually is, or two different inventory numbers for the same warehouse. None of these are edge cases. They’re the ordinary shape of a large company where more than one team touches the same data every single day.
What CIOs still have to decide about Microsoft Fabric and Databricks
With the platform question settled for the growing number of companies that already run both Microsoft Fabric and Databricks, a real decision remains. It comes down to where the next dollar and the next hire go. More capacity for the team building and training models inside Databricks buys faster experimentation and more custom AI work. More capacity for the team turning that work into something a business user can trust and act on inside Microsoft Fabric and Power BI buys wider, faster adoption across the parts of the business that never touch a notebook. Both sides of that split just got measurably more valuable, since neither one has to spend its budget on the plumbing between them anymore. That’s the kind of decision a CIO is actually paid to make, a better one than “which vendor do we standardize on,” which was never really the point.
A reasonable way to run that conversation: look at which of the teams are still spending real hours every month reconciling numbers by hand, and put the first new dollar there, whichever side of the split it happens to sit on. Then look at which decisions are still waiting on a nightly export before anyone can act on them, and fund that gap next. The platforms stopped forcing an order on anyone. The order still has to come from somewhere, and it should come from wherever the actual pain is sitting, not from whichever vendor sent the most recent email.
The alternative to making that call deliberately isn’t neutral. A company that never explicitly decides where the next dollar goes tends to default to whichever team complains loudest, or whichever platform a departing analyst happened to prefer. That kind of default is exactly how the two-copies problem described earlier in this piece got built in the first place, one unplanned workaround at a time. Making the call on purpose, even an imperfect one, beats inheriting it by accident.
The 1-in-20 number this piece opened with won’t move just because two platforms got better at reading each other’s data. It moves when a company decides where its next investment goes and follows through with the same discipline it would apply to any other capital decision. The infrastructure stopped being the obstacle this year. What a company does with that opening is still entirely its own call.
Frequently Asked Questions
What changed between Microsoft Fabric and Databricks in 2026?
OneLake Catalog Federation reached general availability at Databricks’ Data + AI Summit in June 2026, letting Azure Databricks query OneLake data with no pipeline and no copy. Microsoft Fabric could already read Databricks data the other way. The same event moved writing Unity Catalog tables directly into OneLake to public beta, one step short of full two-way parity.
Do you still need pipelines to move data between the two platforms?
No. A Power BI report, a Databricks notebook, and a Microsoft Fabric warehouse can query the same table once a Microsoft Fabric admin turns on a few tenant settings, no engineering pipeline required. The connection is read-only for now: Azure Databricks can pull OneLake data through it but can’t write back yet.
Does this mean governance and permissions are unified too?
No. Zero-copy access doesn’t carry a platform’s permission rules with it. Unity Catalog’s row-level security needs its own setup on the Microsoft Fabric side of a mirror, it doesn’t carry over automatically. 78% of executives don’t feel confident they could pass an independent AI governance audit today.
Is Microsoft Fabric replacing Databricks, or the other way around?
Neither. Databricks is the company and platform, running on AWS, Azure, and Google Cloud. Azure Databricks is the Azure-native version Microsoft and Databricks build together, same engine, different packaging. Microsoft Fabric is a separate product for reporting and BI through Power BI, built on OneLake. Databricks handles the engineering; Microsoft Fabric puts that work in front of the business.
Which companies are already running this combination?
Mastercard and Novo Nordisk are named speakers on this exact setup at Data + AI Summit 2026, alongside PepsiCo, AstraZeneca, and Nasdaq as featured Databricks customers. Databricks counts 20,000-plus organizations including 70% of the Fortune 500. Microsoft Fabric has passed 31,000 customers and $2 billion in annual recurring revenue, up 60% year over year.
What should CIOs decide now that the platforms work together?
Where the next dollar of data investment goes: deeper into Databricks for engineering and model building, or deeper into Microsoft Fabric and Power BI for putting that work in front of the business. Most enterprises already run both, so this budget call repeats every planning cycle.