Migrating from Power BI Premium to Microsoft Fabric: A Step-by-Step Guide

Why This Matters?

Microsoft has announced the retirement of Power BI Premium per capacity SKUs (P-SKUs) in favor of the Microsoft Fabric F-SKU capacity model as part of its unified analytics platform strategy. Fabric includes all Power BI capabilities plus additional workloads like data engineering, data warehousing, Synapse-style analytics, governance, and AI.

If you currently run on Power BI Premium capacity and want to continue without disruption, you need to transition your content to Microsoft Fabric capacity before your next renewal or end of subscription.

---

📅 Key Licensing and Transition Details

Before we dive into steps, here’s the high-level context you need:

• Purchase of Fabric capacity (F-SKUs) is done via Azure; P-SKUs are no longer purchasable after February 1, 2025.

• You can continue using your existing P-SKU until your current agreement expires.

• After the P-SKU ends, Microsoft gives 30 days of free Fabric capacity equal to your previous SKU size to transition your workloads.

• You’ll retain access to your Power BI data for up to 90 days after the P-SKU subscription ends — planning ahead is essential.

• Fabric capacities support all Power BI workloads plus extensive analytics capabilities, so migration is both a platform upgrade and operational shift.

---

🧭 Overview of the Migration Process

At a high level, migrating from Power BI Premium to Fabric involves:

1. Planning your migration strategy

2. Provisioning appropriate Fabric (F-SKU) capacity

3. Reassigning workspaces from Power BI Premium to that Fabric capacity

4. Verifying refreshes, security, and gateways

5. Cleaning up legacy Premium resources

Let’s break each of these down.

---

📌 Step 1 — Plan Your Transition

Effective planning reduces errors and downtime:

🔍 Inventory What You Have

Document:

• All Power BI Premium capacities

• Assigned workspaces

• Gateway connections

• Dataflows, semantic models, data sources, and refresh schedules

This inventory will be the foundation of your migration plan.

---

📌 Step 2 — Provision Fabric Capacity

You must acquire one or more F-SKU capacities suitable for your workloads:

• Decide between Pay-As-You-Go (PAYG) or Reserved pricing (annual commitment). PAYG gives flexibility; reserved offers discounts.

• Azure portal is the gateway for provisioning F-SKU capacities.

• Choose the same region as your existing P-SKU to minimize data latency and region-specific issues.

💡 For like-for-like performance:
F64 is often recommended as a starting point for a replacement for P1.

---

📌 Step 3 — Migrate Workspaces to Fabric Capacity

This is the core step — assigning each workspace to the new Fabric capacity.

🧾 Option A — Manual Migration

Microsoft provides straightforward workspace reassignment:

1. Open the Power BI or Fabric Admin portal.

2. Navigate to Workspaces.

3. Select a workspace and go to Settings → License Info.

4. Choose “Reassign workspace” and select your Fabric capacity (F-SKU).

5. Save changes.

Notes:

• You must have workspace admin permissions and capacity assignment permissions.

• Scheduled refreshes resume after migration (active jobs may be cancelled and will need rerunning).

---

🧠 Option B — Bulk or Automated Migration

For tenants with many workspaces, manual steps may be prohibitive.

Microsoft provides an automated migration tool (a Fabric Notebook) that:

• Creates an equivalent F-SKU (pay-as-you-go) if none exists

• Assigns all selected capacities and workspaces

• Preserves capacity admins and settings

This is particularly useful for tenants with hundreds or thousands of workspaces.

Tip: You may still need to manually transfer some settings like disaster recovery or capacity notifications.

---

🛠️ Step 4 — Review Gateways and Refresh Configurations

After migrating workspaces:

🔑 Gateway Reconfiguration

Gateways do not automatically reassign to the new capacity and must be manually reassigned or scripted via REST APIs.

🔄 Refreshes and Scheduled Jobs

• Active refresh jobs are cancelled during migration; they must be restarted afterward.

• Scheduled refreshes will resume once capacity assignment is complete.

---

📌 Step 5 — Verify and Test

Make sure to:

• Verify dashboard/report access for users

• Validate scheduled refreshes

• Check security permissions

• Monitor performance metrics on the new F-SKU capacity

Testing before decommissioning legacy capacity avoids surprises.

---

🧹 Step 6 — Cleanup

After everything looks good:

• Delete old Power BI Premium capacities when not needed; they won’t auto-delete after the grace period.

• Update documentation and operational runbooks to reference Fabric capacity. 

🧾 Summary

Migrating from Power BI Premium (P-SKU) to Microsoft Fabric (F-SKU) is a critical step for customers continuing on Microsoft’s analytics platform. The essence of the migration is:

1. Purchase/Provision Fabric capacity

2. Reassign workspaces from Premium to Fabric

3. Reconfigure gateways, refresh schedules, and verify workloads

4. Clean up old P-SKUs

It’s a straightforward change on the surface — most migration effort is in planning, bulk reassignment, and ensuring everything is tested afterward. You can choose manual assignment, bulk admin portal assignment, or use the automated migration tool provided by Microsoft. 

🔗 Official Microsoft References

Here are the key official docs and blogs that support the steps above:

• Power BI Premium to Fabric FAQ (guides overall transition steps)

• Microsoft Fabric blog on automated migration (manual and automated approaches)

• Workspace management and reassignment (official admin actions)

• Microsoft announcements and grace period details (licensing and timeline)