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 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.

Important

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.

You cannot assign Power Apps per app plan baseline access licenses to users in a trial environment.

Steps for using per app plans

There are three steps to follow to use a per app plan:

  1. Purchase Power Apps per app plans
  2. Allocate per app plans to environments
  3. Set up apps to use per app plans
  4. 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.

Power Apps per app plan

You can see your purchased plan in the Microsoft 365 admin center (Billing > Products & services).

Power Apps per app plan purchased

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.

Example of purchased capacity in the admin center

To allocate add-ons, select Manage. For detailed information, see Allocate or change capacity in an environment.

Note

As an admin, you can restrict who can allocate add-on capacity to environments. More information: Control who can allocate add-on capacity

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:

  1. Choose the app in Power Apps.

  2. Select ... > Settings.

    App settings

  3. 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.

    Pass assignment

Important

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.

For the time being, "Ad-hoc subscription" consent plans must be enabled for an organization's tenant. An ad-hoc subscription refers to trial licenses that can be assigned by admins to users via Azure Active Directory (Azure AD) or the Microsoft 365 admin portal, or that users can sign themselves up for via https://signup.microsoft.com. End users that receive a per app plan also receive an "ad-hoc" Power Apps baseline access plan. This plan ensures users can launch apps shared with them when they're expected to be entitled access via a per app plan. The requirement for ad-hoc subscription consent plans will be removed in the future. This documentation outlines how ad-hoc subscription consent plans are blocked and unblocked for an organization.

Check capacity

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.

Add-on capacity assignment

Step four: Share the app

After completing the first three steps, you can now share apps.

Sharing model-driven apps

  1. Get the Power Apps per app plan baseline access license here.

  2. Assign the Power Apps per app plan baseline access license to users. See the following topics for guidance:

  3. Share the model-driven app. See Share a model-driven app with Power Apps.

Sharing canvas apps

To share canvas apps, see Share a canvas app in Power Apps.

FAQ

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 they prompted to start a trial after signing in to https://make.powerapps.com?

https://make.powerapps.com is being updated to not require a license to begin making an app. Licenses are required for users to run apps.

For users expected to use a Power Apps per app plan, why are they prompted to start a trial when attempting to create a premium connection?

https://make.powerapps.com is being updated to not require a license to begin making an app. Licenses are required for users to run apps.

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?

Users are receiving trial prompts because Power Apps per app plan is currently dependent on a $0 ad-hoc subscription license being assigned to any user that will utilize a per app plan. The ad-hoc subscription license is called "Power Apps per app baseline access". When users access a canvas app for the first time, the platform attempts to auto-assign this to users so no action is required by a Power Platform service admin or an end user. The auto assignment fails when the AllowAdHocSubscription flag is set to false at the tenant level or Remove-AllowedConsentPlans -Types "Internal" has been executed for the tenant. When the Power Apps per app baseline access license isn't assigned to a user, the Power Apps client prompts the user to start a trial to get an entitlement.

Mitigation steps:

For customers that want to use a Power Apps per app plan and they have the AllowAdHocSubscriptions flag set to false, admins should do the following.

  1. Turn on, at least temporarily, ad-hoc subscriptions. Run the following PowerShell command:

    Set-MsolCompanySettings -AllowAdHocSubscriptions $true 
    

    Documentation for this PowerShell cmdlet

  2. Add to your tenant the required ad-hoc subscription to use a Power Apps per app plan by selecting the following link and completing the sign-up process: https://signup.microsoft.com/signup?sku=bf666882-9c9b-4b2e-aa2f-4789b0a52ba2.

  3. You are now able to assign the Power Apps per app baseline access license to all users expected to use a Power Apps per app plan. Assigning the baseline access plan can be done in https://portal.azure.com or https://admin.microsoft.com.

  4. You can assign the Power Apps per app baseline access individually to users or assign the license to a security group that contains all users that will receive a Power Apps per app plan.

  5. This step is optional, at this point the admin can turn off AllowAdHocSubscriptions for their tenant by using the following command:

    Set-MsolCompanySettings -AllowAdHocSubscriptions $false
    
  6. Execute the following command, if viral consent plans were previously removed: Add-AllowedConsentPlans -(Types @("Viral")

    Viral licenses can be assigned to a user either by an admin or by non-admins that assign these licenses to themselves. The ability for a non-admin to assign the license themselves is controlled by AllowAdHocSubscriptions.

    If AllowAdHocSubscriptions is off and viral consent plans are allowed, end-users can use viral licenses already assigned to them but won't be able to sign up for viral licenses on their own.

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.