Power BI Premium → Fabric F-SKU Migration: 90-Day Enterprise Playbook with Cost Modeling

TL;DR

• The Power BI Premium → Fabric F-SKU migration is the dominant capacity decision for enterprises with active Premium contracts. Microsoft's product investment is concentrated on F-SKUs; Premium-only features will drift over time.
• The migration is not a license change — it is a capacity-model transition with different consumption characteristics, different operational discipline, and different cost structure.
• The 90-day playbook sequences: capacity-consumption baseline, F-SKU sizing analysis, pilot, governance overlay, workspace-by-workspace cutover, and decommissioning.
• Cost modeling typically shows F-SKU as cheaper for workloads with substantial off-hours pause/resume opportunity and more expensive for 24/7 continuous workloads. The actual answer requires modeling against the specific tenant's consumption pattern.
• This guide details the migration sequencing, the cost modeling, and the operational handover for enterprise Premium → F-SKU migrations.

Executive Summary

For enterprises holding Power BI Premium P-SKU contracts approaching renewal, the migration to Fabric F-SKU is more than a capacity-model decision. F-SKU unlocks Copilot, Real-Time Intelligence, Data Activator, and the broader Fabric capabilities that P-SKU does not provide. F-SKU also introduces pay-for-what-you-use billing with pause-and-resume capability — a substantial change from P-SKU's fixed monthly cost.

This guide details the 90-day migration playbook EPC Group has refined across Fortune 500 Premium-to-Fabric migrations.

The 90-Day Playbook

Days 1–15: Capacity-Consumption Baseline

Before any F-SKU is provisioned:

1. Install the Fabric Capacity Metrics app on the existing Premium capacity.
2. Run for at least 30 days to baseline peak hour, average hour, day-of-week patterns.
3. Identify top consuming workspaces and reports.
4. Capture background-operation consumption (refreshes).
5. Identify throttling events.

The baseline is the only honest way to size F-SKU.

Days 16–25: F-SKU Sizing Analysis

Based on the baseline:

1. Calculate the F-SKU capacity that matches peak consumption with appropriate headroom.
2. Cost-model F-SKU vs continuing P-SKU.
3. Identify off-hours pause/resume opportunities.
4. Calculate cost crossover under different operational scenarios.
5. Recommend the target F-SKU size and operational pattern.

Days 26–35: Pilot

1. Provision a pilot F-SKU (typically smaller than the production target).
2. Move 2–3 representative workspaces.
3. Validate performance parity.
4. Validate capacity-consumption tracking against expectations.
5. Validate Copilot enablement.
6. Validate audit-log routing.

Days 36–50: Governance Overlay

1. Update workspace-to-capacity assignment policies for F-SKU.
2. Document capacity pause/resume policy.
3. Document throttling response runbook.
4. Update chargeback model for the consumption-based billing.

Days 51–80: Workspace Cutover

1. Move workspaces from P-SKU to F-SKU in a defined sequence.
2. Sequence: governed-finance workspaces first, operational workspaces next, self-service last.
3. Each cutover is a workspace-administrator setting change.
4. Validation window after each wave.

Days 81–90: Decommission and Stabilize

1. After all workspaces migrated and validation windows passed.
2. Decommission the P-SKU.
3. Coordinate with the contract renewal calendar.
4. Stabilization period for the F-SKU operational pattern.

Cost Modeling

F-SKU vs P-SKU comparison

The cost crossover depends on the workload pattern:

