Step-by-Step Guide to Migrating from Power BI Premium to Microsoft Fabric in 2026

Step-by-step guide to migrating from Power BI Premium to Microsoft Fabric in 2026 | Updated October 2026 | By the Infocepts Data & AI Advisory Team | 4-6 weeks for a mid-size tenant | Beginner

What You’ll Learn

Migrating from Power BI Premium to Microsoft Fabric doesn’t have to mean rebuilding your entire analytics stack. This guide walks enterprise technology leaders through the exact sequence Microsoft recommends for a smooth transition, allowing you to complete the full migration before your Enterprise Agreement renewal date without touching a single report or dashboard. You’ll navigate licensing deadlines, understand what the grace period actually means for your data access, and uncover real cost optimization opportunities along the way.

• Understand exactly which Power BI Premium P-SKUs are retiring and what the 30-day/90-day grace period means for your data access.
• Map your current P1-P5 capacity to the correct Fabric F-SKU using Microsoft’s capacity-unit methodology.
• Execute a wave-based workspace reassignment that avoids downtime for business-critical reports.
• Validate, decommission, and right-size your new Fabric capacity to capture significant cost savings.

Prerequisites: Fabric or Power BI admin rights, an active Azure subscription, and a current inventory of Power BI Premium workspaces and gateways.

---

Why Migrating to Microsoft Fabric Matters in 2026

Power BI Premium’s per-capacity licensing model, known as P-SKUs, isn’t quietly fading away. Microsoft is actively phasing it out on a contract-by-contract basis. Microsoft’s own migration decision guide confirms that if your Enterprise Agreement is still active, you can continue running existing P-SKU capacity and renew it annually through your agreement until the EA term ends. But if your Enterprise Agreement or Microsoft Cloud Agreement is expiring, you cannot add or purchase new P-SKU capacity through that agreement. For organizations in media, retail, life sciences, and manufacturing running mission-critical dashboards on Premium, this isn’t a future roadmap item. It’s an operational deadline tied directly to your next renewal date.

The consequences are concrete. According to Microsoft’s Power BI Premium to Microsoft Fabric migration overview, after your subscription ends, your capacity enters a 30-day grace period. Starting on day 31, access is throttled. On day 91 and beyond, all operations are rejected. Your data remains intact but inaccessible until you migrate the workspaces to a Fabric F-SKU capacity or delete the capacity entirely. That’s a 90-day countdown from renewal expiry to a fully locked tenant.

Here’s the upside: Fabric capacity is pay-as-you-go and elastic in ways Premium never was. Fabric capacity can be scaled up, scaled down, and paused on demand, whereas Premium could not. Organizations that move to reserved pricing after right-sizing can pause and resume Fabric instances, allowing for close monitoring and optimal utilization. Once usage patterns are optimized, switching to reserved-instance pricing can reduce costs by approximately 40%. Treated as a strategic project rather than a forced licensing swap, this migration is one of the few mandatory IT events that actually pays for itself.

Key Takeaway: The Power BI Premium P-SKU licensing model is retiring, creating a hard deadline for migration to Microsoft Fabric F-SKUs. Missing this deadline leads to data throttling and inaccessibility, while a proactive migration offers significant cost savings and enhanced elasticity. For supporting data, see Migrating From Power BI Premium to Fabric Capacities.

---

The Process at a Glance

Step	Action	Time	Outcome
1	Inventory workspaces and confirm renewal deadline	2-4 days	Complete map of P-SKU estate and risk exposure
2	Map and right-size your P-SKU to an F-SKU	2-3 days	Correct Fabric capacity size identified
3	Provision Fabric F-SKU capacity in Azure	1 day	Active F-SKU capacity ready for workspaces
4	Reassign workspaces in pilot then production waves	1-4 weeks	All workspaces running on Fabric capacity
5	Validate, decommission P-SKU, and optimize	3-5 days	Legacy capacity retired, costs right-sized

Total time: approximately 4-6 weeks for a mid-size tenant with dozens of workspaces; larger enterprises with cross-region capacities or embedded analytics should budget 8-12 weeks.

