Editorial photograph of a Power Platform low code development review on a boardroom screen
Guide · Microsoft · Power Platform

Microsoft Power Platform. Licensing decoded.

Power Apps, Power Automate, Power Pages, and Copilot Studio carry their own seat plans, capacity meters, and AI credits. Read the buyer side framework, the per app math, and the levers that beat the default quote.

Read the Framework Microsoft Hub
22 to 38%Saving on the right Power mix
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

The Microsoft Power Platform sits at the center of every Microsoft 365 estate that uses low code. The four products are Power Apps, Power Automate, Power Pages, and Copilot Studio. Each carries seat plans, capacity meters, and AI credit pools. The buyer side framework reads all three together.

This guide is a buyer side reference. Pair it with the EA negotiation guide, the Dynamics 365 licensing guide, and the Copilot licensing piece for the wider Microsoft commercial picture.

Key Takeaways

What a CIO needs to know in 90 seconds

  • Power Platform is four products. Power Apps, Power Automate, Power Pages, and Copilot Studio each carry their own price.
  • Per app and Premium plans are the seat levers. Per app fits narrow use, Premium fits estate wide use.
  • Dataverse capacity is the second meter. Storage, database, and file capacity meters sit alongside the seats.
  • Power Automate has unattended bot SKUs. RPA capacity is metered separately from cloud flows.
  • Copilot Studio runs on a credit pool. Conversation credits meter AI use.
  • The 22 to 38 percent saving sits in the mix. Right sized seats, capped capacity, and bid based Premium step.
  • Microsoft includes some Power features in Microsoft 365 already. Read the line before paying twice.

Why this guide

The Power Platform estate is one of the hardest Microsoft lines to right size. Buyers carry shadow estates, mixed seat plans, and uncapped capacity meters. The renewal envelope routinely surprises the buyer side because nobody pulls the full inventory.

Three reasons the Power Platform conversation carries weight

  • Shadow estate. Citizen developers create Power Apps that nobody tracks.
  • Capacity overage. Dataverse storage meters tick up silently.
  • Premium plan creep. Per app users get upgraded to Premium when one app needs a Premium connector.

The four products

The Power Platform groups four products under one commercial umbrella. Each has its own purpose, its own user, and its own price.

Power Apps

The low code application platform. Canvas apps for custom UI, model driven apps over Dataverse, mobile apps for field operations. Sold per app or per user.

Power Automate

The workflow and RPA platform. Cloud flows for SaaS to SaaS automation, desktop flows for RPA against legacy interfaces, AI Builder for document and form processing. Sold per user or per flow.

Power Pages

External facing low code websites built on Dataverse. Customer portals, partner portals, citizen services. Sold per authenticated user, per anonymous visitor, or per page.

Copilot Studio

The conversational AI build tool, formerly Power Virtual Agents. Used to build Copilot extensions, chatbots, and agent style conversational interfaces. Sold on a conversation credit pool.

Pricing primitives

The Power Platform commercial framework runs on three meters. Seats, capacity, and credits. Read all three before quoting.

Three meters that shape the bill

MeterWhat it countsWhere it shows up
SeatsUser access to apps, flows, pagesPower Apps per user, Power Apps per app, Power Automate per user, Power Pages per user
CapacityDataverse storage, database, filesDataverse storage GB, database GB, file GB
CreditsAI Builder, Copilot Studio, RPA hosted botsAI credits, Copilot Studio messages, unattended bot capacity

What Microsoft 365 already includes

  • Power Apps for Microsoft 365. Limited Power Apps over Microsoft 365 data sources.
  • Power Automate for Microsoft 365. Limited cloud flows over Microsoft 365 connectors.
  • Power Apps for Teams. Power Apps inside Teams over the Dataverse for Teams environment.
  • Power Virtual Agents for Teams. Light conversational AI in Teams.

Read the included line before paying twice

Most Microsoft 365 estates already include limited Power Platform use. Estates that buy Premium per user without reading the included line pay for capabilities that Microsoft 365 already provides. The free baseline is real and meaningful for the citizen developer estate.

Per app vs Premium

The biggest seat decision sits between the per app plan and the Premium per user plan. Per app fits narrow use. Premium fits estate wide use. The break even sits around three to five Premium apps per user.

