About Power Apps per app plans
Power Apps per app plan allows individual users to run two applications and one portal for a specific business scenario in a specific environment based on the full capabilities of Power Apps. This plan provides an easy way for users to get started with Power Apps before broader scale adoption. These are available to purchase from the Office admin center and you can allocate add-ons in the Capacity area in the Microsoft Power Platform admin center.More information: Capacity add-ons.
The following release plan topic announces the availability of this feature: New licensing options for Power Automate standalone paid plans.
- Although, Power Apps per app plans appear in the Microsoft 365 admin center, you shouldn't attempt to assign them to users there. Power Apps per app plans must be allocated to an environment (and not to users) by an admin in the Power Platform admin center. After per app plans are allocated to an environment, they are assigned when apps are shared with users in the environment.
- Power Apps for Windows isn't supported if you have the Power Apps per app plan.
Steps for using per app plans
There are three steps to follow to use a per app plan:
- Purchase Power Apps per app plans
- Allocate per app plans to environments
- Set up apps to use per app plans
- Share the app
Step one: Purchase per app plans
You can purchase per app plans from your sales channel or in the Microsoft 365 admin center.
You can see your purchased plan in the Microsoft 365 admin center (Billing > Your products).
Once you've made your purchase, there are no further actions needed in the Microsoft 365 admin center such as license assignment since this license is not assigned to users but rather to environments.
Step two: Allocate per app plans
After purchase, you allocate per app plans to environments. If you have multiple environments like test and production, you need to allocate per app plans capacity to all these environments appropriately.
In the Power Platform admin center, select Resources > Capacity in the left-side navigation pane. If your organization has purchased add-ons that includes per app plans, an Add-ons tile appears on the Capacity screen displaying summary information about the capacity add-ons that your organization has.
To allocate add-ons, select Manage. For detailed information, see Allocate or change capacity in an environment.
As an admin, you can restrict who can allocate add-on capacity to environments. More information: Control who can allocate add-on capacity
If there are users who want to transition to per app, follow the two steps below in order:
- Allocate capacity of the per app licenses to the required environment.
- Remove any user license from the user.
Step three: Set up apps to use per app plans
After an admin allocates Power Apps per app plan to an environment, they're assigned to unlicensed users when an app in that environment is shared with them.
Follow these steps to turn off assigning per app plans for users when an app is shared with them:
Choose the app in Power Apps.
Select ... > Settings.
Under Pass assignment, change the Auto assign per app passes toggle to Yes. The Auto assign per app passes toggle appears in all app setting.
If per app plans are not allocated to the environment the app is installed in, the toggle is disabled.
Turning off the per app plan is currently available only for canvas apps. Model-driven apps and portals will have this ability in the future.
Check the App passes capacity for the environment with the app you're sharing. Make sure you have sufficient app passes assigned for the number of users using the app.
Go to Resources > Capacity > Add-ons tab.
Step four: Share the app
After completing the first three steps, you can now share apps.
Sharing model-driven apps
Share the model-driven app. See Share a model-driven app with Power Apps.
When the user launches the app, we create the user in the required Microsoft Dataverse environment. Users will not get added at the time of app sharing.
Sharing canvas apps
To share canvas apps, see Share a canvas app in Power Apps.
Consumption of per app licensing
The per app license gives a user access to two Power Apps and one portal for a single environment. See the table below for an example of the consumption of licenses by the number of applications and the environments used.
- Sharing an app with a user consumes the per app capacity.
- Each user is required to have a license.
- The consumption reporting for the per app license is a work in progress. Please check back for more details once the reporting is launched.
Reducing per app capacity to zero
If you allocate per app capacity to an environment and later reduce per app capacity to zero, users that were added to Dataverse while per app capacity was greater than zero will not get disabled in Dataverse. However, these users won’t be able to launch apps since there is no per app capacity allocated to the environment. Admins should remove the role of the user they do not intend to access the platform.
I assigned the baseline access license to my users as a workaround suggested earlier. Now that this workaround is not needed, what should I do to ensure my users are setup correctly?
As of October, 2020, the baseline access license is no longer required. Ensure that the per app capacity is allocated to the environment. After this step, you can remove the baseline access license from the user using these instructions.
What happens if I assign a user the Power Apps per user license when earlier they were using apps with the per app license?
Once the user is allocated a Power Apps per user license, per app license consumption reports will show per app licenses aren’t being consumed.
When will I be able to see the list of users who are using the Power Apps per app license?
We are currently working on this report. Please check back again for more details. This report will be available in the Power Platform admin center.
What are the differences in the admin experience between the Power App per app and the Power App per user license?
Power Apps per user plan is a user license assigned by admins from https://admin.microsoft.com. Once the user has this license they can access any number of Power Apps apps. However, the Power Apps per app plan provides a capacity to run apps and the management experience for this license is in the Power Platform admin center. The license is assigned to users when apps in the environment are shared with them. Admins allocate the capacity of per app to an environment and the makers share the app with users. This sharing consumes the per app capacity. Once the reporting is available, admins can see the users who are consuming capacity in the Power Platform admin center and not in the Microsoft 365 admin center.
Can I assign Power Apps per app plans in the Microsoft 365 admin center (admin.microsoft.com)?
No. Although after purchasing Power Apps per app plans they appear in https://admin.microsoft.com, they shouldn't be assigned to users in this website. Power Apps per app plans are to be allocated to an environment by an admin in https://admin.powerplatform.microsoft.com. After per app plans are allocated to an environment, the plans are assigned to users when apps are shared with users in the environment.
For users expected to use a Power Apps per app plan, why are users that use an app shared with them prompted to start a Power Apps trial?
For users to run Power Apps apps they must have a license, this includes being assigned a trial, per user plan or be accessing an app in an environment with Power Apps per app plan allocation.
Why are makers prompted to start a trial when creating a premium connection using gateways?
This is an artifact of previous, but no longer required, licenses being assigned to Power Apps makers. This license check and prompt to start a trial will eventually be removed.
Mitigation steps: The maker should sign up for the trial to proceed with creating the connection that uses a gateway.
Are users with a disabled account in an environment able to use per app plan?
Yes. If a user account is disabled in an environment, adding per app capacity, sharing the app with the user, and the user launching the app will enable the user.