Skip to main content

Fixed: "A Power Apps Per User Plan, Power Apps Per App Plan or Power Apps Pay-as-You-Go Plan Will Be Required During Playback"

· 6 min read
Jagdish Kumawat
Founder @ Dewiride

Power Apps Studio attaches this note to an app's data sources: A Power Apps per user plan, Power Apps per app plan or Power Apps pay-as-you-go plan will be required during playback for apps with this connector. In the example, it was attached to SharePoint and Office 365 Users, which are standard connectors. The app's License designation said Standard, and a user with only a Microsoft 365 license ran it.

Where the Message Appears​

In the Career Development Plan app, the Data pane lists three data sources: Office365Users and two SharePoint lists. While building the app in Part 3, I found the message attached to each of them:

Message
A Power Apps per user plan, Power Apps per app plan or Power Apps pay-as-you-go plan will be required during playback for apps with this connector.

Looking closer, Studio doesn't show it on screen. The data sources have no icon next to them:

The Data pane listing Office365Users, CompetencyResponses and RoleCompetencies, each with its connection and a ... button, and no premium icon

The text is attached to each item as a description for screen readers, so a screen reader announces it with the data source's name. It's also in the page text that tools read.

What a Real Premium Connector Looks Like​

Compare it with a premium data source. In Add data, Dataverse tables have a diamond icon, and hovering it shows a Premium tooltip:

The Select a data source flyout with Dataverse tables Accounts, Activities and Contacts, each with a diamond icon, and a Premium tooltip reading A Power Apps Premium per user plan, Power Apps per app plan, or Power Apps pay-as-you-go plan will be required during playback for apps with this connector.

That tooltip names Power Apps Premium. The text on SharePoint and Office 365 Users doesn't, and they have no diamond.

How to Check What Your App Needs​

Don't go by the Data pane. Power Apps works out a License designation for every app from what it uses. Open Apps, select the app and choose Details. In the example, it said Standard, and its information icon explained what that means (How to Check a Canvas App's License Designation in Power Apps):

The License designation Standard on the app's Details page, with a tooltip reading An app that only uses standard connectors. An end user must have Power Apps included with Office 365 plan, Per App Plan, or a Per User Plan to access this app.

Microsoft's license designation article has the same table: a Standard app uses only standard connectors, and users can run it with a Power Apps for Office 365 plan, a per app plan or a per user plan. A Premium app uses at least one premium connector, a custom connector or an on-premises gateway, and needs a per app or per user plan.

The Proof: A User with Only Microsoft 365​

In Part 7, the app was shared with the demo team. Olivia Bennett has a single license, Microsoft 365 E5 Developer, which includes Power Apps for Office 365 (Plan 3) (How to See a User's Licenses and Apps in the Microsoft 365 Admin Center):

Olivia Bennett's Licenses and apps tab with one license checked, Microsoft 365 E5 Developer (without Windows and Audio Conferencing), and Microsoft Copilot Studio Viral Trial and Microsoft Power Automate Free unchecked

She opened the app, saw her plan and sent a response, with no license prompt:

The Career Development Plan app running for Olivia Bennett: Welcome, Olivia, Job title: Head of Sales, Manager: Admin User, and the My plan and My team buttons

When It Does Matter​

The designation changes if the app starts using a premium connector, a custom connector or an on-premises gateway. Microsoft lists one known gap: a flow that uses a premium connector doesn't change the app's designation, even though users then need premium rights. And in a managed environment, every user needs a qualifying license, whatever the app uses (Licensing for managed environments).

Common Mistakes​

MistakeWhat happensDo this instead
Buying Power Apps licenses because of the noteMoney spent on rights users already haveCheck the app's License designation
Trusting Standard while a flow uses a premium connectorUsers need premium rights anywayCheck the flows the app calls
Turning on Managed EnvironmentsEvery user needs a premium licenseLeave it off for Microsoft 365-only users

Troubleshooting​

SymptomLikely causeFix
The designation says PremiumThe app uses a premium or custom connectorFind it in the Data pane: it has a diamond
A user is asked for a licenseThe app is premium, or the environment is managedCheck the designation and the environment

FAQ​

Why does Studio attach the message to standard connectors?​

Microsoft doesn't explain it. The visible signs, the missing diamond and the Standard designation, both say the app doesn't need a Power Apps plan, and a Microsoft 365 user ran it.

Which Microsoft 365 licenses include Power Apps for Office 365?​

Many Microsoft 365 and Office 365 business and enterprise plans do. Check a user's Licenses and apps in the Microsoft 365 admin center for Power Apps for Office 365.

Conclusion​

The note A Power Apps per user plan … will be required during playback on SharePoint and Office 365 Users isn't the license requirement. The app's License designation is. In the example it was Standard, and a user with only Microsoft 365 ran the app.

Additional Resources​

Stay Updated

Subscribe to our newsletter for the latest tutorials, tech insights, and developer news.

By subscribing, you agree to our privacy policy. Unsubscribe at any time.