Microsoft Fabric Licensing & Pricing - FAQs

Fabric policies are not yet available in every capacity region: at the time of writing the preview is not supported for capacities in West Europe, North Europe or West US. UK South and UK West are not on Microsoft's list of unsupported regions, so UK capacities in those regions should see the feature. Irish organisations, and UK organisations whose capacities were provisioned in North Europe or West Europe, will not see the feature until Microsoft extends regional coverage. Our Fabric policies guide has the current availability details and what to check first.

Yes. Both platforms have non-obvious costs worth knowing. Fabric capacity sizing is its own learning curve, and over-provisioning is common in early Fabric deployments. Databricks workspaces can sprawl, with notebook clusters left running and unmanaged. Both vendors have monitoring tools. Use them from day one rather than discovering the bill at month-end.

Yes, on-demand billing can be used on larger Fabric capacities. On an F2 or higher, individual billing categories can be moved to on-demand while the remaining workloads stay provisioned, which allows spiky workloads to be billed by consumption without changing how steady production load is paid for.

Yes. You can reduce Fabric cost materially through reservations. Annual reservations save around 20 per cent off PAYG list prices. Three-year commitments through an Enterprise Agreement save up to 41 per cent. For workloads that only run during business hours, pausing capacity outside hours saves another 50 per cent on top. Combined, these can reduce Fabric capacity costs by 60 per cent or more against PAYG-without-pausing for typical mid-market patterns. The specific savings depend on your workload pattern; we cover sizing methodology in the True Cost FAQ.

Microsoft Fabric policies do not cost extra and do not consume capacity units. They are included with the Fabric licence, so there is no sizing or budget conversation to have before using them. Limits apply instead: up to 100 rules in a tenant policy, 50 in a capacity policy, and 50 values per condition. Our Fabric policies guide covers the limits, and our Fabric licensing calculator covers capacity costs more generally.

No, warehouse snapshots have no separate storage. A snapshot creates no Parquet files and relies entirely on the source warehouse's existing Delta versioning, so it does not duplicate the underlying data or require a second copy to be built.

Yes, Business Central mirroring consumes Fabric resources: mirrored data is stored in OneLake and queries against it use Fabric capacity. Before adopting mirroring you should check existing capacity headroom and size the estate properly, which is what a Fabric licensing assessment or calculator is for.

To tell whether a Fabric capacity is correctly sized, review carry-forward of smoothed work across a full business cycle including month-end rather than a single utilisation figure, check whether throttling is occurring at peaks, and confirm sandbox workloads are not sharing capacity with critical reporting. Continuous capacity monitoring or a capacity audit gives a reliable answer.

Training and operability costs factor in heavily, and most pricing comparisons miss this. A platform your team can run with existing skills costs less in practice than one that requires hiring. Fabric tends to win on this for organisations with Power BI developers. Snowflake tends to win for organisations with strong SQL engineering teams. The platform you can run is almost always cheaper than the platform you have to staff up to run.

Training and team costs are heavily underweighted in most BI platform pricing comparisons. The platform your team can run with existing skills costs less in practice than one requiring hiring. Fabric tends to win for organisations with Power BI developers and analyst skillsets. Databricks tends to win for organisations with Python and Spark engineering capability. Hire the platform you have a team for, or have a plan to staff the one you need.

To compare BI platform pricing fairly, build a representative workload and price both. Sample queries, refresh patterns, user counts. Most pricing comparisons are unfair because they price one platform at a typical workload and the other at peak. Both vendors have pricing calculators. Use them with realistic numbers, including non-production environments and growth assumptions. Our Microsoft Fabric page covers how we deliver it.

You size a Fabric capacity for an implementation by running a week of representative load on a pay-as-you-go capacity, reading the capacity metrics app to see peak and smoothed utilisation by workload, and then reserving the SKU that keeps smoothed utilisation comfortably under its limit, which for most mid-market estates with an ERP and a few other systems is an F4 to F16. Guessing in either direction either throttles users or wastes thousands a month. Fabric capacity explained covers the method.

Databricks pricing works on consumption, charged in DBUs (Databricks Units) per workload type. Compute scales when needed and stops when idle. Costs are visible per workload but less predictable per month. For organisations with intermittent workloads, this can be cheaper than Fabric's fixed capacity. For continuously running workloads, Fabric capacity often comes out ahead.

Fabric pricing affects the per-user Power BI cost decision through an interaction that is the most commonly missed cost pattern. On Fabric capacity below F64, every author and viewer of Power BI content still needs a Pro licence (£11 per user per month). At F64 and above, viewers are free; authors still need Pro. The crossover point where F64 becomes cheaper than F8 plus per-user Pro is around 500 viewers at PAYG, around 370 with annual reservations, around 250 with three-year EA discounts. Most mid-market businesses sit below the crossover and should stay there.

