Some Microsoft 365 licences include limited Power Apps and Power Automate rights. They let licensed users build and run apps that extend Microsoft 365 using standard connectors. They do not provide unrestricted access to premium connectors, custom connectors, an on-premises gateway or full Dataverse use.
That distinction matters because an app can start as a simple SharePoint form and become premium when one connection changes.
What the included rights are for
Microsoft describes the included capabilities as a way to extend and customise Microsoft 365. A common example is a canvas app using a SharePoint list, Microsoft Lists, OneDrive or another standard connector.
The exact entitlement depends on the user's assigned Microsoft 365 plan. Do not infer it from the fact that the Power Apps maker portal opens. Ask an administrator to check the user's licences and the app's licence designation.
Microsoft maintains a Power Platform licensing overview and a separate licensing FAQ. Both are more reliable than a price or plan table copied into an article because licensing changes.
What usually moves an app beyond Microsoft 365 rights
An app normally needs separate Power Apps licensing when it uses premium capabilities. Examples include:
- a premium connector;
- a custom connector;
- an on-premises data gateway;
- Dataverse capabilities beyond the limited Microsoft 365 entitlement;
- a code component that connects directly to an external service from the browser.
Microsoft's app licence designation guidance explains how standard, premium and other designations affect end users. The licence is not only a maker concern. Every person who runs the app needs the appropriate entitlement.
A practical check before you build
Write down the complete data path before choosing a licence:
- Which data sources will the app read and write?
- Which connectors will it use directly?
- Does a flow called by the app use premium connections?
- Will it use a gateway, custom connector or code component?
- Who must create, own, share and run it?
- Which environment will hold the app and its connections?
Then open the app in Power Apps and use Settings > General > License designation to inspect its current designation. Treat that as a current technical signal, not a permanent promise. Adding or reclassifying a connector can change the answer.
Sharing is separate from licensing
Publishing a canvas app makes the latest saved version available. It does not automatically give people access.
You must share the app and make sure each user can reach the underlying data. A user might be able to open an app but fail when it reads a SharePoint list, or have list access but lack the licence required for a premium connector.
Connection ownership also needs thought. Avoid leaving an operational app dependent on one employee's personal connection. Use an ownership and support model your administrators can maintain.
The honest answer
Power Apps can come with Microsoft 365, but only as a bounded set of capabilities attached to qualifying licences. For a SharePoint-based app using standard connectors, those rights may be enough. For Dataverse, custom APIs, gateways or premium connectors, assume nothing and verify the complete design against current Microsoft licensing guidance.
For practical help checking a proposed app before licensing surprises appear, join the Power Apps Builders Space.