Aug 30, 2026

Are Power BI Embedded A SKUs Being Retired? What Actually Changed (and What Didn't)

ByPascal Kiefer

If you run Power BI Embedded on an A SKU, chances are someone on your team has asked: "isn't that being retired?"

It's an understandable question. Microsoft really is retiring Power BI capacity products and pushing customers toward Microsoft Fabric — and with product names as close as "Power BI Premium" and "Power BI Embedded", headlines about the one are easily read as news about the other.

So let's clear it up. The short answer: A SKUs are not being retired. What's actually retiring is Power BI Premium per-capacity — the P SKUs. Here's what's changing, what isn't, and what it means if you're choosing an embedding capacity today.

Where the confusion comes from

In March 2024, Microsoft announced the retirement of Power BI Premium per-capacity SKUs (P1–P5), directing customers to Microsoft Fabric F SKUs instead. "Power BI Premium is being retired" made the rounds — and for anyone running Power BI Embedded, that's uncomfortably close to home. Same product family, similar name, both capacity-based: it's easy to walk away believing your embedding capacity is on the same clock.

Adding to the muddle, the licensing analysts at Directions on Microsoft report that the original announcement did initially cover the Azure Power BI Embedded A SKUs too — before Microsoft quietly dropped that part of the plan without a reversal announcement.

Whatever you heard and whenever you heard it, the situation today is clear: the retirement that is actually in effect applies to the Premium P SKUs, and the Azure Power BI Embedded A SKUs are untouched.

What is actually retiring: the Premium P SKUs

The retirement that is happening affects Power BI Premium per-capacity subscriptions (P1–P5):

• July 1, 2024 — P SKUs were removed from the purchase flow for new customers.
• January 1, 2025 — existing customers without an Enterprise Agreement could no longer renew; Enterprise Agreement customers transition when their current agreement term ends.
• The migration path is a suitable Fabric F SKU, which offers more capacity sizes, pay-as-you-go billing, and can count toward Azure spend commitments.

If you're on a P SKU, this transition is real and worth planning — Microsoft's grace-period post covers the timeline details. But it's a Premium story, not an Embedded one.

What stays: the A SKUs

The Power BI Embedded A SKUs (A1–A6) remain available in Azure, unchanged:

• Billed hourly, pay-as-you-go, with no commitment.
• They can be paused when not in use — a dev or test capacity that runs only during business hours costs a fraction of an always-on one.
• Fully supported for embedding scenarios, with no forced migration and no announced end date.

If your embedding workload runs happily on an A SKU today, nothing about the P SKU retirement requires you to touch it.

A SKU or F SKU for a new project?

The real question in 2026 isn't "do I have to leave A SKUs?" — it's "which one should a new embedding project start on?" Both work with the Embedsy Portal, and both embed Power BI content the same way. The differences that matter:

Choose an A SKU when embedding is all you need

If your capacity exists purely to serve embedded Power BI reports, the A SKU is the simpler product: hourly billing, pausable, and sized in familiar A1–A6 steps. For small and mid-sized embedding workloads — especially ones that don't run around the clock — it's often the most cost-effective option. Our pricing guide compares the numbers in detail.

Choose an F SKU when you want the Fabric platform

F SKUs are full Microsoft Fabric capacities: alongside embedding, they include the whole Fabric workload family — and some newer capabilities are Fabric-only. The most relevant one for embedding: Direct Lake semantic models require a Fabric capacity and don't run on A SKUs. F SKUs start small (F2), bill pay-as-you-go like A SKUs, and additionally offer reservation pricing that can cut costs significantly for always-on workloads. Strategically, F SKUs are also clearly where Microsoft's investment is going.

A reasonable rule of thumb: pure embedding with predictable, modest needs — A SKU. Anything touching the broader Fabric ecosystem, Direct Lake, or an always-on production workload that can benefit from reservation pricing — F SKU. And because the Embedsy Portal treats capacity as configuration, moving from one to the other later is a settings change, not a rebuild — see the capacity documentation.

The takeaway

No, Power BI Embedded A SKUs are not being retired. The Premium P SKUs are what's going away, and their replacement (Fabric F SKUs) is also the strategic home for new embedding investment. Existing A SKU deployments can carry on as they are; new projects should make a deliberate A-vs-F choice rather than assuming either is mandatory.

If you're weighing that choice for a customer-facing analytics portal, that's exactly the decision we help with: book a free demo and bring your capacity questions.

Get started

Book a free demo Start free trial