Executive Summary
Who This Is For
Use this if you are planning, prototyping, or fixing a Power Apps canvas app and the licensing question has suddenly appeared:
- "Can we use the Microsoft 365 licenses we already have?"
- "Does SQL, Dataverse, a gateway, a custom connector, or this flow mean everyone needs Premium?"
- "Can we use per-app licensing instead?"
- "What can we build if Premium is not approved?"
You do not need to become a licensing specialist. You do need a written risk note before the app design, demo promise, or rollout plan hardens around a guess.
The Short Answer
A working app is not the same thing as a rollout-ready app.
Premium risk usually comes from the data source, connector, gateway, flow, environment, user count, and purchase channel. The app's license designation is a useful clue, but it is not the whole check.
Use one of three labels for the app idea:
| Label | Use when | Next move |
|---|---|---|
low risk | Standard connectors only, no visible Dataverse/gateway/custom connector/premium flow, no Managed Environment issue, and the intended users and access are known. | Build a small pilot and keep the risk note with the app. |
review needed | User count, entitlement, per-app availability, environment, guest access, flow context, data sensitivity, or connector status is unknown. | Ask IT or procurement before the architecture hardens. |
likely premium | Dataverse, SQL, a premium connector, custom connector, on-premises gateway, premium flow, or Managed Environment licensing issue is present. | Confirm the license path or design a fallback before making demo or rollout commitments. |
The useful meeting line is:
We are not asking for a licensing ruling yet. We are asking whether this app idea has low risk, needs review, or is likely Premium before we build around the wrong assumption.
The Premium Risk Decision Table
| Item to check | Lower-risk pattern | Review or likely Premium trigger |
|---|---|---|
| Users | Known internal users with existing access to the data source. | Unknown user count, guests, contractors, external users, or broad department rollout. |
| SharePoint or Microsoft Lists | Standard connector, users already have appropriate access, and the list design genuinely fits the process. | SharePoint is being used only to avoid a needed data, security, or lifecycle review. |
| Dataverse | Dataverse for Teams inside Teams within its documented boundary, or admin-confirmed Premium rights. | Standalone Dataverse tables, model-driven app needs, cross-environment lifecycle, richer security, or admin-unknown Dataverse use. |
| SQL or Azure SQL | Do not assume low risk by default. | SQL Server, Azure SQL, or on-premises database appears in the app, flow, or fallback design. |
| Custom connector or custom API | Do not assume low risk by default. | Any custom connector, custom API, or API-backed connector dependency. |
| Premium connector | Do not assume low risk by default. | Any connector that appears on Microsoft's current Premium connector list. |
| On-premises gateway | Do not assume low risk by default. | Any gateway dependency in the app, data source, or connected flow. |
| Power Automate flows | Standard-only flow with admin-confirmed context. | Premium connector, instant/app-triggered flow, automated/scheduled premium flow, run-only user question, Process license question, service account, or service principal pattern. |
| App license designation | The designation has been checked and flows have also been reviewed. | A Standard designation is being treated as proof while connected flows are ignored. |
| Per-app option | Admin confirms capacity, environment allocation, and purchase-channel fit. | Maker assumes per-app is available without tenant, environment, or channel confirmation. |
| Managed Environment | Admin confirms the environment and entitlement position. | Target environment is Managed Environment and entitlement has not been reviewed. |
Build The Risk Note
Copy this into the app ticket, review note, owner email, or decision record before you build too far.
Power Apps Premium Risk Note App idea: Owner: Date: Target environment:
What To Check First
Start with the app users. A prototype for five internal users is a different question from a department rollout, guest-user process, or app that every frontline user is expected to run.
Then list every data source and connector. Do not stop at the screen. Check the app, connected flows, gateways, custom connectors, Dataverse tables, SQL dependencies, and any "temporary" data path that will quietly become the real design.
Check the app license designation in Power Apps, but treat it as a clue. Microsoft documents a known issue where a premium connector used inside a flow connected to an app may not be recognized by the app's license designation. A Standard designation does not, by itself, prove that the rollout is standard-license safe.
Check flows separately. Automated and scheduled flows, instant flows, Power Apps-triggered flows, owner context, invoking-user context, Process licensing, run-only users, service accounts, and service principals can change the question. Do not tell the maker "the flow is covered" without admin confirmation.
Check per-app only as a question unless the tenant owner confirms it. As of January 2026, the Power Apps per-app SKU is no longer available for new EA or MPSA customers to purchase, though existing EA customers can continue to renew and CSP customers are unaffected. Per-app availability, purchase channel, capacity, app pass allocation, target environment, and channel-specific status are not maker-side guesses.
Check Managed Environment status. If the app will run in a Managed Environment, mark the note review needed until an admin confirms the entitlement position.
Fallback Options If Premium Is Not Approved
Use fallback options carefully. The goal is not to dodge licensing by building a weaker app.
| Premium trigger | Possible fallback | Caveat |
|---|---|---|
| Dataverse chosen for an early prototype | SharePoint or Microsoft Lists MVP | Only if permissions, relationships, delegation, lifecycle, and data sensitivity still fit. |
| SQL connector appears | SharePoint/List design or admin-owned data path | Do not use a poor data design just to avoid Premium. |
| Premium flow behind the app | Standard-connector flow, manual step, or Process review | Flow context and owner/run licensing still need admin confirmation. |
| Custom connector or API | Built-in Microsoft connector or approved manual handoff | May reduce capability or create extra operational work. |
| Managed Environment issue | Ask whether the environment policy and entitlement path are already covered | Environment policy may be non-negotiable. |
| Per-app uncertainty | Premium user plan review, pay-as-you-go review, or smaller pilot | Purchase channel, tenant setup, and environment allocation drive the real answer. Note that as of January 2026, per-app is no longer available to new EA/MPSA customers; existing EA customers can renew and CSP customers can still purchase. |
Questions For IT Or Procurement
Take these questions with the risk note.
- Which users will run this app, and do they already have Power Apps Premium or another qualifying entitlement?
- Does the app or any connected flow use Dataverse, SQL, a premium connector, a custom connector, an on-premises gateway, AI Builder, or another premium feature?
- Is the target environment a Managed Environment?
- If per-app licensing is being considered, is it available for our purchase channel and allocated to this environment?
- If a flow is app-triggered or manually triggered, who is considered the invoking user for license purposes?
- If a Process license or pay-as-you-go meter is proposed, who owns that decision and budget?
- Does the app involve guest users, external users, regulated data, HR, finance, legal, customer-confidential data, service accounts, or service principals?
- What fallback should we use if Premium is not approved before the pilot?
Evidence Notes
Use Microsoft documentation to trust the mechanics: app license designation, premium connector categories, Dataverse and gateway warning signs, flow run context, per-app allocation, Managed Environment licensing prompts, pricing-page caveats, and the current Premium connector list.
Do not use those sources as proof that your tenant is licensed correctly, that a specific user group is covered, that procurement will approve a plan, or that a quoted price applies to your agreement.
- The Power Apps licensing FAQ supports the main Premium trigger categories and the need for entitlement review. It does not decide the right license path for your tenant.
- The app license designation documentation supports checking Standard, Extended, or Premium designation. It also warns that connected-flow premium connectors may not appear in that designation, so use it as a clue rather than a final answer.
- The Power Automate licensing FAQ supports the separate flow check. It shows why trigger type, owner context, invoking user, Process licensing, service principals, and premium connectors must be reviewed rather than summarized as "owner pays" or "everyone pays."
- The per-app and pricing sources support asking current commercial questions. The Microsoft per-app end-of-sale page confirms the January 2026 status: no new EA/MPSA purchases, existing EA can renew, CSP is unaffected. Those sources do not create a price guarantee or prove that a channel, agreement, or environment can use a specific option.
- The Managed Environment source supports marking a Managed Environment as a review trigger. It does not prove whether your tenant already has the right qualifying licenses, capacity, or meter arrangement.
- The June 2026 Power Platform Licensing Guide PDF was resolved and downloaded as a formal Microsoft reference, but local text extraction was unavailable in this worker. Treat it as a document for human/admin verification before publication-level licensing claims, not as support for any guide-specific statement in this Briefing.
Proof Boundary
This Briefing can help you decide whether one app idea is low risk, review needed, or likely premium before the build hardens. It gives you a risk note, fallback options, and questions to take to IT or procurement.
It does not prove exact customer price, license compliance, legal entitlement, procurement approval, tenant-specific coverage, whether every user needs a SKU, whether a fallback design is architecturally correct, or whether Premium is worth the business value.
If leadership asks "can we build this?", answer with the decision label and the open questions. Do not answer with a licensing guarantee.
Briefing published by Collab365 Spaces, reviewed by Mark Jones on . Cite as "Check Power Apps Premium Risk Before You Build", Collab365 Spaces. 12 sources referenced.