Power Platform licensing explained

Power Platform licensing is famously confusing, partly because the model has changed several times, partly because it spans four products (Power Apps, Power Automate, Power BI, Power Pages, plus Copilot Studio and Dataverse). A clear map saves a lot of money and angry calls to Microsoft.

What's "free" with Microsoft 365

Microsoft 365 subscriptions include limited Power Platform usage:

• Power Automate — cloud flows using standard connectors only (in-suite: Outlook, SharePoint, Teams, Office, etc.), with per-user run allowances.
• Power Apps — canvas apps using standard connectors, no Dataverse.
• Power BI — read-only access to reports shared with you, plus authoring of personal workspaces (Pro is required to share with others).

This is enough for many simple scenarios but it's strictly limited. The moment you reach for SQL, HTTP, on-premises gateway, Dataverse, or anything premium, you need additional licensing.

Standalone licensing

The main standalone SKUs:

• Power Apps Premium — per-user, per-month. Unlimited custom apps, Dataverse, premium connectors. The default for serious citizen developers.
• Power Apps per-app — licence specific users for specific apps. Better when many users use one app.
• Power Automate Premium — premium connectors, unlimited flows, business process flows.
• Power Automate Process — unattended RPA, per-bot.
• Power Pages — per authenticated user or per anonymous user per site.
• Copilot Studio Messages — billed in packs of messages.
• AI Builder credits — for OCR, document parsing, prediction models.
• Power BI Pro — per-user, sharing rights.
• Power BI Premium Per User (PPU) — per-user, premium features.
• Microsoft Fabric capacity (F-SKUs) — capacity-based, replaces Power BI Premium P-SKUs.

Pay-as-you-go

For unpredictable workloads, pay-as-you-go plans bill against an Azure subscription:

• Power Apps PAYG — per active user per month.
• Power Automate PAYG — per cloud flow run.
• Copilot Studio PAYG — per message.

PAYG is often cheaper for sporadic use and trivial for enterprise IT to administer. The trade-off is forecasting cost.

Capacity-based items

Some products license by capacity, not user:

• Dataverse database capacity (in GB) — pooled across the tenant.
• Dataverse file capacity.
• Dataverse log capacity.
• Fabric capacity (F-SKUs, scaling by compute units).

Tenants get a small default allocation; large estates buy more.

How to plan licensing

A pragmatic approach:

1. Inventory what's being built today (use the CoE Starter Kit).
2. Classify each app/flow as standard-only or premium.
3. Identify users of premium content.
4. Compare per-user vs per-app vs PAYG for each premium scenario.
5. Negotiate at Microsoft renewal — Power Platform licences are commonly part of EA discussions.

The biggest cost trap is viral adoption — citizen developers build apps that quietly need premium connectors, and the licence requirement creeps up. The CoE Toolkit's monitoring is essential for catching this early.

For most Microsoft 365 customers, Power Platform pays back many times over once the licensing is sorted. Don't let the model deter you — just plan deliberately.