All stacks · Warehouses & analytics
OneLake, Lakehouse, Data Factory, and Power BI in one Microsoft plane.
Microsoft FabricOneLake shortcuts are not a copy job, capacity units are shared, and a Power BI refresh can queue a Spark notebook. Fabric is not rebranded Synapse.
AzureA practical guide to the Azure data platform: when to use Data Factory, what happened to Synapse, and how Microsoft Fabric changes the picture.
AzureA component-by-component migration map from Synapse to Fabric, the T-SQL and workload management gaps that bite, and the order I move things in to keep risk low.
Microsoft Fabric is the bet that OneLake, lakehouses, Data Factory, and Power BI share one capacity meter and one security story. Synapse-era shops are mid-migration; that is the tutorial problem, not a greenfield demo.
We already cover Synapse-to-Fabric and Azure Data Factory patterns. This stack page is the hub for the Microsoft analytics plane.
No. The UX and capacity model changed; Spark and SQL still exist, but OneLake and the item types are the new contract. Treat a lift-and-shift of every Synapse pipeline as a project, not a toggle.
Many estates still run classic ADF. Fabric Data Factory is the direction Microsoft is selling. New work should land where your capacity and IAM already live — dual control planes are how jobs get lost.
If the org is Microsoft-only and Power BI is the serving plane, Fabric is the political winner. Snowflake still wins multi-cloud sharing and a lot of SQL performance work. Iceberg/OneLake shortcuts make “or” less binary each year.
One email a week with our latest tutorials. No spam.
Newsletter signup is not live yet. Use the contact form if you want to be notified.