Microsoft Fabric capacity smoothing spreads the cost of operations over a following window, up to 24 hours for background operations, rather than charging the spike at the moment it occurs. This stops a heavy overnight load from throttling morning reports, but it also means a utilisation chart looks calmer than real demand and can hide a queue of smoothed work that has not yet landed.

Fabric capacity for mid-market is priced as F-SKU capacity, from F2 (around £200 per month) to F2048 for enterprise workloads. Mid-market implementations typically start on F8 (around £1,050 per month) or F16 (around £2,100 per month) for production. F64 (around £6,400 per month) becomes economical when viewer counts exceed roughly 500 because free Power BI viewing kicks in at that tier. The True Cost FAQ in our library covers the licensing economics in detail, including the five overspending patterns we see most often.

AI on Microsoft Fabric costs the capacity you already run, from £138 a month reserved for an F2 with Copilot included, plus the build of the governed foundation if it does not exist, a four-week Establish phase and ten to sixteen week build, and a scoped piece of work for any custom model; there is no separate AI licence for Copilot, data agents or the data science workload. See what an AI analytics project costs.

Fabric mirroring replication compute does not consume capacity units, and mirrored storage is free up to one terabyte per capacity unit, so an F64 includes 64 TB. You pay for the queries that read mirrored data, and a running capacity is required for replication to continue. Our Fabric licensing calculator helps estimate the rest.

Microsoft Fabric costs £0.1585 per capacity unit hour in UK South pay as you go: an F2 is £231 a month or £138 reserved, an F8 £926 or £550, an F64 £7,405 or £4,404, with Power BI viewers free from F64. Storage is £0.0181 per gigabyte per month. See the full UK price comparison with Databricks and Snowflake.

Microsoft Fabric costs £0.1585 per capacity unit hour in UK South on pay-as-you-go, which is £231 a month for an F2, £926 for an F8 and £7,405 for an F64, falling to £138, £550 and £4,404 with a one-year reservation, at Microsoft's October 2026 list prices excluding VAT. Power BI Pro licences at £10.80 per author per month and storage at £0.0181 per gigabyte are added on top. Our Fabric licensing calculator works out the total for your numbers.

A Microsoft Fabric implementation costs the licences, from £138 a month for a reserved F2 capacity plus Power BI Pro at £10.80 per author, and the build, which for a four-week Establish phase and ten to sixteen weeks of delivery is the larger part and depends on the number of sources and the state of the definitions. How much does Microsoft Fabric cost? covers the licence side and our free audit scopes the build.

The platform cost of a data warehouse in Microsoft Fabric depends on the capacity you run, and since FabCon Europe 2026 you can start on an on-demand F0 capacity with no reservation until you know what you use. The consultancy cost is separate and, in our case, quoted as fixed outcome-based phases. Our Fabric licensing calculator gives a first estimate of the platform side, and sizing Fabric capacity without overpaying or throttling explains the method.

Building a data platform for a mid-sized business costs three lines: a Microsoft Fabric capacity from £138 a month reserved for an F2, with an F4 to F16 typical, plus OneLake storage at £0.0181 per gigabyte; Power BI Pro licences at £10.80 per user per month with free viewers from an F64; and a fixed-price build of a four-week Establish phase and ten to sixteen weeks, which on our published tiers is an indicative two-year investment of £52.7k to £114.5k by business size. See the Analytics Acceleration Programme.

Fabric workspaces should be tiered into mission-critical, operational and sandbox groups. Mission-critical reporting sits on reserved, monitored capacity; operational departmental work shares capacity with headroom reserved for month-end; and sandbox experimentation sits on separate on-demand capacity with a spend limit, so testing can never throttle business-critical reporting.

Yes, a one-year reserved Fabric capacity is worth it for any steady production workload, because it costs £825.69 per capacity unit per year in UK South, a 40% discount against pay-as-you-go, and a three-year reservation costs exactly three times that, buying price certainty rather than a further discount. Keep development and proof of concept work on pay-as-you-go or on demand so it can be paused. Our free audit will tell you which capacity to reserve.

For many mid-market businesses, starting Microsoft Fabric on the new F0 on-demand capacity is sensible, because it lets you measure real usage before committing to a reservation. Pricing for F0 and on-demand billing had not been published at the time of writing, so the right move is to run a baseline first and reserve only once the pattern is clear. Our Fabric licensing calculator gives a first estimate, and sizing Microsoft Fabric capacity without overpaying or throttling explains the method.