---

Step 1: Inventory Your Workspaces and Confirm Your Migration Deadline

What You’re Doing

Before you change any capacity settings, you need complete visibility into your entire Power BI Premium footprint. That means every workspace, gateway, dataflow, and semantic model currently running on Premium, plus the exact date your P-SKU stops renewing. A P-SKU is a per-capacity licensing model for Power BI Premium that is being retired. This inventory becomes your roadmap for everything that follows.

How to Do It

1. Confirm your contract type and renewal date with your Microsoft account representative. This is your single source of truth for migration timing, so don’t skip it.
2. Run discovery against every workspace, not just the ones you expect to contain Fabric items. Even if your organization licensed only Power BI Premium, users might have created Fabric items during a trial period, so cast a wide net here.
3. Use the Power BI admin REST APIs or the Semantic Link Labs admin functions to extract workspace and item metadata at scale.
4. For each workspace, record its region, gateway connections, dataflows, semantic models, refresh schedules, and row-level security setup. This inventory becomes the foundation of your migration plan.

Common Mistakes

Treating the grace period as a deadline: The grace period is a safety net, not a planned migration window. Start early. Skipping gateway and dataflow discovery: These dependencies are the most common cause of post-migration refresh failures, so don’t overlook them.

What Done Looks Like

You have a single spreadsheet or dataset listing every Premium workspace, its region, its dependencies, and your confirmed P-SKU expiry date. That’s it. Simple, but complete.

Key Takeaway: A thorough inventory of all Power BI Premium workspaces and a confirmed P-SKU expiry date are critical first steps, ensuring you understand your estate and avoid treating the grace period as a migration window. For a more detailed walkthrough, see Power BI Premium Capacity Is Retiring & Is Microsoft ….

---

Step 2: Map and Right-Size Your P-SKU to the Correct F-SKU

What You’re Doing

Microsoft Fabric capacity is measured in Capacity Units (CUs) rather than v-cores. You need to translate your current Premium size into its Fabric equivalent, then adjust based on real usage rather than simply copying the old number across. A Fabric Stock Keeping Unit (F-SKU) is the equivalent capacity unit for Microsoft Fabric, replacing the P-SKU model. Capacity Units (CUs) are a measure of compute power in Microsoft Fabric. Getting this right now saves you from over-provisioning and wasting budget later.

How to Do It

1. Start with the default capacity-unit mapping. Each P-SKU v-core corresponds to 8 CUs, so the baseline conversion is straightforward: P1 maps to F64, P2 to F128, and so on.
2. Open the Microsoft Fabric Capacity Metrics app for your P-SKU capacity and review your maximum utilization period. Look at the longest available window in the Metrics App, taking into account any Autoscale consumption on Premium.
3. Complement that historical data with the Fabric SKU Estimator, which models future consumption based on your workload profile and gives you a forward-looking perspective.
4. Flag any peak-usage days where CU utilization runs consistently near 100%. Those periods determine whether you need to size up from the default mapping.

Example

Current P-SKU	Default F-SKU Mapping	CUs
P1	F64	64
P2	F128	128
P3	F256	256
P4	F512	512
P5	F1024	1024

A manufacturing enterprise running P1 today would default to an F64 capacity, which also happens to be the licensing threshold where content can be viewed with a free license. Below F64, every viewer needs Pro or Premium Per User, an important cost consideration if you’re deciding whether to size up or down.

What Done Looks Like

You have a confirmed target F-SKU size backed by both historical Metrics App data and forward-looking Estimator output, not just a default lookup-table guess.

Key Takeaway: Accurate F-SKU sizing requires translating P-SKU v-cores to Fabric CUs, then validating and adjusting based on historical utilization from the Capacity Metrics app and future projections from the Fabric SKU Estimator.

---

Step 3: Provision Your Fabric F-SKU Capacity in Azure

What You’re Doing

Your sizing decision becomes a live, billable Fabric capacity in this step. The key here is to purchase the new capacity separately from your existing Premium capacity so both can run in parallel during validation. This gives you a safety net if something goes wrong.

