Overview
In this episode of The Dashboard Effect, Brick Thompson and Caleb Oaks share their takeaways from the Microsoft Build conference, focusing specifically on Microsoft Fabric and what its arrival means for organizations currently building or evaluating their data infrastructure. The conversation covers what makes Fabric a meaningful evolution beyond Azure Synapse, what the OneLake concept changes about how data is stored and accessed, and what practical advice the hosts offer for teams who are mid-project and trying to figure out how Fabric fits into their current plans.
For any organization invested in the Microsoft data ecosystem and trying to understand where it is heading, this episode provides a clear and experience-grounded orientation to what Fabric is and why it matters. See how Blue Margin’s Managed Data Platform helps organizations implement Microsoft Fabric and take advantage of what the platform makes possible without navigating the complexity of the transition alone.
What This Episode Covers
Microsoft Fabric Overview (1:24 – 2:20)
The hosts describe Fabric as a major evolution of Microsoft’s BI stack, moving beyond the Azure Synapse model toward a managed data platform that significantly simplifies configuration and data management. The direction is toward consolidation and accessibility, reducing the operational overhead that came with assembling and maintaining the components of a Synapse-based architecture while expanding what the platform can do for organizations that invest in it.
The OneLake Concept (2:23 – 5:50)
OneLake is the standout architectural feature of Fabric. By storing data centrally in Delta Parquet files, it eliminates the data duplication problem that arises when different systems each maintain their own copy of the same data. A particularly notable capability is the ability to access data from external sources like AWS or Azure without physically moving the files, using proprietary indexing that maintains high performance while keeping the data where it already lives. For organizations with data spread across multiple cloud environments, this changes the consolidation conversation significantly.
Accessibility and Pricing (7:00 – 8:34)
The hosts note that Fabric’s entry-level pricing, around $275 per month, is surprisingly accessible relative to previous premium Microsoft data offerings. That pricing makes Fabric a realistic option for mid-market organizations that might have previously assumed a platform of this capability was out of their budget, and it changes the cost side of the build versus buy calculation for organizations evaluating data platform options.
Advice for Current Data Projects (9:31 – 10:34)
For organizations that are starting data projects before Fabric reaches general availability, the hosts offer a practical bridge strategy: build on Azure Data Lake Storage now. When Fabric goes live, existing data can be connected through shortcuts without requiring a migration. That continuity means teams do not have to choose between starting now and being positioned for Fabric later. The two are compatible, and the recommendation is to move forward rather than wait.
Flexible Engines on a Shared Data Layer (11:11 – 11:55)
Fabric allows users to switch between different processing engines, including the Warehouse for T-SQL-based work and the Lakehouse for Spark and Python-based work, while operating on the same underlying data. That flexibility means teams with different technical backgrounds and different analytical needs can work in the paradigm that fits their use case without requiring separate data environments or data copies for each engine. The data is shared. The access methods are flexible.
Who It’s For
This episode is worth your time if you are a data architect or technology leader evaluating Microsoft Fabric and wanting a practitioner’s take on what differentiates it from the Azure Synapse architecture it is replacing, a team that is currently mid-project on a data initiative and trying to understand how Fabric fits into or affects what you are building, an organization that has been priced out of premium Microsoft data offerings and wants to understand whether Fabric’s entry-level pricing changes that calculation, or any business invested in the Microsoft ecosystem that wants to understand what the Build conference announcements mean for the direction of the platform and what they should be planning around.
Why It’s Worth a Listen
The OneLake discussion is the most architecturally significant part of the episode. The ability to access data from multiple cloud environments without moving it addresses one of the most persistent friction points in multi-cloud data strategies, and understanding what that enables changes how organizations think about consolidation without forcing a single-cloud commitment.
The advice for current projects is the most immediately actionable part of the conversation. Organizations that are waiting for Fabric to reach general availability before starting data work are deferring value unnecessarily. The bridge strategy the hosts describe, building on Azure Data Lake Storage now and connecting to Fabric via shortcuts later, removes the false choice between starting today and being ready for the platform the ecosystem is moving toward.
And the pricing point is worth taking seriously for mid-market organizations that have historically assumed Microsoft’s more capable data infrastructure was out of reach. The accessibility of Fabric’s entry-level tier changes the landscape for organizations that have been managing on less capable or more fragmented infrastructure because the alternative seemed prohibitively expensive.
