Power Platform Licensing Strategy: Managed Environments, Copilots, and End-User Access

Question

1. In a Power Platform Managed Environment, do end-users who only interact with deployed apps or flows require a standalone Power Apps/Power Automate premium license, even if the app would not normally require one (e.g., it uses only standard connectors)?
2. Specifically for Microsoft Copilot Studio, when a copilot is deployed in a Managed Environment, do end-users need a personal license to interact with it, or does the tenant's messaging capacity pack cover their usage?
3. What is the fundamental licensing requirement for enabling and using Managed Environments? Does this apply only to makers and admins, or to every user active in that environment?
4. What are the recommended strategies for structuring Power Platform environments and licensing to optimize for cost, governance, and user experience, especially when mixing standard apps, premium apps, and copilots?

Answer 1

Hello Tadas Vaidotas, here are the responses to your specific questions.

1. Yes. When an environment is toggled to “Managed,” all apps and flows in that environment are treated as premium assets, regardless of the connectors they use. End users must have a paid Power Platform premium license to run any app/flow in a Managed Environment, even if those apps would ordinarily be covered by Office 365 licensing in an unmanaged environment.
2. End-users do not necessarily need individual Copilot licenses if your organization has purchased Copilot Studio message capacity (in the form of message packs or pay-as-you-go). Their interactions can be covered by the tenant’s capacity. However, if you have not provisioned any shared capacity, then each user would indeed need a Copilot license (such as a Microsoft 365 Copilot license) to use the Copilot agent.
3. To use Managed Environments, all active users (makers and consumers) in those environments must be covered by a Power Platform premium license (or eligible trial) – not just the admins. In other words, Managed Environments is unlocked by any standalone Power Apps, Power Automate, Power Pages, Microsoft Copilot, or Dynamics 365 license assigned to a user, and each user who builds or runs apps in a managed environment needs at least one such license. It is not a feature that only the admin needs to have.
4. I would generally say that this should start with aligning your environment strategy with the licensing boundaries. In practice, you should segregate apps by their licensing needs and criticality, and leverage different license models (per-user, per-app, capacity-based) to minimize cost. At the same time, use Managed Environments selectively for governance where it adds value, and maintain a good user experience by not over-restricting truly low-cost apps. Don't mix heavily Standard-only apps with Premium apps in the same managed environment. Also, you can look at per-app plans if you have the majority covered by existing user licenses but want to cover for some occasional users. Finally, segregate your dev, test and prod environments with appropriate plans. Look at where you can use the message-packs vs PAYG instead of full licensing.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Answer 2

Dear Tadas Vaidotas,

Thank you for your comprehensive inquiry regarding Power Platform licensing strategy. Please find detailed responses to your specific questions below.

1. End-User Licensing Requirements in Managed Environments: When an environment is designated as "Managed," all applications and flows within that environment are classified as premium assets, irrespective of the connectors utilized. Consequently, end-users must possess a valid Power Platform premium license to access any application or flow within a Managed Environment, even if such applications would typically be covered under Office 365 licensing in standard environments.

2. Microsoft Copilot Studio Licensing Model: End-users are not required to maintain individual Copilot licenses provided your organization has procured Copilot Studio message capacity through message packs or pay-as-you-go arrangements. User interactions are accommodated within the tenant's allocated capacity. However, in the absence of provisioned shared capacity, each user must possess an appropriate Copilot license (such as Microsoft 365 Copilot) to interact with deployed Copilot agents.

3. Managed Environment Licensing Prerequisites: Utilization of Managed Environments necessitates that all active users—including both makers and consumers—maintain coverage under a Power Platform premium license or eligible trial period. This requirement extends beyond administrative personnel. Managed Environments functionality is enabled through standalone Power Apps, Power Automate, Power Pages, Microsoft Copilot, or Dynamics 365 licenses, with each user requiring at least one qualifying license for environment participation.

4. Strategic Implementation Recommendations: We recommend establishing an environment strategy that aligns with licensing parameters and organizational requirements. Best practices include:

• Segregating applications based on licensing requirements and business criticality
• Implementing diverse licensing models (per-user, per-app, capacity-based) to optimize cost efficiency
• Deploying Managed Environments selectively where enhanced governance provides measurable value
• Avoiding the co-location of standard-only applications with premium applications within managed environments
• Considering per-app licensing plans for organizations with comprehensive existing user licenses requiring coverage for occasional users
• Maintaining appropriate environment segregation across development, testing, and production phases
• Evaluating message pack versus pay-as-you-go options as alternatives to comprehensive licensing

Thanks,  

Karan Shewale. 

*************************************************************************  

If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.

Answer 3

Would be nice if MSFT clarified the licensing requirement to cover Copilot premium licensing options as well. The grey area in the current DOC [link below] only covers Flows running in the context of Copilot Studio but does not cover Copilot Studio agents that DO NOT call flows, so not I'm not clear on how that behaves.

https://learn.microsoft.com/en-us/power-platform/admin/managed-environment-licensing

Answer 4

Hello Tadas Vaidotas, here are the responses to your specific questions.

1. Yes. When an environment is toggled to “Managed,” all apps and flows in that environment are treated as premium assets, regardless of the connectors they use. End users must have a paid Power Platform premium license to run any app/flow in a Managed Environment, even if those apps would ordinarily be covered by Office 365 licensing in an unmanaged environment.
2. End-users do not necessarily need individual Copilot licenses if your organization has purchased Copilot Studio message capacity (in the form of message packs or pay-as-you-go). Their interactions can be covered by the tenant’s capacity. However, if you have not provisioned any shared capacity, then each user would indeed need a Copilot license (such as a Microsoft 365 Copilot license) to use the Copilot agent.
3. To use Managed Environments, all active users (makers and consumers) in those environments must be covered by a Power Platform premium license (or eligible trial) – not just the admins. In other words, Managed Environments is unlocked by any standalone Power Apps, Power Automate, Power Pages, Microsoft Copilot, or Dynamics 365 license assigned to a user, and each user who builds or runs apps in a managed environment needs at least one such license. It is not a feature that only the admin needs to have.
4. I would generally say that this should start with aligning your environment strategy with the licensing boundaries. In practice, you should segregate apps by their licensing needs and criticality, and leverage different license models (per-user, per-app, capacity-based) to minimize cost. At the same time, use Managed Environments selectively for governance where it adds value, and maintain a good user experience by not over-restricting truly low-cost apps. Don't mix heavily Standard-only apps with Premium apps in the same managed environment. Also, you can look at per-app plans if you have the majority covered by existing user licenses but want to cover for some occasional users. Finally, segregate your dev, test and prod environments with appropriate plans. Look at where you can use the message-packs vs PAYG instead of full licensing.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.