You should forecast at both SKU and aggregate level, with reconciliation. SKU-level forecasts inform stock decisions; aggregate forecasts (category, total) inform broader planning and reconcile against expected revenue. Independent SKU and aggregate forecasts often disagree (the SKU forecasts add up to a different total than the aggregate forecast). Hierarchical forecasting techniques (using libraries like hts) reconcile the levels mathematically. For most mid-market businesses, simpler approaches (forecast at the most useful level, use management judgement to reconcile) work well enough.

Azure cost for mid-market data work is variable, because the services are consumption-priced. Typical mid-market Azure data spend ranges from around £1,000 per month for a modest implementation (small ADF environment, small Azure SQL database) up to £10,000 or more per month for a substantial estate. Reservations and Enterprise Agreements reduce list prices materially (typically 20 to 41 per cent for committed usage). The True Cost FAQ in our library covers the licensing economics; this FAQ covers the architectural choices that determine which services you actually need.

Azure data engineering costs a platform line and a build line: a Fabric capacity from £138 a month reserved for an F2, Power BI Pro at £10.80 per author and OneLake storage at £0.0181 per gigabyte, plus a build priced per phase, a four-week Establish and ten to sixteen weeks of build, that includes governance, testing and enablement rather than leaving them for a phase two. See how much Microsoft Fabric costs.

Fabric usually costs less than running the components separately at mid-market scale, once integration costs are factored in. Buying ADF, Synapse, Power BI Premium, and Storage separately produces a list-price total similar to or higher than equivalent Fabric capacity, with significantly more configuration work. The integration tax is real: separate components require integration engineering, separate governance, and separate operational overhead. Fabric removes that. For mid-market businesses, the all-in cost of Fabric is usually lower than the all-in cost of equivalent capability assembled from separate Azure components.

Fabric cost is capacity-based. You buy a capacity tier (F2, F4, F8, and so on) and run workloads against it. Costs are predictable per month, less so per query. Mid-market organisations typically land on F4 or F8 for production, costing several hundred to a few thousand pounds a month. Power BI Premium licences flow into Fabric capacity, so existing investment is not lost.

Beyond the licences, a Microsoft Fabric project costs the build and the adoption: an Establish phase to agree sources and definitions, then a build of the ingestion, lakehouse, semantic model and reports, which for a mid-market business is typically a four-week Establish phase followed by ten to sixteen weeks of build, and is the larger part of the total cost. Data warehouse consultancy in the UK explains what that money buys.

Fabric throttles in four stages based on how much future capacity the work has consumed: up to 10 minutes gives overage protection with no throttling, 10 to 60 minutes delays interactive jobs by 20 seconds at submission, 60 minutes to 24 hours rejects interactive jobs while background operations still run, and beyond 24 hours all requests are rejected until the consumed CUs are paid off.

A fixed-price data platform build on our tiers includes the four-week Establish phase with signed definitions and architecture, the landing of the ERP and other systems into a layered lakehouse, the gold star schema and certified semantic model reconciled to the ledger, the priority reports, security, Git and deployment pipelines, a month end closed on the platform, analyst enablement and two years of continuity support. See what a Power BI engagement costs.

F0 is a zero-provisioned Microsoft Fabric capacity SKU with true on-demand billing, announced at FabCon Europe 2026. Nothing is reserved up front, usage is measured in CU-hours without smoothing, and spend limits apply over a rolling 24-hour window, which lowers the cost of starting with Fabric and suits spiky or isolated workloads.

The cheapest Microsoft Fabric capacity is an F2 at £231 a month on pay-as-you-go or £138 a month with a one-year reservation in UK South, and it is enough for development, proofs of concept and small production workloads such as a single-company Business Central model. Fabric can also be bought on demand since October 2026, paying per hour used, which can be cheaper still for irregular use. Fabric capacity explained covers sizing.

The cost of switching BI platforms later is lower than it used to be, because both platforms support open table formats (Delta, Iceberg) and standard SQL, which makes switching easier than it once was. Switching is still meaningful work, mostly in semantic models, BI tooling and security. Plan as if you are choosing for five years. Switching is possible but not free, and choosing well now is cheaper than fixing it later.

A tenant-scoped Fabric policy applies across the whole organisation and can only be activated by a Fabric administrator, while a capacity-scoped Fabric policy applies to the workspaces on one capacity and is activated by that capacity's administrator. The scope is chosen when the policy set is created and cannot be changed afterwards, and only one policy set can be active per scope at a time. External data sharing and workspace settings editing are tenant policies; item creation is a capacity policy. See our Fabric policies guide for how the two scopes fit together.

