Power Platform: What It Is and Why Licensing Is Complex
Microsoft Power Platform is a suite of low-code development and automation tools. It sits at the intersection of Microsoft 365, Dynamics 365, and Azure, which creates a multi-dimensional licensing model. Users access Power Platform through a combination of seeded rights included in their M365/D365 licences, standalone per-user plans, and consumption-based credits. Understanding which bucket your organisation's usage falls into — and which it will fall into as adoption grows — is the key to cost control. This article is part of our Microsoft Enterprise Agreement Negotiation: Definitive Guide.
The core complexity: Microsoft Power Platform licensing changed significantly in 2023 with the introduction of the pay-per-app model being replaced by per-user plans and the introduction of Copilot Studio as a standalone product. The seeded rights included in M365 and D365 licences also changed. Many enterprises are running on licensing assumptions that no longer reflect current terms — and are either over-paying or at compliance risk.
Power Apps Licensing
Power Apps licensing operates on three models:
Free Guide
Microsoft EA Negotiation Tactics
How Fortune 500 buyers slash Microsoft EA costs — true-up traps, ELP rules, and renewal leverage.
Power Apps Premium (Per User)
Provides unlimited app usage across all Power Apps apps for the licensed user. Includes access to premium connectors (Salesforce, SAP, ServiceNow). Required for any user accessing apps that use premium connectors or Dataverse outside of Dynamics 365.
Power Apps Per App (Pay-Per-App)
Allows a specific user to run a single app. Cost-effective for limited use cases but expensive at scale — three apps per user exceeds the per-user plan cost. Typically used for departmental deployments of a single workflow app.
Seeded Rights (M365/D365 Included)
M365 licences include seeded Power Apps rights that allow users to create and run apps using standard connectors (SharePoint, Teams, Office 365 data). Standard connectors do not require a premium licence. The critical boundary: the moment an app accesses Dataverse, a premium connector, or an on-premises data gateway, a Power Apps Premium licence is required.
The Premium Connector Trap
The most common Power Apps over-spending scenario is the premium connector trigger. When a developer builds a Power App that connects to Salesforce, SAP, or a custom API connector, every user of that app requires a Power Apps Premium licence — even if they previously had full seeded rights. Organisations with active citizen developer programmes frequently discover this trigger after deployment, resulting in retrospective licence procurement at list price. Building a connector classification review into your app governance process prevents this.
Stay Ahead of Vendors
Get Negotiation Intel in Your Inbox
Monthly briefings on vendor pricing changes, audit trends, and contract tactics. Unsubscribe any time.
No spam. No vendor affiliations. Buyer-side only.
Power Automate Licensing
Power Automate has a similar seeded/premium structure:
Power Automate Premium
Provides access to premium connectors and attended robotic process automation (RPA) using Power Automate Desktop. Required for flows using premium connectors or attended automation runs.
Power Automate Process
For unattended RPA — automation runs that execute without a logged-in user. Priced per bot/process rather than per user. Critical distinction: attended RPA requires a Power Automate Premium per-user licence; unattended RPA requires Process licences.
Seeded Rights
M365 users can run Power Automate flows using standard connectors as part of their seeded rights. Same premium connector boundary as Power Apps applies.
Power BI Licensing
Power BI has one of Microsoft's cleaner licensing structures, though it still requires careful management at enterprise scale:
Power BI Free
Allows users to create reports and consume content published to their own workspace. Cannot share reports with other users without a Pro or Premium licence.
Power BI Pro
Required to share reports with other Pro users, or to publish to shared workspaces. If even one user in a group needs shared access to a report, all users in the group need Pro. M365 E5 includes Power BI Pro.
Power BI Premium Per Capacity (P SKUs)
Dedicated cloud capacity for large-scale deployments. Allows unlimited consumers (read-only) without per-user Pro licences. Cost-effective when consumer count exceeds ~500 users. Also enables paginated reports, larger dataset sizes, and AI features.
Power BI Premium Per User (PPU)
Provides Premium features on a per-user basis rather than capacity purchase. Better value for smaller Premium deployments (under ~250 users) than the P1 capacity SKU.
Copilot Studio Licensing
Copilot Studio (formerly Power Virtual Agents) is Microsoft's low-code conversational AI builder. With the Copilot wave, it has become central to many enterprise automation strategies — and its licensing is among the most opaque in the Power Platform suite.
Copilot Studio is licensed on a message pack basis: each interaction with a Copilot Studio bot consumes messages from a pre-purchased pool. The pricing model is:
- Message packs are purchased in blocks of 25,000 messages at approximately $200 per pack per month
- The Microsoft 365 Copilot licence ($30/user/month) does not include Copilot Studio consumption — it covers Microsoft's own Copilot features embedded in Office apps only
- Organisations building custom bots with Copilot Studio require separate message pack purchases, in addition to any M365 Copilot licences
- Azure OpenAI Service charges may apply for custom models used in Copilot Studio, adding a further variable cost layer
Negotiation opportunity: Power Platform licences — particularly Power Apps Premium, Power Automate Premium, and Copilot Studio message packs — are routinely included in EA negotiations at 20–35% below list price. Microsoft's account team has significant discounting authority for Power Platform when it is included as part of a larger EA renewal or expansion. Purchasing Power Platform standalone, outside an EA negotiation, consistently results in list-price or near-list procurement. For context on the EA negotiation framework, see our Microsoft EA Renewal: 15 Tactics That Work.
Negotiating Power Platform in Your EA
Power Platform has become a meaningful line item in most enterprise EA renewals. Key negotiation points include:
Bundle Power Platform with Your Core EA Renewal
Do not purchase Power Platform licences as a standalone transaction. Including Power Apps Premium, Power Automate Premium, and Power BI Pro/PPU in your core EA renewal gives Microsoft's account team clear commercial incentive to apply enterprise discounts. Standalone Power Platform purchases rarely receive more than 5–10% off list; EA-bundled purchases regularly achieve 20–30% discounts.
Negotiate Option Pricing for Future Expansion
If your Power Platform adoption is growing, negotiate pre-agreed option pricing in the EA for additional seats and message packs. This protects you against list-price exposure when your citizen developer programme scales beyond the initial committed base. Our Right-Size Your Microsoft Licence Estate guide covers how to model growth assumptions for EA negotiation.
Challenge the Premium Connector Assessment
Before accepting Microsoft's premium connector licence requirement, conduct an independent assessment of which apps genuinely require premium connectors versus which can be re-architected to use standard connectors or Microsoft Dataverse. The architectural choice between premium and standard connectors is a licensing decision as much as a technical one, and the right architecture can save significant licence cost.
Power BI Premium vs Pro: Model the Break-Even
For organisations with large Power BI consumer populations, the break-even between Pro per-user and Premium per-capacity licences is typically around 400–500 consumers. Above this threshold, Premium capacity becomes cost-effective. Model this break-even before your renewal and use it as a negotiating variable — Microsoft will often apply additional discounting on Premium capacity in competitive situations.
Further Reading
- Microsoft Enterprise Agreement Negotiation: Definitive Guide — the full EA commercial framework
- Microsoft EA Renewal: 15 Tactics That Work — EA renewal negotiation tactics
- Microsoft Copilot Licensing: Enterprise Guide — M365 Copilot and Copilot Studio licensing
- Right-Size Your Microsoft Licence Estate — seat optimisation before renewal
- Dynamics 365 Licensing Guide — Dynamics and Power Platform integration licensing
- Microsoft EA Negotiation Guide (Free PDF) — downloadable reference
- Microsoft Advisory Service — IT Negotiations' full EA engagement capability