What\u2019s Next?<\/strong> <\/h3>\n\n\n\nOur goal with this update is to make managed environment capabilities accessible to a broader range of customers. This licensing change is a direct response to customer feedback, and we\u2019ll continue to evaluate ways to improve managed environments and Power Platform governance in response to your evolving needs. <\/p>\n\n\n\n
Stay tuned for more details during Microsoft Ignite on November 19th and be sure to reach out to your Microsoft account representative if you have any questions on how this update can benefit your organization.<\/p>\n\n\n\n
FAQ<\/h4>\n\n\n\n
Q:<\/strong> How do the changes to the managed environment licensing model impact my existing Power Apps and Power Automate licenses? <\/p>\n\n\n\nA: <\/strong>These changes allow customers to assign their existing premium Licenses more easily and consume them fully, before they need to acquire more licenses. <\/p>\n\n\n\nQ:<\/strong> Do all users in a managed Environment need a premium license<\/strong> even if they are not directly interacting with flows or apps? <\/p>\n\n\n\nA: No,<\/strong> this doesn\u2019t change, only active users<\/strong> in managed environments that are generating activity by launching an app or running a flow are required to have a premium license assigned. <\/p>\n\n\n\nQ: <\/strong>What is the expected license behavior if a user is assigned a Power Apps Premium and Power Automate<\/strong> Premium <\/strong>while running basic on in-context Flows only? <\/p>\n\n\n\nA: <\/strong>If a user is assigned both a Power Apps Premium and Power Automate Premium<\/strong> but only running basic or in-context flows, the Power Apps premium covers this activity, the Power Automate premium provides additional flexibility for any premium flows. <\/p>\n\n\n\nQ:<\/strong> What types of activities are considered basic flows<\/strong> in managed environments, and how are they covered under this new model? <\/p>\n\n\n\nA:<\/strong> All Standard Standalone flows hosted in managed environment that got created via the Power Automate Studio or outside of the studio (via SPO, Teams, Outlook\u2026) are basic flows in managed environment that can be run if the user has a Power Apps Premium license, or a Power Automate Premium license. <\/p>\n\n\n\nQ: Flow using SQL<\/strong> in an environment used by a user with a Power Apps Premium<\/strong>; Does the user need an Automate Premium License? <\/p>\n\n\n\nA: Yes, they need a Power Automate License.<\/strong> When the flow is not running in the context of a Power App and is using a premium connector like SQL, then a Power Automate Premium license is required. The Power Apps Premium licenses does not cover standalone cloud flows with premium connectors unless the flow is directly associated with or triggered by the Power App. <\/p>\n\n\n\nQ: Desktop flow <\/strong>in managed environment with desktop DLP <\/strong>used by a user with a Power Apps Premium. <\/strong>Does the user need an Automate Premium License? <\/p>\n\n\n\nA:<\/strong> Yes, they need a Power Automate<\/strong> Premium License<\/strong>. Desktop Flows (RPA) require a Power Automate Premium License<\/strong>, regardless of the user’s Power Apps license. The Power Apps Premium license does not cover desktop automation or RPA scenarios. <\/p>\n\n\n\nQ: User with a Power Automate Premium License that starts to use a premium Power App;<\/strong>
Do they need a Power Apps Premium license? <\/p>\n\n\n\nA: Yes, they need Power Apps<\/strong> license. A Power Automate Premium license<\/strong> does not include access to Premium Power Apps.<\/strong> To use Apps in managed environment or to use premium Power Apps (Apps with Dataverse or premium connectors), the user must also have a Power Apps Premium license<\/strong>.
Note: If the user was assigned the premium Power Automate licenses just to use basic flows in a managed environment (vs. for the use of RPA or premium flows), admins can remove that assignment once the Power App Premium is assigned.<\/em> <\/p>\n\n\n\nQ: A user with a Power App Premium license creates a new standalone flow via Power Automate studio<\/strong> and the flow only uses standard connectors <\/strong>(SharePoint, Outlook\u2026).
Does the user need a Power Automate Premium? <\/p>\n\n\n\nA:<\/strong> No,<\/strong> Power Automate is not required. Standard flows do not require an additional premium license, so the user can run the flow in a managed environment using their existing Power Apps<\/strong> Premium license<\/strong>. <\/p>\n\n\n\nQ: A user sets up an independent flow in an environment that integrates with Dataverse<\/strong> as part of a data management process and not triggered by any Power App. Does the user need a Power Automate Premium License? <\/p>\n\n\n\nA: Yes, a Power Automate Premium license is required.<\/strong> Since the flow uses Dataverse<\/strong>, which is a premium connector<\/strong>, the user needs a Power Automate Premium license<\/strong> to use this flow when it is not in the context of a Power App. <\/p>\n\n\n\nQ:<\/strong> A user with a Power Apps Premium license<\/strong> creates a flow using AI Builder<\/strong> (e.g., extracting text from documents) within an environment. Does the user need a Power Automate Premium license? <\/p>\n\n\n\nA:<\/strong> Yes, a Power Automate Premium license is required<\/strong>. The use of AI Builder<\/strong> is considered a premium feature within Power Automate, so even though the user has Power Apps Premium license, they must also have a Power Automate Premium license<\/strong> to run flows with AI Builder capabilities. <\/p>\n\n\n\nQ:<\/strong> A flow using a premium connector<\/strong> is shared with a team of 10 members. The flow runs within a managed environment, and all users need access to edit or trigger the flow. Some users have Power Apps Premium licenses<\/strong>, while others have Power Automate Premium licenses<\/strong>. What is required? <\/p>\n\n\n\nA:<\/strong> All users who need to interact with or trigger the flow must have Power Automate Premium license<\/strong>. Power Apps Premium licenses<\/strong> do not cover editing or running a standalone flow with a premium connector outside the context of an app<\/strong>. <\/p>\n\n\n\n<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
In response to customer feedback and a commitment to empowering organizations with more advanced governance and security capabilities, we\u2019re making an update to our managed environments licensing model. At Microsoft Ignite we are announcing managed environments capabilities are included with existing Power Apps Premium or Power Automate Premium (Power Platform user licenses). Here\u2019s what this<\/p>\n","protected":false},"author":458,"featured_media":125993,"comment_status":"closed","ping_status":"closed","template":"","it-pro-content-type":[3293],"it-pro-tags":[3296,3306],"it-pro-product":[],"it-pro-topic":[],"coauthors":[1280],"class_list":["post-126319","it-pro","type-it-pro","status-publish","has-post-thumbnail","hentry","it-pro-content-type-announcements","it-pro-tags-announcement","it-pro-tags-governance"],"yoast_head":"\n
Announcing exciting updates to managed environments licensing - Microsoft Power Platform Blog<\/title>\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n\n\n\t\n\t\n\t\n