Workload pattern	F-SKU advantage
24/7 continuous high utilization	Usually P-SKU cheaper
Business-hours only (50% of week)	F-SKU cheaper with pause/resume
Variable seasonal demand	F-SKU cheaper (scale up/down)
Heavy Copilot consumption	F-SKU only (P-SKU can't host)
Multi-region with regional capacity	F-SKU more granular

Pause/resume calculations

F-SKU pause/resume saves money only if the workload is actually paused. Common pause windows:

• Nights and weekends (40-50% of week paused).
• Weekend-only pause (30% paused).
• Off-business-hours pause within the week (varies).

The savings calculation is: (paused-hours / total-hours) × F-SKU hourly rate. Even modest pause windows produce material savings against 24/7 P-SKU cost.

Capacity expansion economics

F-SKU supports easy capacity expansion. Common patterns:

• Month-end batch workloads run on temporarily-expanded F-SKU.
• Seasonal demand peaks scaled up; scaled back after.
• Copilot enablement scaling.

The expansion economics typically favor F-SKU for workloads with predictable peak periods.

Multi-capacity architectures

For very large workloads exceeding single-capacity bounds, multi-capacity F-SKU architecture supports workload isolation. Each capacity sized to its workload; cross-capacity workspaces use Composite Power BI models. Cost is the sum of capacity costs.

Operational Pattern Differences

From P-SKU to F-SKU operational discipline

P-SKU operation: fixed capacity, set-and-forget after initial sizing.

F-SKU operation: continuous capacity-consumption monitoring, periodic right-sizing, pause/resume orchestration, capacity-expansion-and-contraction discipline.

The shift requires team capability development. Without the operational discipline, F-SKU's cost benefits don't materialize.

Chargeback model

P-SKU chargeback typically allocates the fixed monthly cost across business units. F-SKU chargeback can reflect actual consumption, but this exposes consumption variation that may be uncomfortable for business units accustomed to flat allocation.

The conversation with finance and business units about the chargeback model needs to happen before the migration, not after the first F-SKU bill.

Audit and compliance

F-SKU audit and compliance work the same as P-SKU at the Power BI level. New Fabric-specific workloads (Copilot, Real-Time Intelligence) add their own audit and compliance surfaces.

Migration Sequencing by Workspace Type

Tier 1: Governed-Finance Workspaces

Migrate first. These workspaces are typically slow-changing, well-governed, and lowest-risk. The migration validates the pattern.

Tier 2: Operational Workspaces

Migrate next. These workspaces have more activity but are still well-governed. The migration tests under broader operational load.

Tier 3: Self-Service Workspaces

Migrate last. These workspaces have the most variation and require the most adoption support. The migration completes the transition.

Common Pitfalls

1. Provisioning F-SKU at P-SKU equivalent size. P-SKUs are typically oversized; F-SKUs should be right-sized.
2. Skipping the consumption baseline. Sizing without the baseline is guessing.
3. Underestimating Copilot consumption. Copilot adds substantial capacity demand.
4. Mixing P-SKU and F-SKU in production too long. Set a target end date.
5. Forgetting Power BI Report Server (PBIRS). PBIRS doesn't migrate to F-SKU; it requires its own modernization plan.
6. Not adjusting the chargeback model. Consumption-based billing exposes variation that flat allocation hides.

Frequently Asked Questions

What is the Power BI Premium → Fabric F-SKU migration?

The migration is the capacity-model transition from Power BI Premium (P-SKU) to Microsoft Fabric (F-SKU). The migration is at the capacity level — workspaces move from P-SKU capacity to F-SKU capacity. The Power BI workload itself continues to function.

Why migrate from Premium to Fabric?

Microsoft's product investment is concentrated on F-SKUs. F-SKU unlocks Copilot, Real-Time Intelligence, Data Activator, and other Fabric capabilities not available on P-SKU. P-SKUs are not formally end-of-life but feature drift is expected over time.

Is F-SKU cheaper than P-SKU?

It depends on the workload pattern. F-SKU is typically cheaper for workloads with substantial off-hours pause/resume opportunity. P-SKU may be cheaper for 24/7 continuous workloads. Detailed cost modeling against the specific tenant's pattern is required.

How do I size an F-SKU capacity?

Run the Fabric Capacity Metrics app on the existing Premium capacity for at least 30 days. Identify peak consumption, average consumption, and throttling events. Size the F-SKU to match peak with appropriate headroom. Validate during pilot.

What is the typical migration timeline?

The standard 90-day playbook covers capacity baseline, sizing analysis, pilot, governance overlay, workspace cutover, and decommissioning. Larger enterprises may extend; smaller enterprises may compress.

Can I run P-SKU and F-SKU simultaneously?

Yes. Most migrations run both in parallel during the cutover window (typically 6–12 weeks). Workspaces move from P-SKU to F-SKU as the migration progresses.

What about Power BI Report Server (PBIRS)?

PBIRS does not migrate to F-SKU. PBIRS workloads require a separate modernization plan — typically migrating to Power BI Service or Fabric.

How does the migration affect users?

The migration is a capacity-administrator change. Workspace users experience no functional change; the workspace continues to function on the new capacity. Performance characteristics may shift; validation windows confirm parity.

How does the chargeback model change?

F-SKU's consumption-based billing exposes variation that flat P-SKU allocation hides. Business units that consume more pay more under a consumption-based model. The chargeback model conversation should happen before the migration.

What is the role of Fabric Capacity Metrics app?

The Capacity Metrics app provides operational visibility into capacity consumption. It is the foundation for sizing decisions, pause/resume planning, and throttling diagnosis.

How does Copilot enablement affect F-SKU sizing?

Copilot consumes capacity units. Enabling Copilot tenant-wide typically requires F-SKU sizing increment over the baseline. The sizing model should explicitly include Copilot.

What is the relationship between F-SKU and the rest of Microsoft Fabric?

F-SKU is the capacity unit for Microsoft Fabric. The same capacity hosts Power BI semantic models, Fabric Lakehouse, Fabric Warehouse, Eventhouse, Real-Time Intelligence, and Copilot workloads. Capacity sizing should account for all Fabric workloads running on it.

Can workspaces span multiple F-SKU capacities?

A workspace is assigned to exactly one capacity at a time. For very large workloads, multi-capacity architectures with separate workspaces handle the scale.

How does EPC Group support Premium → F-SKU migrations?

EPC Group works with Fortune 500 enterprises on Premium → F-SKU migrations. The standard 90-day engagement covers the playbook from baseline through decommissioning. Our consultants — including Microsoft Press bestselling author Errin O'Connor — bring direct migration experience.

What is the typical cost-savings range from a Premium → F-SKU migration?

Cost savings vary by workload pattern. Common ranges: 20-40% savings for workloads with substantial off-hours pause/resume opportunity; cost-neutral or slightly higher for 24/7 continuous workloads. Detailed modeling against the specific tenant's pattern is required.

Next Steps

If your enterprise is approaching a Power BI Premium contract renewal:

1. Install the Fabric Capacity Metrics app and run for 30 days.
2. Calculate the F-SKU sizing recommendation.
3. Cost-model F-SKU vs P-SKU continuation.
4. Plan the 90-day migration playbook.
5. Engage a partner with deep Premium → F-SKU migration experience.

EPC Group has 29 years of enterprise Microsoft consulting experience and is Microsoft Solutions Partner with the core designations. We were historically the oldest continuous Microsoft Gold Partner in North America from 2016 until the program's retirement. Our consultants — including Microsoft Press bestselling author Errin O'Connor — bring direct Premium → F-SKU migration experience across many Fortune 500 enterprises. To discuss your migration, contact EPC Group for a 30-minute discovery call.