Loading...
Microsoft Fabric 101
Microsoft Fabric is Microsoft's unified analytics platform: one place to bring your data together, keep it governed, and get reporting and AI that actually work. Here is what it is, what sits inside it, and how the pieces fit, in plain English.
The short version
Most organisations run analytics across a handful of disconnected services: one to move data, another to store it, another to transform it, another to report on it. Every seam between them is somewhere data gets copied, drifts out of sync, or quietly breaks.
Microsoft Fabric is Microsoft's answer to that fragmentation: a single software-as-a-service (SaaS) platform that unifies the whole data lifecycle (ingestion, storage, transformation, real-time analytics, data science and reporting) on one shared foundation. You do not provision servers, resource groups or storage accounts; the platform manages the infrastructure for you.
Underneath every workload sits OneLake, a single logical data lake for your whole organisation, with Microsoft Purview governance built in. Because every experience reads from and writes to the same OneLake, your data stays in one place instead of being copied between tools, which is exactly the condition trustworthy reporting and practical AI depend on.
What's inside
Fabric is organised into role-specific workloads that share the same storage, security and governance. You do not have to adopt all of them; most teams start with the two or three that solve the problem in front of them. Here is what each one does and why it matters.
One data lake for the whole organisation
OneLake is the foundation the rest of Fabric is built on: a single, logical data lake that comes automatically with every Fabric tenant, built on Azure Data Lake Storage. It stores data in open formats (Delta Parquet and Iceberg), so it isn't locked into a proprietary format. Shortcuts let you reference data that already lives elsewhere (in other workspaces, or in Amazon S3 and Google Cloud Storage) without copying it.
Why it matters
One governed copy of your data, reusable by every tool, is what stops the spreadsheet-versus-dashboard arguments about whose numbers are right.
Why it matters
Plenty of tools can move, store or chart data. Fabric's difference is the shape of the platform itself: one governed foundation instead of a stack you assemble and maintain yourself.
Ingestion, storage, transformation, real-time analytics, data science and reporting live in one SaaS environment. There is no wiring separate services together, and no infrastructure to run.
Every workload reads and writes the same OneLake, so a dataset ingested by a pipeline, refined in a notebook and shown in a report stays in one place: no duplication, no drift.
Microsoft Purview governance is built in. Permissions, sensitivity labels and auditing are applied centrally and inherited across items, rather than reinvented per tool.
OneLake stores data in open Delta Parquet and Iceberg formats that any compliant tool can read: your data is not trapped in a proprietary store.
Connected, governed data is the precondition for AI, automation and reporting that work. Fabric is built to provide that foundation, with Copilot embedded across it.
Fabric integrates with Microsoft 365 and lives inside your own Microsoft tenant, so data can be consumed in tools like Excel and Teams that your people already use.
Clearing up the confusion
These names get used interchangeably and they shouldn't be. Here is how they actually relate.
The unified SaaS platform that brings the analytics workloads together on OneLake. It is the umbrella the others now sit under or alongside.
Think of it as the whole platform, not a single tool.
Microsoft's reporting and dashboard tool. It is a fully native workload inside Fabric: the same Power BI you may already know.
Power BI is one part of Fabric. Using Power BI means you are already using Fabric.
The earlier Azure analytics service, run as platform-as-a-service (PaaS): you manage more of the underlying Azure infrastructure yourself.
Fabric is the SaaS evolution, delivering equivalent data engineering, warehousing and data science experiences without that infrastructure overhead.
Fabric doesn't force an overnight rip-and-replace. Power BI keeps working, and existing Azure investments still have their place: the shift is that you stop stitching the pieces together by hand.
The commercial basics
Fabric is licensed on capacity, not per feature. The mechanics are worth understanding before you talk numbers: this is also where the 'no second platform bill' argument comes from.
A capacity is a pool of compute measured in Capacity Units (CUs). Every workload and every workspace assigned to it draws from the same pool, so one capacity can serve the whole organisation rather than a licence per tool.
Fabric capacities are sold as F SKUs, sized from small (F2) up to very large. You purchase them in Azure, or through a Microsoft partner (CSP), and can resize up or down, or pause them entirely when they're idle.
F capacities are billed per second with no long-term commitment, so you can start small. If usage is steady, a yearly reservation lowers the rate.
Authoring Power BI content needs a Power BI Pro (or Premium Per User) licence. At the F64 capacity size and above, users with a free licence can view Power BI content held in that capacity.
The takeaway: one capacity, sized to what you actually use, can replace several separate tool subscriptions: a governed foundation with no second platform bill.
Common questions
Where to start
Book a 30-minute fit call. It's a short, no-obligation conversation with a senior person, not a sales pitch, to work out whether a governed Microsoft Fabric foundation is the right next step, and what a fixed-scope first sprint would cover.