Cluster II · Article xxviii of forty

Power Platform licensing.

Power Platform licensing spans Power Apps, Power Automate, Power Pages and Copilot Studio on per-user, per-app and per-flow models. The Admodum read on the SKUs, the connector classification, the AI Builder credit pool and the audit posture.

ClusterMicrosoft
Read12 minutes
AuthorMarcus T. Bennett
PublishedDecember 2024
UpdatedAugust 2025

Key takeaways

Section i

The four products.

The Power Platform spans four principal products. Power Apps is the low-code application platform: canvas apps (drag-and-drop UI; on the Dataverse and connector surface) and model-driven apps (data-driven UI; on Dataverse only). Power Automate is the workflow and RPA platform: cloud flows (event-triggered; multi-step orchestrations), desktop flows (RPA on the user-machine surface), and process advisor (process-mining).

Power Pages is the external-facing portal product (formerly Power Apps Portals), licensed on per-authenticated-user and per-anonymous-user surfaces. Copilot Studio (formerly Power Virtual Agents) is the AI agent and conversational-bot surface, licensed on a per-tenant capacity-purchase basis with overage. The wider Copilot Studio licensing spoke reads against the agent surface in detail.

Section ii

The per-user versus per-app.

Power Apps licensing carries two principal commercial surfaces. The per-user licence covers every user for unlimited Power Apps usage (canvas and model-driven, Premium connectors included). The per-app licence covers every user for up to a fixed number of distinct apps (the per-app pricing is per-user-per-app, with a multi-app discount on bundled per-app licences).

The break-even between per-user and per-app runs at the inflection where the per-user licence cost equals the cost of the per-app licences the user requires. A user who runs one app is best on a single per-app licence; a user who runs three apps approaches the per-user break-even depending on the per-app pricing surface in the geography; a user who runs five or more apps is generally best on the per-user licence. The wider per-user versus per-device spoke is the parallel principle on the suite surface.

Section iii

The connector classification.

The Power Platform connector library is the principal data-access surface. The connector classification is binary: Standard connectors and Premium connectors. Standard connectors include the Office 365 family (SharePoint, Outlook, OneDrive, Teams), the Dataverse for Teams surface and a wider set of free-tier connectors; they are included with the seeded Microsoft 365 Power Apps entitlement.

Premium connectors include the Dataverse full surface, SQL Server, Azure SQL Database, ServiceNow, Salesforce, SAP, and the wider third-party premium surface; they require a Power Apps Premium (per-user) licence, a Power Apps Per-App licence, or the corresponding Power Automate Premium entitlement. The Admodum read on the connector-classification audit is the connector-traffic inspection: a connector-traffic record against a Premium connector on a non-Premium-licensed user is a licence-non-compliance finding. The wider SAM audit anatomy framework reads the connector inspection.

Section iv

The Power Automate model.

Power Automate licensing runs on three principal surfaces. The seeded entitlement (with Microsoft 365 and per-user Power Apps) covers cloud flows that use Standard connectors and the seeded entitlement; the Power Automate Premium per-user licence covers Premium connectors and the wider attended and unattended RPA surface; the Per-Flow licence is the surface for shared flows (the flow is licensed, the users are shared on the flow).

The RPA (desktop-flow) entitlement carries the attended-versus-unattended axis. Attended RPA runs on the user's machine, under the user's authentication, and sits inside Power Automate Premium per-user. Unattended RPA runs on a server, under a service-account authentication; an unattended-add-on licence (per bot, per month) is required for each parallel unattended bot. The wider Copilot pilot methodology spoke is the adjacent surface where Power Automate flows often connect to Copilot scenarios.

Section v

The AI Builder credit pool.

AI Builder is the AI-feature surface inside the Power Platform: forms processing, document understanding, prediction (binary and multiclass classification on tabular data), text classification, GPT-capability invocation. AI Builder consumption is metered in AI Builder credits; each AI operation consumes a measured credit count.

The credit pool attaches to the licence tier (every Power Apps Premium licence carries a credit allocation; Power Automate Premium carries a separate allocation; Copilot Studio carries a separate allocation). Overage above the credit pool requires a separate AI Builder per-month credit-pack purchase; the per-month credit pack is the bridge to the Azure OpenAI per-token rate on the inference surface. The wider Azure OpenAI economics framework is the inference-cost surface against which AI Builder credit cost is read.

Section vi

The buyer artefacts.

The buyer-side artefacts to hold against the Power Platform estate are: the app inventory (every canvas and model-driven app, every author, every user, every connector used), the connector-traffic record (every connector, every call, every user, every classification), the licence-assignment register (every per-user, per-app, per-flow licence, every user, every app), the AI Builder credit position (every credit pool, every consumption, every overage), the unattended-bot register (every bot, every machine, every parallel session).

Power Platform licensing posture is app inventory, connector traffic, licence assignment and AI credit pool. The buyer-side artefacts close all four; the audit catches only the unattested.

The wider engagement sits in the Microsoft practice; the aggregated reading list sits in the Microsoft knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.

More from the Microsoft cluster

Continue the reading.

Article xxvii

Power BI Pro and Premium

The analytics-tier reading against the Power Platform breadth.

Article xxix

Copilot Studio licensing

The agent surface in the Power Platform stack.

Article iv

Copilot seat economics

The Microsoft 365 Copilot adjacency on the seat-economics surface.

Engage

Read your Power Platform position with a senior advisor.

A senior Admodum Microsoft advisor will read your app inventory, your connector-traffic record and your licence-assignment register against your renewal and audit posture on a private call. Active audit moments route to Audit Defence.

Independence
Admodum is not a partner, reseller, or affiliate of Microsoft, or of any other software vendor. No reseller margin, no referral commission, no audit-subcontract relationship.