Microsoft 365 E3 and E5: Where Power Platform Licensing Ends
Technical review: 26 October 2026. Product names, licensing references and procedures reflect this review; check the linked documentation for your release.
“Do we need E3 or E5 for Power Platform?” is too broad to produce a reliable licensing answer. Microsoft 365 subscriptions can include useful Power Apps and Power Automate rights, but those rights are not a universal entitlement to every connector, Dataverse workload or agent capability. Start with the scenario the user intends to run.
Build a small workload inventory
List the app or flow, who creates it, who runs it, the connectors involved and the destination environment. Include unattended automation, external users and any dependency on Dataverse or a Managed Environment. These details are more useful than choosing the highest enterprise suite and hoping it covers everything.
Distinguish authoring from consumption. A maker’s entitlement does not necessarily license every end user of a production application. Likewise, an application that happens to be launched from Teams is not automatically covered for every premium feature or use of full Dataverse.
Keep these entitlement boundaries visible
| Scenario | Licensing question to resolve |
|---|---|
| An app using Microsoft 365 data and standard connectors | Does the assigned subscription include the required seeded rights for this use? |
| An app or flow using premium/custom connectors | Which standalone, qualifying bundled or metered entitlement covers the scenario? |
| Full Dataverse in a business environment | What app/flow entitlement, capacity and access model apply? |
| A developer sandbox | Are the activities limited to eligible development/testing? |
| A published Copilot Studio agent | How are maker access and agent consumption funded? |
E5 is not a shortcut to every Power Platform premium capability. Dataverse for Teams and full Dataverse also have different contexts and limits. Use the current licensing guide for the particular workload instead of transferring an answer from an unrelated product.
Do not confuse licensing with authorization
Even a correctly licensed user can lack environment membership, app sharing or Dataverse table privileges. Conversely, a permission assignment can make a screen visible without proving that the production use is properly licensed. Capture those checks separately so that one is not used as evidence for the other.
The Dataverse access checklist covers the security side. For agents, Copilot Studio access and billing separates maker permission from metered consumption. Avoid mixing those questions into a single yes/no statement about an E3 or E5 license.
Write down the decision and its assumptions
Record the exact product/service plans, intended users, environment type and features that the decision depends on. Link the current official licensing material and note its review date. Do not hard-code a price into an operational runbook unless the commercial terms and region have actually been checked.
When an app gains a premium connector, moves into production or changes its audience, revisit the decision. A short approved matrix is easier to maintain than a claim that “everyone with Microsoft 365 is covered.” For procurement or contract interpretation, confirm the final entitlement with the organization’s licensing owner using the current product terms.
References
- Microsoft: Power Platform licensing FAQs
- Microsoft: Power Apps and Power Automate licensing guidance
- Microsoft: Dataverse for Teams overview