Power Platform Licensing Guide 2026: What You Actually Need to Know

Why Licensing Still Trips Everyone Up

Power Platform licensing has never been simple, but 2026 has brought a fresh wave of changes that caught many organisations off guard. Between the end-of-sale of Per App plans, the shift from AI Builder credits to Copilot credits, and evolving Microsoft 365 entitlements, even experienced IT admins are second-guessing their licence assignments.

This guide covers the current state of affairs as of March 2026. We will walk through what has changed, what it costs, and — most importantly — how to avoid the mistakes we see organisations make repeatedly.

The Big Changes You Need to Know About

Per App Plan: End of Sale

Microsoft officially ended new sales of the Power Apps Per App plan in January 2025. If you had existing Per App subscriptions, they will continue to renew at their current terms until the end of their agreement period, but you cannot purchase new ones.

This matters because Per App was the go-to recommendation for organisations with a small number of apps and a large user base. The replacement strategy depends on your situation:

Small user count, many apps: Power Apps Premium (per user) is the natural successor
Large user count, few apps: Consider Power Apps Pay-as-you-go, which charges per active user per app per month
Mixed scenario: A combination of Premium licences for power users and Pay-as-you-go for occasional users

Per User Pricing (Current as of March 2026)

Here is a summary of the primary standalone plans:

Plan	Price (USD/user/month)	What You Get
Power Apps Premium	$20	Unlimited apps, Dataverse, premium connectors, 5000 Copilot credits/month
Power Automate Premium	$15	Unlimited cloud flows, premium connectors, AI Builder (via Copilot credits), attended RPA
Power Automate Process	$150/bot	Unattended RPA bot, cloud flows, premium connectors
Copilot Studio	$200	25,000 messages/month, autonomous agents, generative AI

These prices are list prices. Enterprise Agreement and CSP pricing will differ — check with your Microsoft partner for actual rates.

Copilot Credits: The New Currency

This is the change that causes the most confusion. Microsoft is transitioning from the old AI Builder credits model to a unified Copilot credits system. The key dates:

Already live: Copilot credits are included in Power Apps Premium and Power Automate Premium licences
November 2026: AI Builder credits are fully deprecated and converted to Copilot credits
Now through November 2026: Both systems run in parallel, with automatic conversion

Copilot credits are consumed by AI-powered features across the platform:

AI Builder model training and predictions
Copilot in Power Apps (app generation, formula assistance)
Copilot in Power Automate (flow generation, expression help)
Copilot Studio message processing
AI Prompts in Power Automate

The allocation is straightforward but the consumption rates vary wildly depending on the feature. A simple AI Builder text extraction might consume 1 credit, while a Copilot Studio conversation with generative answers can consume 5-50 credits depending on complexity and knowledge source size.

Practical tip: Monitor your credit consumption in the Power Platform Admin Centre under Billing > Copilot credits before November 2026 to understand your actual usage patterns.

What Is Included in Microsoft 365

This is where most licensing mistakes happen. Microsoft 365 E3/E5, Business Basic/Standard/Premium all include some Power Platform entitlements, but they are limited:

Microsoft 365 Seeded Entitlements

Power Apps for M365: Run apps that use standard connectors and Microsoft Dataverse for Teams. No premium connectors, no full Dataverse, no custom connectors.
Power Automate for M365: Run cloud flows with standard connectors in the context of M365 services. No premium connectors, no attended RPA, no AI Builder.
Copilot Studio for M365 (with M365 Copilot licence): Build copilots within Teams. No autonomous agents, limited customisation.
Power Pages: Not included in any M365 plan.
Dataverse for Teams: Included. Full Dataverse: Not included.

The “Context of M365” Trap

The seeded Power Automate licence is scoped to “within the context of Microsoft 365.” In practice, this means your flow must be triggered by and primarily interact with M365 services (Outlook, SharePoint, Teams, etc.). A flow triggered by a button in a canvas app that writes to Dataverse is not “in the context of M365” and requires a standalone licence.

Microsoft has not published an exhaustive list of what counts. The general rule of thumb:

Triggered from M365 service (SharePoint, Outlook, Teams) → likely covered
Uses only standard connectors to M365 services → likely covered
Triggered from Power Apps → needs standalone licence
Uses premium or custom connectors → needs standalone licence
Uses Dataverse (not Dataverse for Teams) → needs standalone licence

When in doubt, buy the standalone licence. An audit finding is far more expensive than the monthly per-user cost.

Premium vs Standard Connectors

The connector tier determines whether you need a premium licence. Common sources of confusion:

Connectors That Surprise People by Being Premium

