Merge pull request #2327 from likiemel/main

Updating Content For Per App Licensing

power-platform/admin/about-powerapps-perapp.md

@@ -67,16 +67,17 @@ Follow these steps to turn on assigning per app plans for users when an app is s
 
    ![App settings.](media/app-settings2.png "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.
+3. Under **Per-app licensing**, change the toggle to **On**. The toggle appears in all app setting.
+   > [!NOTE]
+   > In the default environment, go to app settings > **Pass Assignment** and set the **Auto assign per app passes​** toggle to **Yes**.
 
-   ![Pass assignment.](media/pass-assignment2.png "Pass assignment")
+   ![Per app licensing.](media/per-app-licensing.png "Per app licensing")
 
 > [!IMPORTANT]
 > If per app plans are not allocated to the environment the app is installed in, the toggle is disabled. 
 > 
 > If per app plans are allocated to the environment, the toggle is enabled and defaults to on for apps created after October 1, 2020. 
 
-
 ### 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.
 
@@ -196,4 +197,4 @@ Yes. If a user account is disabled in an environment, there are three different
 ### Power Automate capabilities included with Per App plans
 A Power Apps Per App plan assignment doesn't give user the ability to create or own Power Automate flows that user Premium features. Creating and owning flows using Premium features requires assignment of a Power Apps Per User or Power Automate Per User license.  This doesn't apply for flows [associated to an app](/power-platform/admin/powerapps-powershell#associate-in-context-flows-to-an-app).
 
-[!INCLUDE[footer-include](../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../includes/footer-banner.md)]