A working guide for CIOs, procurement, and platform owners licensing Microsoft Power Platform at scale: Power Apps Per App against Per User, Power Automate cloud flows and RPA, Power Pages authenticated and anonymous users, and premium connector and Dataverse capacity. Most enterprises right size 20 to 40 percent of Power Platform spend once usage is mapped.
Executive Summary
Power Platform spend grows quietly. It starts with the seeded rights inside Microsoft 365, then expands into standalone Power Apps, Power Automate, and Power Pages licenses as real applications go live.
The cost drivers are the plan choice, the premium connector and Dataverse capacity, and the user counts on external facing Power Pages. Each is easy to over buy and hard to unwind later.
This guide walks the four licensing areas that decide the bill, the common traps, and the moves that right size them. Read the related Microsoft services practice, the Microsoft knowledge hub, the Microsoft EA renewal playbook, the Microsoft EA guide, and the multi vendor negotiation scorecard.
Background and Market Context
Power Platform covers Power Apps, Power Automate, Power Pages, and Copilot Studio, all built on the Dataverse data service and a library of connectors.
Microsoft 365 includes limited Power Platform rights, but those seeded rights only cover standard connectors and apps inside the Microsoft 365 context. The moment an app uses a premium connector, Dataverse, or custom logic, it needs a standalone Power Platform license.
That boundary between seeded and premium use is where most enterprises lose track of cost, because the upgrade is easy to trigger and easy to over provision.
The buyer side job is to map which apps and flows actually need premium licensing, then size the plans and capacity to that, not to a worst case. Read the related Microsoft EA guide.
Power Apps: Per App against Per User
Power Apps has two standalone plans, and choosing the wrong one is the most common source of overspend.
How the two plans work
- Per App. Licenses a user to run a defined set of applications. It suits people who use one or two specific apps.
- Per User. Licenses a user to run unlimited apps. It suits power users and developers who touch many apps.
- The break even. Per User only pays off above a certain number of apps per user, so most occasional users belong on Per App.
- Seeded rights. Check what Microsoft 365 already covers before buying either plan.
The buyer side move is to map each user to the apps they actually run, then put the majority on Per App and reserve Per User for genuine power users.
Power Automate: cloud flows and RPA
Power Automate licensing splits by what the automation does, and the desktop RPA piece is where costs jump.
The main licensing lines
- Per user cloud flows. For attended automation tied to a named user.
- Attended RPA. A user plus desktop flows running with a person present.
- Unattended RPA and hosted process. Bot style automation that runs without a user, licensed per process and often the largest line.
- Pay as you go. A metered option that can be cheaper for low volume automation.
The buyer side move is to count real running flows and processes, separate attended from unattended, and avoid licensing every user for RPA they never run.
Power Pages: authenticated and anonymous users
Power Pages builds external facing sites, and it is licensed by the people who visit them, which makes user counts the main risk.
How Power Pages is metered
- Authenticated users. Licensed in capacity packs per site, sized to the logged in users you expect.
- Anonymous users. Licensed separately in their own capacity packs for public visitors.
- Per site. Capacity is bought per site, so multiple sites multiply the cost.
- Bursting risk. Underestimating traffic can trigger overage, while overestimating wastes committed capacity.
The buyer side move is to forecast authenticated and anonymous traffic per site from real data and buy capacity in steps rather than committing to a peak up front.
Premium connectors and Dataverse capacity
Premium connectors and Dataverse capacity are the hidden cost layer underneath every Power Platform app.
What drives the cost
- Premium connectors. Any app or flow that uses one needs a premium standalone license, not seeded rights.
- Dataverse database capacity. Each premium license adds an entitlement; heavy data use can exceed it and trigger overage.
- File and log capacity. Metered separately from the database and easy to overlook.
- Overage rates. Buying additional capacity after the fact usually costs more than planning it in.
The buyer side move is to inventory which connectors your apps actually use and to monitor Dataverse capacity against entitlement before overage builds up.
Common Mistakes and Traps
The same avoidable mistakes recur in Power Platform licensing:
- Buying Per User when Per App fits. Most occasional users do not run enough apps to justify Per User.
- Ignoring seeded Microsoft 365 rights. Some scenarios are already covered.
- Licensing every user for RPA. Unattended processes, not users, are what need licensing.
- Undersizing Power Pages capacity. Anonymous traffic overage adds up fast.
- Missing Dataverse overage. Database, file, and log capacity all meter separately.
- Treating premium connectors as free. One premium connector upgrades the whole app.
Five Recommendations from Redress Compliance
- Map users to apps before choosing plans. Put occasional users on Per App and reserve Per User for genuine power users and makers.
- License automation by what runs, not who has it. Separate attended from unattended, and license unattended processes individually.
- Forecast Power Pages traffic per site. Size authenticated and anonymous capacity from real data and buy it in steps.
- Track Dataverse capacity against entitlement. Monitor database, file, and log use to avoid overage charges.
- Audit premium connector use. Confirm which apps truly need premium licensing and stop paying for it where seeded rights cover the need.
Frequently Asked Questions
What is the difference between Power Apps Per App and Per User?
Per App licenses a user for a defined set of applications, while Per User covers unlimited apps. Per User only pays off above a certain number of apps per user, so most occasional users belong on Per App.
Do you need a license if Power Platform is in Microsoft 365?
Microsoft 365 includes limited, seeded Power Platform rights. The moment an app or flow uses a premium connector, Dataverse, or custom logic, it needs a standalone Power Platform license.
How is Power Automate RPA licensed?
Attended automation is licensed per user, while unattended RPA and hosted process are licensed per process and run without a user. The unattended lines are usually the largest, so license them by what actually runs.
How is Power Pages licensed?
Power Pages is licensed by visitors, in capacity packs per site, split between authenticated and anonymous users. Forecast traffic per site from real data and buy capacity in steps to avoid overage.
What is Dataverse capacity and why does it matter?
Dataverse is the data service behind Power Platform, metered as database, file, and log capacity. Each premium license adds an entitlement, and heavy data use can exceed it and trigger overage charges.
How much can you save on Power Platform licensing?
Most enterprises right size 20 to 40 percent of Power Platform spend once usage is mapped. The saving comes from correct plan choice, right sized RPA and Power Pages capacity, and disciplined Dataverse and connector use.
How Redress Compliance Engages on Microsoft Power Platform
The practice runs four engagement models against Power Platform licensing.
- Vendor Shield always on advisory subscription. Covers Power Platform alongside the broader Microsoft estate continuously, not just at renewal. Read Vendor Shield.
- Renewal Program. A structured twelve month managed sequence around the Microsoft agreement. Read Renewal Program.
- Benchmark Program. Sizes your Power Platform commitment against documented engagements. Read Benchmark Program.
- Software spend assessment. Sizes Power Platform alongside the broader Microsoft, Oracle, and cloud footprint. Read software spend assessment.
Read the related Microsoft EA renewal playbook, the Microsoft EA guide, the Microsoft Azure ELA negotiation, the Microsoft Fabric pricing negotiation, the Microsoft audit defense, the Microsoft services practice, the Microsoft knowledge hub, the multi vendor negotiation scorecard, the software spend health check, and the complete white paper library.