How to Do It

1. Purchase the F-SKU before you reassign any workspaces, and keep the P-SKU active until reassignment and validation succeed. Never reverse this order.
2. Sign in to the Azure portal and confirm that the Microsoft.Fabric resource provider is registered on your subscription. In the subscription pane, select Resource providers, find Microsoft.Fabric, and select Register if it isn’t already registered.
3. Create the capacity by buying a Microsoft Fabric subscription, choosing the region, SKU size, and billing model (pay-as-you-go or reservation) you decided on earlier.
4. Choose the same region as your existing Premium capacity unless you have an explicit reason to move regions, since cross-region moves require extra handling for large semantic models and Fabric items.

Best Practices

Start with pay-as-you-go billing for the first 30-60 days so you can observe real consumption before committing to a reserved-price term. Keep both capacities active in parallel rather than pausing the P-SKU early; this avoids forcing workspaces into the grace period prematurely.

What Done Looks Like

A live Fabric F-SKU capacity appears in the Azure portal in the correct region, with zero workspaces assigned to it yet.

Key Takeaway: Provisioning the F-SKU in Azure involves purchasing the subscription, ensuring the Microsoft.Fabric resource provider is registered, and selecting the appropriate region and billing model, ideally starting with pay-as-you-go for flexibility.

---

Step 4: Reassign Workspaces in Pilot and Production Waves

What You’re Doing

This is the actual migration: moving workspaces from the old Premium capacity to the new Fabric capacity. You’ll do this workspace by workspace, starting small and expanding once you’ve validated everything works. This wave approach protects you from surprises.

How to Do It

1. Understand that this move happens one workspace at a time. The migration happens at the workspace level; you reassign each workspace from a P-SKU capacity to an F-SKU capacity through the Fabric admin portal or in bulk through the capacity migration notebook. There’s no tenant-wide flip switch.
2. Begin with a pilot: start with a representative but non-critical workspace and validate access, security, reports, gateways, refreshes, and performance before migrating larger batches.
3. Schedule cutovers outside processing windows. Workspace reassignment can interrupt active queries or refresh jobs, so migrations should happen during off-peak hours.
4. For large tenants, automate the bulk of the work. Microsoft provides a capacity migration notebook for automating large-scale workspace transfers, available via the Fabric blog’s migration automation guidance.
5. Move in sequence: non-critical workspaces first, then the bulk of standard content, then business-critical and executive-visible dashboards last, once the pattern has proven stable.

Common Mistakes

Migrating everything at once: Big-bang cutovers remove your ability to catch a broken gateway or RLS rule before it hits executive dashboards. Ignoring cross-region content: Large semantic models and Fabric items created during a trial often need to be backed up and recreated rather than simply reassigned. You must back them up or capture their definitions before reassignment, then recreate them in the new region.

What Done Looks Like

Every workspace from your Step 1 inventory now shows the new F-SKU capacity in its settings, with refreshes, gateways, and row-level security confirmed working against the new capacity.

Key Takeaway: Workspace reassignment is a manual, workspace-level process best executed in controlled waves, starting with pilots and scheduling cutovers during off-peak hours to minimize disruption and validate functionality.

---

Step 5: Validate, Decommission the P-SKU, and Optimize Capacity

What You’re Doing

Once every workspace has been confirmed healthy on Fabric capacity, you close the loop by retiring the old Premium capacity and tuning the new one for cost efficiency. This is where you capture the 40% savings mentioned earlier.

How to Do It

1. Confirm no orphaned workspaces remain on the P-SKU by cross-checking your original inventory against the Fabric admin portal.
2. Cancel the P-SKU only after the migrated workspaces run clean. Buy the F-SKU first, validate, then cancel. Never the reverse.
3. Once you have migrated all of your data to your new Fabric capacities, delete your Power BI Premium capacities.
4. Use the Capacity Metrics app to monitor real consumption for 2-4 weeks, then revisit your billing model. Organizations that right-size after this observation window are the ones capturing the roughly 40% reserved-pricing savings.