Power BI Copilot and Fabric Copilot both run on Fabric capacity. Since April 2025 the minimum capacity is F2 (around £200 per month). Before that change, the minimum was F64. The reduction is significant for mid-market organisations that were previously priced out. The capacity covers all Fabric workloads, not just Copilot, so the cost should be assessed against the whole platform value, not Copilot in isolation.

The ongoing cost of a data platform after it is built is the Fabric capacity, from £138 a month reserved for an F2 to £1,101 for an F16, OneLake storage at about £18 per terabyte per month, Power BI Pro at £10.80 per author and viewer below an F64, and whatever continuity support the business chooses; on our tiers two years of continuity are included in the published investment. See how much Microsoft Fabric costs.

A mid-sized business usually needs an F4 to F16 Fabric capacity for a first data platform, from £275 to £1,101 a month reserved, sized on the overnight load and the daytime query pattern rather than the data volume, with reservation for the base and pay as you go for peaks; the capacity can be resized in an afternoon, which is why it is decided last. See the Fabric licensing calculator.

Real-time analytics pays back in five recurring patterns. Operational dashboards where the value of acting in seconds exceeds the cost of the streaming infrastructure. Fraud detection where the window to prevent loss is short. Supply chain visibility where shortages or delays need to surface before they affect customers. IoT and connected products where the device data is inherently streaming. Customer-facing operations (call centres, dispatch, warehouse) where decisions are made in real time anyway. Outside these patterns, batch analytics is usually sufficient and significantly cheaper. Our Microsoft Fabric page covers how we deliver it.

Fabric pay-as-you-go is cheaper than reserved capacity only when the capacity genuinely runs for a minority of the month, because reservations are around 40% cheaper than the pay-as-you-go rate. Past roughly 59% sustained usage the reservation wins, so production capacities serving business-hours reporting should almost always be reserved.

You see Copilot costs in Microsoft Fabric in the Fabric Capacity Metrics app under the operation Copilot in Fabric, measured in capacity units and billed as a background job smoothed over 24 hours; converting those capacity units to pounds at your capacity rate gives the running cost line for the scorecard. See our Fabric licensing calculator.

Anomaly detection pays back fastest in five recurring patterns. Finance integrity (unusual journals, expense outliers, supplier payment anomalies). Operations monitoring (equipment, process, service quality). Supply chain (delivery exceptions, demand spikes, stock anomalies). Customer behaviour (unusual purchase patterns, account compromise). Cyber security (unusual access patterns, data exfiltration).

Demand forecasting pays back fastest in five business shapes. Retailers with significant stock investment where over-stock and stock-out costs are material. FMCG and consumer goods with multi-channel distribution. Wholesalers and distributors with thousands of SKUs and multi-warehouse stock. Manufacturers with long production lead times. Subscription businesses needing capacity planning. The pay-back is typically through stock optimisation savings (lower stock levels at the same service level, or higher service levels at the same stock level) and through fewer stock-outs reaching customers.

Market basket analysis pays back in five common applications. Cross-sell recommendations (when a customer puts A in the basket, suggest B). Email campaign segmentation (target customers who have bought A but not B). Store layout decisions (place strongly associated products near each other or deliberately apart). Range planning (identify products that anchor baskets versus products that come along). Promotional design (price the anchor product to drive baskets). Each pays back when the marginal margin from the rule-driven action exceeds the cost of implementing the rule. For most retailers and wholesalers, several of the rules surfaced are commercially material.

The Fabric capacity a mid-market business needs is usually an F4 to F16 for a first platform, sized on the overnight load and the daytime query pattern rather than the data volume, with reservation for the base and pay as you go for peaks; F64 is the point at which free Power BI viewing pays for itself at around 380 to 400 users. Our Fabric licensing calculator gives a first estimate.

Pausing a Fabric capacity can cause a large bill because smoothing carries unbilled work forward, and pausing forces that carried-forward usage to be settled and added to your Azure bill straight away, instead of being spread over the following hours. Scaling down sharply can also push a busy capacity into throttling. Separately, if the capacity overage option is switched on, work beyond the capacity is billed on its own meter at around three times the pay-as-you-go rate with no reservation discount. Let smoothed work drain and confirm there is no significant carry-forward before pausing.

Copilot in Fabric adds to capacity load, but on its own it rarely causes throttling, because Copilot operations are billed as background jobs and smoothed over 24 hours rather than charged as a single spike. Each request is charged in capacity units under the Copilot in Fabric operation, at 100 CU seconds per 1,000 input tokens and 400 per 1,000 output tokens, so a typical question of 2,000 input and 500 output tokens uses about 400 CU seconds. Throttling becomes a risk when heavy Copilot use sits on top of a capacity that is already near its limit, so watch the Copilot in Fabric operation in the Fabric Capacity Metrics app alongside your other background jobs. See what an AI analytics scorecard should track.