Listen to this blog
Microsoft’s Power BI Premium retirement is far beyond a licensing update. For enterprises running business-critical analytics on Power BI Premium capacity, timely decisions are required around migration, capacity planning, cost management, governance, and operational continuity.
Microsoft is retiring Power BI Premium per-capacity P SKUs and directing customers toward Microsoft Fabric capacity. Organizations that still use P1 through P5 capacities should assess their current environment and plan their transition before their existing agreement expires.
Here is what is changing, and how enterprises can prepare.
What does Power BI Premium retirement mean?
The announcement does not mean Power BI Premium capabilities are disappearing. It specifically applies to Power BI Premium per-capacity P SKUs.
Power BI Pro, Power BI Premium Per User and Power BI Embedded A and EM SKUs are not currently included in this retirement. Sovereign cloud customers are also unaffected until Microsoft Fabric becomes available in those environments.
For organizations using P SKUs, Microsoft Fabric F SKUs are designated replacements. Fabric incorporates existing Power BI capabilities while adding services for data integration, engineering, warehousing, data science, real-time intelligence, and AI within a unified analytics platform.
Microsoft stopped selling new P SKU capacity in 2024. Existing P SKU subscriptions now end according to the customer’s current agreement terms. Enterprise Agreement customers may continue renewing eligible capacity annually until their agreement ends, but should confirm their specific position with their Microsoft account representative.
Source: Power BI Premium to Microsoft Fabric Migration Overview - Power BI | Microsoft Learn
Understand the retirement timeline
There is no single Power BI Premium retirement date that applies identically to every enterprise. The effective deadline depends on the organization’s subscription and agreement end date.
According to Microsoft’s current guidance, the following stages begin once an eligible P SKU subscription expires:
- Days 1–30: The capacity continues operating at its existing size during a free grace period.
- Days 31–90: Access is throttled, and interactive operations may be delayed.
- Day 91 onward: Operations are rejected. The data is retained but becomes inaccessible until the workspaces are moved to an F SKU or the old capacity is deleted.
The grace period should be treated as a safety net, not as a planned migration window. Enterprises should complete their Power BI Premium to Microsoft Fabric migration before their P SKU subscription ends.
What replaces Power BI Premium capacity?
Microsoft Fabric F SKU capacity replaces the retiring P SKU model. The closest compute-based mappings are:
This is a capacity-unit comparison, not a guarantee that every enterprise should select the equivalent Microsoft Fabric F SKU.
Organizations should review actual consumption, peak utilization, refresh schedules, concurrency, and anticipated growth before choosing a capacity. Planned Fabric workloads, including lakehouses, warehouses, notebooks, and pipelines, must also be included in the calculation.
Simply replacing P1 with F64 without analyzing demand could lead to unnecessary expenditure or insufficient capacity.
What changes after migration?
For most users, the Power BI experience remains familiar. Reports, dashboards, semantic models, workspaces and apps can continue operating after reassignment to suitable Fabric capacity.
Behind the scenes, however, several commercial and operational changes require attention.
Purchasing and billing
P SKUs were generally purchased through Microsoft 365 agreements. F SKUs are Azure resources and can be purchased using pay-as-you-go pricing or capacity reservations.
Pay-as-you-go billing offers flexibility to scale, pause or resume capacity. Reservations can provide better economics for steady, predictable workloads. Fabric spending may also count toward an organization’s Microsoft Azure Consumption Commitment.
Capacity management
Fabric allows organizations to resize capacity through Azure. Unlike Power BI Premium autoscale, F SKUs rely on manual, API-driven or automated scaling approaches rather than the same built-in autoscale model.
Enterprises should establish monitoring, budget alerts, and consumption guardrails before moving production workloads.
User licensing
User licenses do not automatically change because of migration. However, capacity size affects content consumption.
On F64 and larger capacities, users with a Fabric Free license and the Viewer role can view Power BI content. On F2 through F32, report viewers generally need Power BI Pro or Premium Per User licenses. This distinction can significantly influence the total cost of ownership.
Power BI Report Server
Organizations using Power BI Report Server should verify their licensing before cancelling a P SKU. Report Server rights are available through an eligible Fabric capacity reservation of F64 or higher or through SQL Server Enterprise Edition with Software Assurance.
How should enterprises approach the migration?
The technical move is primarily performed by reassigning workspaces from P SKU capacity to F SKU capacity. But enterprise environments often contain hundreds or thousands of workspaces, complex dependencies and varying business-criticality.
A structured migration should include five stages.
1. Inventory the existing environment
Create an inventory of capacities, workspaces, semantic models, reports, refresh schedules, gateways, administrators, and business owners. Identify Fabric items and large semantic models that could need special handling.
2. Establish a performance baseline
Use the Microsoft Fabric Capacity Metrics app to understand current utilization, peak periods, throttling, and refresh demand. Include expected workload and user growth when estimating future capacity.
3. Select and provision the F SKU
Choose the target region, capacity size, and billing model. Provision the new F SKU before reassigning workspaces and keeping the existing P SKU active until testing is complete.
4. Pilot and migrate in waves
Begin with a representative but non-critical workspace. Validate access, security, reports, gateways, refreshes and performance before migrating larger batches.
Workspace reassignment can interrupt active queries or refresh jobs, so migrations should be scheduled outside critical processing windows. Microsoft also provides a capacity migration notebook for automating large-scale workspace transfers.
Source: Automate your migration to Microsoft Fabric capacities | Microsoft Fabric Blog
5. Validate before decommissioning
Confirm that all workspaces have moved successfully and compare performance against the original baseline. Monitor consumption through a full business cycle wherever possible, including month-end or other high-demand periods.
Only cancel the P SKU after reports, refreshes, gateways, permissions, and dependent processes have been thoroughly validated.
Avoid turning migration into uncontrolled modernization
The Power BI Premium licensing changes create an opportunity to modernize enterprise analytics, but migration and modernization should not become one large, high-risk program.
Moving to Fabric capacity is the immediate priority. Consolidating capacities, changing regions, redesigning semantic models or adopting new Fabric workloads can introduce additional complexity. Where possible, complete and stabilize the licensing migration first, then pursue modernization through separate, carefully governed workstreams.
From mandatory migration to measurable value
Power BI Premium retirement creates a firm reason to act, but the transition does not need to be purely defensive.
With the right approach, enterprises can use the move to improve capacity visibility, introduce stronger cost controls, and build a foundation for unified analytics across Power BI and Microsoft Fabric.
The key is to start before the subscription deadline. Assess the current environment, select capacity based on evidence, migrate in controlled waves, and validate before decommissioning the old platform.
Prepare for Power BI Premium retirement with a migration strategy built around continuity, cost and long-term value. Talk to Visionet’s Microsoft data and analytics experts.
Frequently asked questions (FAQs)
1. Is Microsoft retiring Power BI Premium completely?
No. Microsoft is retiring Power BI Premium per-capacity P SKUs. Power BI Pro and Premium Per User will continue.
2. When should enterprises migrate from Power BI Premium?
Enterprises should migrate before their current P SKU agreement expires to avoid service disruption.
3. What replaces Power BI Premium P SKUs?
Microsoft Fabric F SKUs replace P SKU capacity. For example, F64 is the closest equivalent to P1.
4. Will existing reports need to be rebuilt?
Usually not. Most organizations can move their workspaces to Fabric capacity without rebuilding existing Power BI reports.
5. What should enterprises do first?
Review current capacities, workspaces, usage and renewal dates. Then create a phased migration plan based on actual business needs.
Ready to move from insight to action?
Whether you’re exploring new opportunities, solving operational challenges, or planning your next stage of growth, Visionet can help you move forward with clarity and confidence.
Speak with our experts to explore how we can support your business goals.
