Power Platform licensing 2026: Power Apps and Power Automate
Asking whether the company has Microsoft 365 is not enough. Licensing depends on the actual app or flow, connectors, data source, runtime model and users.
1. Describe the use case first
A personal productivity flow and a business-critical app used by hundreds of people have very different licensing implications.
- who uses it
- what triggers it
- which data sources it touches
- where it runs
2. Standard or premium capability?
Connectors and data sources can determine whether Microsoft 365 rights are enough or a separate Power Platform licence is needed.
- standard connectors
- premium connectors
- Dataverse
- custom connectors and APIs
3. User, process or capacity model?
Microsoft offers several licensing models. The right one depends on how the solution is used, not just what it is built with.
- user licensing
- process / bot licensing
- capacity
- consumption options
4. Verify current terms
Licensing changes. Final architecture and commercial estimates should always be checked against current Microsoft pricing and your organisation's agreement.
- current Microsoft pricing
- licensing guide
- existing tenant licences
- CSP / enterprise agreement
5. 2026 purchasing assumptions need a fresh check
Microsoft documents that the Power Apps per app SKU is no longer available to new customers through some purchasing channels from 2 January 2026, while availability differs for existing customers and CSP channels. Do not carry an old per-app assumption into a new architecture or estimate without checking the current purchasing route.
- per-app SKU availability
- purchasing channel
- existing entitlements
- re-check before procurement