Microsoft Power Platform licensing. The 2026 deep dive.

Power Platform combines Power Apps, Power Automate, Power BI, and Power Pages under one brand. Each component carries its own licensing model, and the cumulative cost at scale is the principal source of Microsoft commercial surprise.

Power Platform is Microsoft's low code, automation, business intelligence, and external portal stack. The four components sit under one brand and one administrative model, and the licensing model is one of the most operationally complex parts of the broader Microsoft estate.

The complexity is the source of the cost surprise. Power Apps, Power Automate, Power BI, and Power Pages each carry their own per user and per app pricing structures, and the Copilot Studio and AI Builder additions sit on top of the base licence.

Read the related Microsoft advisory practice, the Microsoft Power Platform sprawl guide, the CIO playbook for Power Platform licensing strategy, and the Microsoft knowledge hub.

The four Power Platform components

Power Apps

Low code application platform for building custom apps against Dataverse, SharePoint, and other data sources. Licensed Per User or Per App, with premium connector entitlements differentiating the two.

Power Automate

Workflow automation platform for both desktop (RPA) and cloud flows. Licensed Per User, Per User with Attended RPA, and Per Flow, with separate plans for hosted RPA.

Power BI

Business intelligence platform with Free, Pro, Premium Per User (PPU), and Premium capacity SKUs. Pro is bundled in M365 E5; standalone in lower SKUs.

Power Pages

External facing portal platform for partner, customer, and citizen scenarios. Licensed Per Authenticated User or Per Anonymous User.

Licensing models compared

Per user vs per app for Power Apps

The Power Apps licensing decision sits at the heart of most enterprise conversations. The per user plan covers unlimited apps for the licensed user; the per app plan covers two apps for a specific user against a per app fee.

Per User suits

• Heavy users. Users who consume many premium apps.
• Developer and citizen developer populations. Builders who run multiple internal apps.
• Predictable broad coverage. Customers who want a single licence model across the population.

Per App suits

• Light usage scenarios. Users who only need one or two specific premium apps.
• Targeted rollouts. Single business unit deployments with a known app set.
• Pilot or proof of concept phases. Lower entry cost before broader rollout.

The crossover point sits where the per user price equals the cost of two per app licences. Beyond two premium apps per user, per user is the cheaper option.

Premium connectors and the standard vs premium boundary

Power Platform connectors split into standard and premium. The standard set is included with the M365 base plans; the premium set requires a paid Power Apps or Power Automate plan.

The boundary is the source of most licensing surprise. Connectors that look intuitive to use, such as the Dataverse connector, SQL Server connector, custom connector, on premises data gateway connector, and many of the business application connectors, all sit on the premium side.

The practical effect is that workflows that look free under M365 can pull the user into a paid Power Apps or Power Automate licence the moment they touch a premium connector.

The four governance moves

1. Audit connector usage. Identify which workflows touch premium connectors.
2. Map users to licences. Confirm every user who consumes a premium connector holds a valid paid licence.
3. Set tenant policy. Use the Power Platform admin centre to restrict premium connector use to licensed populations.
4. Educate the builder community. Most premium connector exposure is accidental; awareness reduces it.

Copilot Studio and AI Builder

Copilot Studio is Microsoft's conversational AI design surface. AI Builder ships generative and predictive AI inside Power Apps and Power Automate. Both are licensed under metered consumption models rather than per user.

The licensing model uses credit packs at tenant level. Each Copilot Studio message, each AI Builder model invocation, and each generative AI prompt consumes a known credit allowance. The metered model can produce cost surprise at scale when usage is not actively managed.

Read the related Microsoft Copilot licensing guide 2026 for the broader Copilot framework across the Microsoft estate.

Power Platform sprawl

Sprawl is the dominant cost driver at upper enterprise scale. The platform makes app and flow creation easy, and the natural trajectory is uncontrolled growth in environments, apps, flows, and licence consumption.

The platform exposes the data, the admin centre exposes the controls, and the buyer side play is to instrument both before the cost line tells the story.

The five sprawl signals

• Environment count. Production, sandbox, developer, and trial environments multiply quickly without governance.
• Apps per environment. Apps that are built once and never retired accumulate.
• Premium connector usage. Workflows that drift into premium connectors trigger licence consumption.
• Flow count per user. Power Automate flows multiply with citizen developer adoption.
• Capacity consumption. Dataverse capacity, AI Builder credits, and Power BI Premium capacity scale with usage.

Read the deeper Power Platform sprawl guide for the full operational framework.

The buyer side framework

The full framework for Power Platform licensing has nine moves at every Microsoft renewal cycle.

1. Inventory every Power Platform deployment. Build a tenant level view of environments, apps, flows, capacities, and AI credits.
2. Classify users by component. Map every user to their actual Power Platform consumption.
3. Decide Per User vs Per App. Make the decision against the actual app consumption.
4. Audit premium connector usage. Identify accidental premium consumption.
5. Govern environment sprawl. Retire dormant environments, archive unused apps and flows.
6. Manage capacity consumption. Monitor Dataverse, AI Builder, and Power BI Premium capacity against the allocated entitlement.
7. Negotiate Copilot Studio against actual usage. Anchor the AI conversation in the customer's real consumption.
8. Build governance into the platform. Use the admin centre to enforce the policy.
9. Reframe the renewal annually. Treat Power Platform as a real commercial conversation each year.

Read the broader playbook in the Microsoft advisory practice, the Power Platform sprawl guide, the CIO playbook for Power Platform licensing strategy, the Microsoft Copilot licensing guide 2026, the EA 2026 guide, and the Microsoft knowledge hub.

What to do next

1. Pull the current Power Platform inventory at tenant level across environments, apps, flows, capacity, and AI credits.
2. Classify every user by actual Power Platform consumption.
3. Validate the Per User vs Per App decision against the live data.
4. Audit premium connector usage and reconcile against licensed populations.
5. Set up the environment governance model and retire dormant environments.
6. Establish capacity monitoring across Dataverse, AI Builder, and Power BI Premium.
7. Plan the Copilot Studio and AI Builder commercial conversation against actual usage.
8. Engage advisory support if the next Microsoft renewal is inside twelve months. Contact us.

Frequently asked questions

Is Power Apps free with Microsoft 365?

Limited. M365 includes seeded Power Apps rights against standard connectors only. Any workflow that touches a premium connector, Dataverse, or a custom connector requires a paid Power Apps or Power Automate licence.

What is the difference between Power Apps Per User and Per App?

Per User covers unlimited premium apps for the licensed user; Per App covers two specified apps per user against a per app fee. The crossover sits where per user equals two per app licences; above two premium apps per user, per user is cheaper.

How is Power Automate RPA licensed?

Per User with Attended RPA covers desktop automation alongside a single user; Per Flow with Unattended RPA covers automated processes running without a user. Both carry separate per user pricing above the base Per User plan.

What is the cost model for Copilot Studio?

Credit packs at tenant level. Each Copilot Studio message consumes a known credit allowance. Customers can buy additional credit packs or move to higher capacity tiers as usage grows.

How do I control Power Platform sprawl?

Through the Power Platform admin centre. Environment governance, connector policies, capacity monitoring, and app lifecycle management combine to control sprawl. Read the deeper sprawl guide for the full framework.