Per app versus Premium at a glance

ElementPer app planPremium plan
ScopeAccess to two named apps or one portalUnlimited apps and portals
Premium connectorsIncludedIncluded
DataverseIncluded capacity per licenseHigher included capacity per license
Use caseSingle workflow, single app usersCitizen developer fleet, estate wide use
Break even1 to 2 apps per user3 plus apps per user

A typical Power Apps mix for 15,000 users

  • 1,500 Premium users. Citizen developers, app makers, power users.
  • 4,000 per app users. Targeted users with one or two specific apps.
  • 9,500 free baseline users. Microsoft 365 included Power Apps and Power Automate.

Dataverse and capacity

Dataverse is the underlying database for the Power Platform. Capacity is metered in three units. Storage, database, and file. Capacity overage carries a per GB monthly cost that is easy to miss.

What is included with each seat

  • Premium per user. Base storage, database, and file allocation per license.
  • Per app per user. Lower allocation per license.
  • Microsoft 365 base. Limited Dataverse for Teams capacity per tenant.
  • Tenant pool. Total capacity pools across all eligible licenses.

Where capacity overage shows up

  1. Model driven apps over large datasets. Asset registers, customer records, contract repositories.
  2. Document libraries inside Power Apps. File capacity ticks up quickly.
  3. Power Automate run logs. Long retention drives database capacity.
  4. AI Builder document processing. Stored files and metadata in Dataverse.

Copilot Studio pricing

Copilot Studio sells on a conversation credit pool. The pool is sized to the tenant and replenished monthly. Higher tier capabilities consume more credits per conversation. Sized incorrectly the pool runs out mid month and the buyer faces an overage rate.

Three rules that shape the Copilot Studio bill

  • Conversation credit pool. Sized to the buyer at sign up.
  • AI capability tier. Generative answers consume more credits than rule based.
  • Per copilot scope. Multiple copilots share the same tenant pool.

Negotiation levers on the Power Platform

Power Platform contracts open seven buyer side levers. Three sit in the seat mix. Four sit in the capacity and credits.

Seat side levers

  • Per app right sizing. Move users from Premium to per app where the app count is one or two.
  • Free baseline first. Validate Microsoft 365 included Power Apps for new use cases.
  • Premium tier discount. Negotiate volume discounts on Premium seats above a defined threshold.

Capacity and credits levers

  1. Capacity pool buy ahead. Purchase capacity in larger blocks at a lower per GB rate.
  2. Overage rate cap. Cap the per GB overage rate for the contract term.
  3. AI credit pool sizing. Size the pool to the validated demand, not the peak.
  4. Annual escalator cap. Hold the annual uplift to a defined ceiling.

Clauses worth red lining

The Power Platform contract carries clauses worth reading carefully. Capacity overage, Premium step up, term, and connector liability.

Five clauses that matter most

  • Capacity overage rate. The per GB price for Dataverse overage.
  • Premium step up. The path from per app to Premium without a forced full estate uplift.
  • Term length and renewal. Multi year terms with annual true up windows.
  • Connector liability. Premium connectors carry usage and rate limits.
  • AI credit rollover. Monthly credits typically do not roll forward without negotiation.

The capacity overage line is the silent cost

Buyers see seats on the invoice every month. Capacity overage shows up quarterly or annually as a true up. The true up surprises the buyer because nobody reads the capacity meter monthly. Build the capacity overage cap into the contract and into the operating cadence.

What to do next

The eight step checklist below moves the Power Platform estate from the renewal envelope to a defensible seat and capacity mix.

  1. Pull the full Power inventory. Apps, flows, portals, and copilots by owner.
  2. Score the seat mix. Premium, per app, and free baseline users.
  3. Map the capacity meters. Storage, database, and file capacity utilization.
  4. Quote the right seat mix. Premium for power users, per app for targeted users.
  5. Quote the capacity pool. Block buy ahead at a lower per GB rate.
  6. Quote the AI credit pool. Sized to validated demand.
  7. Defend the residuals. Document the citizen developer governance.
  8. Lock the route 60 days out. Cap overage and escalators in writing.

Frequently asked questions

Do every Power Apps user need Premium?

