Moving From Power BI Premium (P-SKU) to Fabric (F-SKU)
What to Expect After Switching
Microsoft is retiring Power BI Premium per-capacity licensing, the P-SKUs, and moving every customer onto Microsoft Fabric capacities, the F-SKUs. If your organization runs on a P1, P2, or P3, you will need to move, but the good news is that this is far less disruptive than it sounds: your reports and data stay put, most of your capabilities carry over, and you gain flexibility the old model never had. This guide explains what's changing, what stays the same, and how to move without a scramble.
01
What Is Retiring
Only one thing is going away: Power BI Premium per-capacity, the P1 through P5 SKUs. Microsoft is retiring those per-capacity SKUs and moving customers to Fabric F-SKUs. Power BI Pro, Premium Per User, and the embedded licenses are unaffected, so if you only use Pro or PPU, nothing changes for you at all.
02
The Good News: This Is Not a Data Migration
The word “migration” makes people picture moving terabytes and rebuilding reports. This isn’t that. Your workspaces, reports, semantic models, and data all stay exactly where they are. The move is a reassignment: you point your existing workspaces at a new Fabric capacity instead of the old Premium one. Nothing is rebuilt.
03
The SKU Mapping Is Direct
There’s no guesswork about which F-SKU you need. The compute maps one to one: P1 becomes F64, P2 becomes F128, P3 becomes F256, and so on up the line. Because the compute is equivalent at each tier, your workloads run the same, with no re-tuning required.
04
What This Really Is
It helps to reframe the move. At its heart, it’s a consolidation of Power BI Premium into the wider Fabric platform. Handled deliberately, most teams come out the other side with more capability, better cost control, and a cleaner Azure setup than they started with.
05
The Business Case in One Sentence
The move is mandatory, but it’s also an opening: the same capacity that runs your reports now unlocks the full Fabric platform and a billing model you can pause and scale, so a forced switch can leave you better off than before.
What Stays the Same
Start with the reassuring part, because most of what you rely on carries over untouched.
Your Reports and Data Don't Move
Every workspace, report, dataset, and dataflow stays where it is. You reassign the workspace to the new capacity; the contents come along without a rebuild.
Your Premium Features Carry Over
All the Power BI Premium capabilities remain available on Fabric: large semantic models, paginated reports, deployment pipelines, XMLA endpoints, dataflows, and advanced AI features. Nothing you paid for in Premium disappears.
Free Viewers at F64
The viewer economics carry over. At F64 and above, report viewers still need only a free license, exactly as they did on a P1. Your authors and editors still need Pro or PPU, also unchanged.
Your Pro and PPU Licenses
Per-user licensing is untouched. Everyone who has Power BI Pro or Premium Per User keeps it, and the retirement doesn’t require a single per-user license change.
What Changes
Now the real shifts, which are mostly improvements.
Billing Moves to Azure
This is the biggest change. F-SKUs are bought and billed through Azure, pay-as-you-go by default with the option to reserve for a discount, rather than the fixed monthly or annual commitment a P-SKU carried. Your capacity becomes an Azure resource.
You Can Pause and Scale
Because it’s an Azure resource, you can pause a capacity when it’s idle to stop billing, and scale it up or down at any time. A P-SKU was a fixed size for the whole term; an F-SKU flexes with your needs, which can cut real cost for workloads that don’t run around the clock.
The Capacity Is Now Shared Across Fabric
A P-SKU dedicated its compute to Power BI. An F-SKU’s capacity units are a shared pool that every Fabric workload draws on, Power BI, Data Factory, data engineering, warehousing, and real-time intelligence. That’s powerful, and it means you’ll want to watch consumption so one workload doesn’t starve another.
You Unlock the Full Fabric Platform
The same capacity that ran your Premium reports now runs the whole of Microsoft Fabric: lakehouses, warehouses, pipelines, Direct Lake, and Copilot. Capabilities you’d have bought separately, or gone without, are suddenly included in the compute you already have.
New Cost Factors
Two line items are new. Fabric bills OneLake storage separately, at a small per-gigabyte monthly rate, which P-SKU customers didn’t see. On the plus side, Fabric spend counts toward a Microsoft Azure Consumption Commitment, which P-SKU spend did not, so teams with an Azure commitment can offset the cost.
| Aspect | Power BI Premium (P-SKU) | Microsoft Fabric (F-SKU) |
|---|---|---|
|
Bought through |
Microsoft 365 / volume licensing |
Azure |
|
Billing |
Fixed monthly or annual commitment |
Pay-as-you-go or reserved, hourly |
|
Pause when idle |
No |
Yes, stop billing off-hours |
|
Scale up or down |
Fixed for the term |
Any time, in the Azure portal |
|
Capacity scope |
Power BI only |
All Fabric workloads share the pool |
|
Free viewers |
At P1 and up |
At F64 and up |
Almost every change on this list adds flexibility or capability. The one that needs active management is the shared capacity pool, since Power BI now competes with your other Fabric workloads for the same compute.
The Timeline You Need to Know
The deadlines are staggered, and missing yours has real consequences.
Sales and Renewals Already Ended
New P-SKU sales stopped in mid-2024, and customers without an Enterprise Agreement lost the ability to renew in early 2025. If you’re not on an EA, your clock is already running.
Your Deadline Is Your Renewal
There’s no single cutover date for everyone. Your P-SKU ends at your subscription’s renewal, so your deadline depends on your agreement. Enterprise Agreement customers have the most runway, but even that ends, so the safe move is to find your exact renewal date now rather than assume there’s time.
The Grace-Period Cliff
Here’s the part to plan around. If your P-SKU lapses before an F-SKU is in place, your content enters a grace period, then gets throttled, then blocked entirely.
The data is retained, but it becomes unreachable until you move to a capacity. The table shows the sequence.
| After Your P-SKU Ends | What Happens |
|---|---|
|
Days 1 to 30 |
Grace period, full access, no charge |
|
Day 31 onward |
Access throttled, operations slow down |
|
Day 91 onward |
Operations blocked; data retained but unreachable |
The whole cliff is avoidable with one rule: have the F-SKU running before the P-SKU ends, and none of this applies.
How to Move Without a Scramble
The migration is manual, and the order matters. Treated as a planned transition rather than a last-minute switch, it's routine.
Buy the F-SKU First
The cardinal rule: stand up the new Fabric capacity before you cancel the old P-SKU. Never let the P-SKU lapse first, that’s what triggers the grace-period cliff. Buy F, then move, then cancel.
Baseline Your Usage and Size the F-SKU
Before you buy, look at how your current capacity is used, peak load, refresh windows, concurrent users, so you pick the right F-SKU. The direct mapping (P1 to F64) is the safe default, but baselining tells you whether you can go smaller or should go larger.
Reassign Workspaces in Batches
Move workspaces to the new capacity in controlled batches rather than all at once, starting with the lowest-risk ones. Reassignment is quick, but batching lets you validate as you go and limits the blast radius if something needs attention.
Validate, Then Cancel the P-SKU
Once every workspace is on the F-SKU and confirmed working, cancel the P-SKU. Validating first means you never lose access, and cancelling last means you never pay for both at once longer than you must.
What This Move Is Not
A few misconceptions cause needless worry.
It Is Not Automatic
Microsoft won’t move you; the reassignment is manual. That’s a reason to plan ahead, not to wait, since nothing happens until you act.
It Is Not a Feature Downgrade
Everything Premium did, Fabric does, and then some. You keep your capabilities and gain the rest of the platform.
It Is Not Optional
P-SKUs are retiring, so this isn’t a change you can decline. The only choice you have is whether to do it calmly and early or under deadline pressure.
It Is Not a Reason to Panic
Read carefully, the scope is narrow and the mechanics are simple. Most of the anxiety around this retirement comes from assuming it’s bigger than it is.
Turn the Forced Move Into an Upgrade
The teams that come out ahead treat this as an opportunity rather than a chore. Since the same capacity now runs the full Fabric platform, the migration is a natural moment to adopt the workloads you've been meaning to try: a lakehouse for your raw data, Direct Lake for faster reports, Copilot for your analysts. It's also the moment to right-size, matching the F-SKU to real usage instead of inheriting an oversized commitment, and to use pause and reserved pricing to cut the bill. Handled well, a mandate to switch becomes a chance to modernize, ending up with more capability and better cost control than the P-SKU ever offered.
Taking the Next Step
Find Your Renewal Date
The single most useful thing you can do today is find exactly when your P-SKU agreement renews. That date is your real deadline, and everything else plans backward from it.
Model the Cost
Compare your current P-SKU cost against the equivalent F-SKU, factoring in reserved pricing, the pause option, and the new OneLake storage line. The number is often close, and the flexibility usually favors F.
Final Thoughts on the P-SKU to F-SKU Move
Moving from Power BI Premium to Fabric sounds like upheaval, but it’s a workspace reassignment with a deadline. Your reports stay, your features carry over, and you gain a flexible billing model and the full Fabric platform. Plan it around your renewal date, buy the capacity before you cancel the old one, and a forced migration turns into a straightforward upgrade.
Get an Outside Assessment
The hardest part is judging where your work truly centers and whether one platform or both serve it best. A neutral partner can keep that decision grounded in your real workloads and total cost rather than a vendor pitch.
Move to Fabric Smoothly With Allston Yale
If your Power BI Premium renewal is coming and you need to move to a Fabric capacity without disruption, the transition is manageable with a plan and risky without one. We’re a Texas Power BI and Microsoft Fabric consultancy, and our Power BI consulting helps you size the right F-SKU, sequence the move, and put the new Fabric capabilities to work, so you switch on time and come out ahead. Book a free data check-up with us today.