What Done Looks Like

Your tenant shows a single active Fabric F-SKU capacity, zero remaining P-SKU capacities, and a CU utilization trend you can explain line by line.

Key Takeaway: The final step involves rigorously validating all migrated content, safely decommissioning the old P-SKU capacity, and then optimizing the new Fabric capacity’s billing model based on observed usage for maximum cost efficiency.

---

What to Do After Completing the Migration

Phase 1: Stabilize (weeks 1-4 post-cutover). Monitor the Capacity Metrics app daily for throttling events or unexpected CU spikes, and keep a rollback runbook on hand even though reverting to a P-SKU is not possible.

Phase 2: Optimize (months 2-3). Revisit your billing model, move stable workloads to reserved pricing, and use the pause/resume capability on non-production capacities to cut idle spend.

Phase 3: Expand (months 3-6 and beyond). With Fabric capacity in place, start piloting the workloads Premium never offered, such as OneLake-based Lakehouses, Data Factory pipelines, and Copilot-assisted report authoring. These are the capabilities that justify treating this migration as a platform upgrade rather than a licensing chore. This is also the point where many enterprises engage a specialist partner. Infocepts believes that data and AI are essential enablers for organizational success and competitive advantage, and positions itself as a results-driven partner emphasizing measurable outcomes, innovation, and client satisfaction throughout exactly this kind of expansion phase.

Key Takeaway: Post-migration activities include stabilizing the new Fabric environment, optimizing costs through reserved pricing and pausing idle capacities, and then expanding into new Fabric capabilities like Lakehouses and Copilot for platform growth.

Let’s Talk

Discuss with one of our Data and AI Experts

Let’s Talk

---

Resources You’ll Need

Resource	Role	Status	Cost
Infocepts	Migration advisory and Fabric implementation partner	Recommended	Custom quote
Microsoft Fabric admin portal	Workspace reassignment interface	Required	Included with tenant
Fabric Capacity Metrics app	Usage monitoring and right-sizing	Required	Free
Fabric SKU Estimator	Forward-looking capacity sizing	Recommended	Free (preview)
Azure portal	F-SKU capacity purchase and management	Required	Pay-as-you-go or reserved

For enterprises managing hundreds of workspaces across media, retail, life sciences, or manufacturing environments, Infocepts delivers measurable business value through tailored Data & AI solutions, leveraging 21+ years of expertise, proprietary platforms, and a global footprint. Its capabilities span AI-led operations, advanced analytics, cloud modernization, and frictionless migration, ensuring accelerated digital transformation and superior client outcomes for organizations navigating exactly this kind of mandatory platform shift. See also, see Migrating to Microsoft Fabric Capacity from Power BI ….

---

Common Plateaus & How to Break Through

Refreshes fail immediately after workspace reassignment

Likely cause: Gateway connections or scheduled refresh jobs were not re-validated after the capacity change, and active jobs were cancelled mid-move.

Fix: Migrate during off-hours, pause scheduled refreshes before reassignment, and restart any canceled jobs immediately after cutover. This follows the same pattern practitioner migration checklists recommend for interrupted refresh scenarios.

Fabric capacity feels under-sized compared to the old Premium capacity

Likely cause: The default CU mapping was applied without checking real peak utilization, or Autoscale consumption on the old Premium capacity was never factored in.

Fix: Go back to the Capacity Metrics app and the Fabric SKU Estimator from Step 2, compare peak-day CU consumption against the new SKU’s ceiling, and scale up one tier if utilization regularly exceeds 80%.

Workspaces get “orphaned,” still pointing at the old P-SKU

Likely cause: The original inventory in Step 1 was incomplete, often because trial-created Fabric items were missed.

Fix: Re-run workspace discovery using the admin REST APIs, cross-check every workspace against your migration tracker, and confirm ownership with individual workspace owners before declaring the cutover complete.

Leadership is confused about whether Power BI itself is being discontinued

Likely cause: Messaging around “Power BI Premium retirement” is frequently misread as Power BI being deprecated.