Dataverse (full, not “for Teams”): Premium
SQL Server: Premium
Azure Blob Storage: Premium
HTTP with Microsoft Entra ID: Premium
Adobe PDF Services: Premium
Approvals (the connector, not the action in flows): Standard — this one surprises people the other way

Connectors That Are Standard but Feel Premium

SharePoint: Standard
Outlook 365: Standard
Microsoft Teams: Standard
OneDrive for Business: Standard
Excel Online: Standard
Approvals: Standard

Key insight: A single premium connector anywhere in an app or flow means every user of that app or flow needs a premium licence. There is no “premium for just that one connection” option.

Common Licensing Mistakes

After working with dozens of organisations on Power Platform governance, these are the mistakes we see most frequently:

1. Assuming M365 Covers Everything

“We have E5 licences, so Power Platform is included.” Partially true — but the seeded entitlements are severely limited. The moment you connect to SQL Server, use Dataverse, or build anything beyond basic M365 automation, you need standalone licences.

2. Licence Stacking Confusion

A user with Power Apps Premium does NOT automatically get Power Automate Premium. If that user builds a flow with premium connectors outside of a Power App, they need a separate Power Automate licence.

However, flows that are triggered from within a Power App and run in the context of that app are covered by the Power Apps licence. The distinction is “in the context of the app” vs “standalone flow.”

3. Ignoring the Multiplexing Rule

If you build a Power App that serves external users (e.g., a portal), you cannot buy one licence and share it. Every individual who benefits from the service needs a licence, even if they access it indirectly. This is the “multiplexing” clause and it catches organisations building customer-facing solutions.

For external-facing scenarios, consider Power Pages (which has its own per-website and per-login pricing model) or Pay-as-you-go pricing.

4. Forgetting About Environment Add-ons

Dataverse database and file capacity is allocated at the tenant level, not per user. Your initial allocation depends on the number and type of licences in your tenant. If you run out, you need to purchase additional capacity separately.

Default allocations (per tenant):

Base: 10 GB database + 20 GB file
Per Power Apps Premium user: +250 MB database + 2 GB file
Per Power Automate Premium user: +100 MB database + 2 GB file

This adds up quickly for organisations with lots of Dataverse data. Monitor capacity in the Admin Centre regularly.

5. Not Planning for Copilot Credits

Organisations that embraced AI Builder early often underestimate how quickly Copilot credits are consumed when features like generative AI in Copilot Studio or AI Prompts in flows are enabled broadly. Start by enabling these features for a pilot group, measure consumption for 30 days, then extrapolate before rolling out widely.

Pay-as-you-Go: When It Makes Sense

Microsoft’s pay-as-you-go (PAYG) model charges based on actual usage via an Azure subscription. This is worth considering when:

You have unpredictable or seasonal usage patterns
You are piloting Power Platform and do not want annual commitments
You have a large user base but each user interacts infrequently
You want to charge back costs to business units via Azure cost management

Current PAYG rates (USD):

Power Apps: $10/active user/app/month
Power Automate: $0.60/standard flow run, $3.00/premium flow run (approximate — check current meter rates)
Dataverse: $48/GB database/month, $2.40/GB file/month

Warning: PAYG can become very expensive at scale. For a user who runs a premium flow 10 times per day, the monthly cost exceeds the flat-rate Premium licence within the first week. Always model both scenarios before committing.

Building a Licensing Strategy

Here is a practical framework for right-sizing your Power Platform licensing:

Step 1: Inventory

Use the Power Platform Admin Centre to identify:

All apps, flows, and copilots in production
Which connectors each uses (standard vs premium)
How many unique users interact with each
Current AI Builder/Copilot credit consumption

Step 2: Categorise Users

Group users into tiers:

Makers (build apps/flows): Almost always need Premium licences
Heavy users (use multiple apps/flows daily): Premium is cost-effective
Light users (use one app occasionally): PAYG or M365 seeded may suffice
External users: Power Pages or PAYG

Step 3: Model Costs

Use the Low-Code Kit Licensing Advisor tool to model different scenarios. Compare annual costs across:

All Premium per-user licences
Mixed Premium + PAYG
Current state vs proposed state

Step 4: Review Quarterly

Microsoft changes licensing terms regularly. Set a calendar reminder to review:

New licence announcements
Connector tier changes (connectors occasionally move between standard and premium)
Copilot credit consumption trends
Dataverse capacity usage

Looking Ahead

The trend is clear: Microsoft is consolidating towards per-user Premium plans and consumption-based Copilot credits. The Per App plan removal was the first step. Expect further simplification over the coming year, but also expect AI-powered features to consume an increasing share of your licensing budget.

The organisations that handle this well are the ones that treat licensing as a governance function, not a one-time procurement decision. Build it into your Centre of Excellence reviews, monitor it monthly, and adjust as your adoption grows.