Migrating from Power BI Premium to Microsoft Fabric is a major step for organizations seeking enhanced analytics, scalability, and new features. This guide provides a comprehensive checklist, best practices, and mitigation strategies to ensure a smooth and successful migration.
What to Expect
Pre-Migration (Months -3 to 0): Planning & Setup
- Conduct a thorough inventory of all assets. The inventory should record:
- Workspace name and ID.
- Workspace owners and business contact.
- Reports, dashboards, paginated reports, dataflows, and semantic models.
- Semantic-model storage format.
- Fabric-native items.
- Refresh schedules and pipelines.
- Gateway dependencies.
- Current capacity settings.
- Planned migration batch and target capacity.
- Decide on Fabric capacity sizing and arrange Azure subscription if needed.
- Assemble a dedicated migration team.
- Establish a detailed schedule for all preparatory steps.
- Register the Microsoft.Fabric resource provider.
- Confirm permission to create and manage Fabric capacities in Azure.
- Confirm the Fabric administrator role.
- Confirm capacity administrator rights on the source P SKU.
- Confirm workspace administrator rights, unless the migration is performed by a tenant administrator.
- Confirm sufficient Fabric CU quota in the target region.
- Install the Microsoft Fabric Capacity Metrics app before migration.
- Add capacity administrators to the new F SKU before assigning workspaces.
- For security-conscious customers, note that Microsoft now recommends least-privilege Azure permissions rather than automatically assigning broad Owner or Contributor access. A custom role can be limited to the necessary Microsoft.Fabric actions.
Fabric Licensing Guidance
Important licensing considerations:
- On F64 and larger skus , Fabric Free users with the Viewer role can view Power BI content.
- On F2 through F32 skus, every viewer needs Power BI Pro or PPU.
- Authors and editors still need Pro or PPU.
| P SKU | Starting F SKU |
|---|---|
| P1 | F64 |
| P2 | F128 |
| P3 | F256 |
| P4 | F512 |
| P5 | F1024 |
Same-Region vs. Cross-Region Migration
One of the first decisions in a Power BI Premium to Microsoft Fabric migration is whether the new Fabric capacity will be deployed in the same Azure region as the existing Power BI Premium capacity.
Same-Region Migration
For most organizations, the recommended approach is to provision the Fabric F SKU in the same Azure region as the existing P SKU and then reassign workspaces to the new capacity.
Microsoft identifies same-region migration as the simplest migration path because it avoids the item-mobility restrictions associated with moving workspaces between regions.
Cross-Region Migration
A cross-region migration requires additional planning because not every workspace item can move between Azure regions.
Items that can move across regions include:
- Reports
- Small-storage-format semantic models
- Dashboards
- Dataflow Gen1
- Paginated reports
- Datamarts
- Scorecards
Other item types must be removed before the workspace can be reassigned to a capacity in another region. This includes Fabric items such as Lakehouses, Warehouses, Notebooks, and Data Factory pipelines. Large-storage-format semantic models also require special handling as part of the migration.
Pay particular attention to Dataflow Gen2. After Dataflow Gen2 items are deleted, their underlying staging Lakehouse and Warehouse may become visible in the workspace. These staging items must also be removed before a cross-region reassignment can succeed.
Cross-Region Migration Warning
Do not treat a cross-region move as a standard P-to-F capacity reassignment. Before migrating, inventory every workspace and identify semantic-model storage formats and Fabric items that cannot move between regions. Back up required data or capture item definitions so that affected items can be recreated in the destination region.
If unsupported items remain in the workspace, the cross-region reassignment can fail.
For most P-to-F migrations, keep the initial migration in the same region unless there is a defined business, technical, or data-residency requirement to change regions. This reduces migration complexity and lets the organization separate the P-to-F capacity transition from a broader regional migration.
Migration Timeline
Day 0: Premium Subscription Ends
- Purchase or activate the required Fabric capacity (F-SKU).
- Reassign workspaces as soon as possible — don’t wait for the grace period to run out.
Days 1–30: Grace Period
- Your capacity keeps running at its current size, at no charge.
- This is your real migration window. Use it to reassign workspaces and validate.
- Validate migration:
- Workspace assignment and target capacity ID
- Reports and dashboards
- Semantic-model queries
- Scheduled refreshes
- Gateway connectivity and credentials
- Paginated reports
- Power BI apps and audiences
- Deployment pipelines and Git integration, where used
- Permissions, Viewer access, and licensing
- Capacity Metrics data
- Items still attached to the old capacity
- Warning banners indicating partial migration
- Active jobs canceled during reassignment
Days 31–90: Throttled Access
- Interactive operations are delayed (roughly a 20-second delay on submission).
- You can still export and recover data during this window — this is your last safe chance to get content out if migration has stalled.
- Prioritize migrating any content still on the old capacity to avoid further degradation.
Day 91 onward: Full Block
- All operations on the old capacity are rejected.
- Data is retained but inaccessible until the workspaces are migrated to an F-SKU or the old capacity is deleted.
- If you’re here, treat it as an outage: escalate to Microsoft or your account rep immediately.
Best Practices for a Successful Migration
- Thorough Planning & Discovery: Inventory all workspaces and assets, including personal and lesser-used ones. Clean up or archive redundant content.
- Phased Migration & Pilot First: Start with a pilot migration. Validate steps and resolve issues before proceeding in batches.
- Capacity Right-Sizing & Monitoring: Analyze current usage to choose the right F-SKU. Monitor capacity and scale as needed.
- Minimal Disruption: Schedule migrations during off-peak hours. Communicate plans and ensure workspaces are idle.
- Leverage Automation: Use Microsoft REST APIs and PowerShell cmdlets to bulk assign workspaces, reducing manual errors.
- Clean Up & Optimize: Archive or delete obsolete datasets and reports. Reorganize workspaces and set proper ownership.
- Enable New Features Thoughtfully: Roll out new Fabric capabilities gradually after core migration is stable.
- Robust Training & Change Management: Train admins and users, maintain open feedback channels, and provide documentation.
- Post-Migration Validation: Validate reports and data after each batch. Monitor system health and usage for several weeks.
Common Issues & How to Avoid Them
| Issue / Risk | Migration Strategy |
|---|---|
| Missing the 30-Day Window | Finish well before 30 days. Plan for 30 days or less, monitor progress, and escalate to Microsoft if needed. |
| Throttling After 30 Days (Old capacity slows down queries) | Migrate critical content in the first 30 days to prevent delays or failures. |
| Under-Sized Fabric Capacity | Analyze usage, right-size F-SKU, and scale up if needed. |
| Interrupted Refreshes/Queries (Active jobs canceled during move) | Migrate during off-hours, pause scheduled refreshes, and restart canceled jobs immediately. |
| Unmigrated “Orphan” Content | Track all workspaces and verify none are left on P-SKU. Confirm with owners. |
| User Confusion or Resistance (Adoption issues) | Communicate changes clearly, emphasize benefits, and offer training/support. |
Additional Resources
- Migrating from Power BI Premium to Microsoft Fabri… – Microsoft Fabric Community
- fabric-toolbox/monitoring/fabric-unified-admin-monitoring at main · microsoft/fabric-toolbox
- Automate your migration to Microsoft Fabric capacities | Microsoft Fabric Blog
Ready to migrate? Careful planning, phased execution, and robust communication are key to a successful transition to Microsoft Fabric. If you have questions or need support, leave a comment below!