Fix: Clarify internally that only the per-capacity P1-P5 purchasing model is retiring. Only the per-capacity P1 through P5 SKUs are retiring; per-user licenses stay exactly as they are, and Power BI reports, dashboards, and Pro/PPU licenses continue unchanged inside Fabric. For more troubleshooting advice, see Should You Migrate to Microsoft Fabric? A Non-Technical ….

---

Conclusion

A disciplined, wave-based approach involving inventory, mapping and sizing, provisioning, reassignment, and decommissioning is the complete step-by-step guide to migrating from Power BI Premium to Microsoft Fabric in 2026 that enterprise IT leaders need to avoid both downtime and the day-91 access lockout. Treated correctly, this mandatory licensing event becomes an opportunity to right-size spend and unlock Fabric’s broader data platform.

Key Takeaways

• Completing this migration means every workspace runs on an active Fabric F-SKU with zero content left on a retiring P-SKU.
• The core insight is that migration is manual and workspace-level, never automatic, so a documented wave plan beats waiting for the grace period to force your hand.
• Next action: Confirm your exact P-SKU renewal date this week and start the Step 1 workspace inventory immediately.

---

FAQ

How to migrate from Power BI Premium to Microsoft Fabric?

To migrate from Power BI Premium to Microsoft Fabric, you must first inventory all Power BI Premium workspaces and confirm your P-SKU renewal date. Next, map your existing P-SKU capacity to the equivalent Fabric F-SKU using Microsoft’s Capacity Metrics app and SKU Estimator. Then, provision the new F-SKU capacity in the Azure portal. The core migration involves reassigning workspaces from the old Premium capacity to the new Fabric capacity in controlled pilot and production waves via the Fabric admin portal. Finally, validate all migrated content and decommission the legacy P-SKU, ensuring no reports or dashboards need to be rebuilt.

Is the Power BI Premium to Fabric migration automatic?

No. Nothing migrates on its own; you manually purchase an F-SKU capacity in the Azure portal and reassign each workspace from the P-SKU to the new capacity. If you take no action, your content moves through the grace, throttle, and block sequence instead.

What happens if I don’t migrate before my P-SKU expires?

Your capacity enters a 30-day grace period, interactive operations are throttled starting day 31, and from day 91 onward all operations are rejected, with your data retained but inaccessible until you migrate or delete the capacity, exactly as described in Microsoft’s official migration overview.

Which Fabric F-SKU replaces my current Power BI Premium P-SKU?

The default capacity-unit mapping is P1 to F64, P2 to F128, P3 to F256, P4 to F512, and P5 to F1024, though you should validate this against your own peak usage with the Fabric SKU Estimator before purchasing, since real consumption often differs from the default lookup table.

Will I need to rebuild my Power BI reports after migrating to Fabric?

Usually not. Most organizations can move their workspaces to Fabric capacity without rebuilding existing Power BI reports. The migration is a capacity reassignment, not a redevelopment project.

Does Power BI Pro or Premium Per User get affected by this retirement?

No. Only the per-capacity P1 through P5 SKUs are retiring; Power BI Pro and Premium Per User licensing continues unaffected and those users keep working exactly as before.

How long does a typical Power BI Premium to Fabric migration take?

For a mid-size tenant with dozens of workspaces, the full process, from inventory through decommissioning, typically takes four to six weeks. Larger enterprises with cross-region capacities, embedded analytics, or large semantic models should plan for eight to twelve weeks to account for extra validation cycles.

Should I migrate now or wait for my renewal date?

Migrate as soon as your inventory and sizing are ready rather than waiting for the renewal deadline. Migrate now if your P-SKU subscription is still active, which is Microsoft’s own guidance. Early migration gives you a full validation window before the grace period becomes relevant.

This guide is based on Microsoft’s official Power BI Premium to Fabric migration documentation and Fabric capacity planning resources, current as of October 2026. Licensing terms, grace periods, and SKU pricing are subject to change; always confirm your specific contract terms and renewal date with your Microsoft account representative before planning a migration date.