Power BI Pro and PPU prices go up in April 2025: what to check now

Power BI is getting more expensive. Microsoft has announced that from April 1, 2025, Power BI Pro will cost USD 14 per user per month and Premium Per User (PPU) will cost USD 24 per user per month. According to the announcement, this is the first pricing update since Power BI launched nearly ten years ago.

For most organisations, Power BI licences are a line item nobody has looked at closely for years. That is exactly why this change deserves an hour of attention now, while you still have months before it lands on an invoice.

What Microsoft announced

The new list prices are simple:

• Power BI Pro: USD 14 per user per month.
• Power BI Premium Per User: USD 24 per user per month.

The increase applies globally to new and existing commercial customers, upon renewal as of April 1, 2025. Other currencies will be priced comparably, so if you pay in Danish kroner or euros, expect a matching change rather than the exact dollar figure.

Microsoft frames the change around a decade of product work: more than 1,500 updates across the Power BI portfolio in the last six years, and a platform used by more than 350,000 organisations. You can agree or disagree with the argument. The invoice changes either way.

Who is affected, and when

The timing depends on how you buy. The announcement splits it into three groups:

• New customers. Commercial customers buying Pro or PPU after April 1, 2025 contract at the new price.
• Existing Enterprise Agreement customers with standalone Pro or PPU keep their current price until their next renewal. New agreements signed after April 1, 2025 use the new price.
• Microsoft 365 E5 and Office 365 E5 annual term subscriptions with annual billing see no pricing change. If your users get Pro through E5, this announcement does not touch them.

The key word is renewal. If your agreement renews in, say, mid 2025, the new price arrives then, not on April 1. Find your renewal date before you do anything else.

When an F64 capacity starts to make sense

This is the question I expect to hear most in the coming months. Capacity licensing works differently from per-user licensing, and the difference matters more when per-user prices rise.

The rule from the Fabric licensing documentation is this: on a Fabric capacity of F64 or larger, users with only a free licence and a viewer role on the workspace can view Power BI content. On F SKUs smaller than F64, every user viewing Power BI content still needs Pro, PPU or an individual trial.

Two details are easy to miss:

1. Creators still need Pro. To create and share Power BI items in a workspace other than My workspace, a user needs Pro or PPU, even on a large capacity. F64 removes the licence cost for viewers, not for report builders.
2. F2 to F32 do not remove the viewer licence. A small capacity is useful for Fabric workloads, but it does not change who needs a paid Power BI licence to read a report.

So the break-even calculation is about viewers. Take the monthly price of an F64 in your region (pay-as-you-go or reserved, from the Azure pricing page) and divide it by 14. That gives you roughly how many viewer-only Pro licences the capacity has to replace before it pays for itself on licences alone. A reservation lowers that number, since Microsoft quotes savings of around 41 percent compared with pay-as-you-go.

If you are far below that number, staying on Pro is still the sensible choice. If you are close to it, F64 becomes interesting, because you also get dedicated compute and the rest of Fabric. Just do not buy a capacity only to avoid a licence increase without checking whether your workloads fit inside it.

What PPU users should think about

PPU is now USD 10 more per user than Pro. That gap is the price of features such as larger semantic models, 48 refreshes per day, XMLA endpoint read and write, and deployment pipelines.

Remember that in a PPU workspace, everyone who accesses the content needs a PPU licence. A PPU workspace with a handful of builders and many readers gets expensive quickly. For that pattern, it is worth comparing PPU against F64 with Pro builders.

What to do next

A practical review you can finish before your renewal:

1. Find your renewal date and how you buy (EA, CSP, direct, or through E5).
2. Export your licence assignments from the Microsoft 365 admin center and count Pro and PPU users.
3. Split users into builders and viewers. Builders publish and share. Viewers only read. Most organisations have far more of the second group.
4. Look for inactive licences. People who changed roles or left still hold licences surprisingly often. Removing them is the cheapest saving you will find.
5. Check who actually needs PPU. If a user does not use a PPU workspace or premium features, Pro may be enough.
6. Run the F64 break-even for your viewer count, using your own region and currency.
7. Budget for the new price at renewal, even if you plan changes. Licence changes take longer than you expect.

None of this is complicated. It just needs someone to own it.

Takeaway

After two decades in data, I have seen the same pattern many times: licences get bought in a hurry and reviewed never. A price increase is an annoying but useful reason to clean up. Count your builders and viewers, find the inactive seats, and only then decide whether Pro, PPU or capacity fits best.

When is your Power BI renewal, and do you know how many of your licensed users actually build reports?

Sources

• Important update to Microsoft Power BI pricing (Power BI blog)
• Understand Microsoft Fabric licenses and capacity (Microsoft Learn)
• Power BI pricing (Microsoft)
• Microsoft Fabric pricing (Azure)