No. Premium fits citizen developers and power users that build three or more apps. Per app fits users with a narrow workflow on one or two apps. Most Microsoft 365 users already have the free baseline Power Apps and Power Automate. Validate the free baseline before quoting paid seats.

How is Power Automate RPA priced?

Power Automate sells attended desktop flows through the per user RPA plan and unattended desktop flows through a separate unattended bot SKU. Unattended bots are priced per hosted bot per month. AI Builder credits sit alongside both for document and form processing. Buyers that scale RPA hit the unattended bot capacity meter first and the AI credit pool second.

Does Dataverse capacity reset every month?

No. Dataverse capacity is allocated to the tenant and consumed cumulatively. Storage, database, and file capacity meters reflect the total consumption against the total allocation. Capacity overage is billed monthly or as a true up at defined intervals. Buyers should monitor capacity utilization monthly to avoid surprise overage charges at the renewal anniversary.

Can Copilot Studio credits roll over?

By default, monthly Copilot Studio credits do not roll forward to the next month. Buyers that want roll over should negotiate the clause explicitly for the contract term. Credit consumption varies by AI tier and conversation length, so sizing the pool against the validated demand is the standard buyer side approach rather than assuming roll over coverage.

Can Power Apps replace a custom app build?

For many internal workflow use cases, yes. The Power Platform shines on form, workflow, and data driven apps over Microsoft 365 and third party SaaS sources. Custom code wins on heavy compute, complex UX, or scale to public users. Use Power Apps for the internal workflow estate, custom code for high complexity.

How does the Microsoft 365 included Power Platform compare to the standalone plans?

The Microsoft 365 included Power Apps and Power Automate cover Microsoft 365 connectors and Dataverse for Teams. Premium connectors, model driven apps, and standalone Dataverse require paid plans. The included baseline is real for citizen developers on Microsoft 365 data. Paid plans extend to third party SaaS and full Dataverse.

How Redress engages on the Power Platform

Redress runs the Power Platform review as a six week assessment. The work pulls the full Power inventory, scores the seat mix, maps the capacity meters, and quotes three routes side by side. The deliverable is a buyer side seat and capacity mix, the negotiation envelope, and the clause checklist.

Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.

Score your Power Platform estate against the buyer side benchmark in under five minutes.
Open the M365 License Optimizer →
White Paper · Microsoft

Download the Microsoft EA Renewal Playbook.

A buyer side framework for the Microsoft renewal cycle. Power Platform seat mix benchmarks, capacity meter sizing, Copilot Studio credit pool guidance, and the residual clause checklist used across enterprise software engagements.

Independent. Buyer side. Built for Microsoft customers running large Power Platform estates with citizen developers, RPA fleets, and Copilot Studio rollouts.

Microsoft EA Renewal Playbook

Open the white paper in your browser. Corporate email only.

Open the Paper →
22 to 38%
Saving on the right mix
3 to 5
Apps where Premium wins
60 to 75%
Free baseline coverage
500+
Enterprise clients
100%
Buyer side

We pulled the full Power inventory, moved 4,000 Premium seats to per app, capped the Dataverse overage at the contract rate, and sized the Copilot Studio credit pool against the validated demand. The combined route reduced the Power Platform line by 33 percent across the contract term.

Director of Enterprise Architecture
Global retail group
More Reading

More from this practice.

Microsoft Hub →
Microsoft EA Negotiation 2025
Microsoft · Guide
Microsoft EA Negotiation 2025
EA negotiation framework.
24 min read
Dynamics 365 Licensing Guide
Microsoft · Guide
Dynamics 365 Licensing Guide
The Dynamics 365 reference.
22 min read
Microsoft 365 Copilot Licensing
Microsoft · Article
Microsoft 365 Copilot Licensing
Copilot enterprise framing.
14 min read
Microsoft 365 E3 vs E5
Microsoft · Article
Microsoft 365 E3 vs E5
Base tier decision.
18 min read
Microsoft Vendor Management
Microsoft · Article
Microsoft Vendor Management
Toolkit for the renewal cycle.
16 min read
Editorial photograph of enterprise contract negotiation strategy

Your Power mix is your envelope.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

Microsoft licensing intelligence, monthly.

Power Platform seat movement, Dataverse capacity overage, Copilot Studio credit pools, RPA bot pricing, and the wider Microsoft commercial leverage signals across every renewal cycle.