A few weeks ago, news broke about an enforcement in Power Automate licensing, referred to as "Non-compliant" flows. This started conversations, questions, and concerns among colleagues, customers and people within the programming community. It raised awareness on the potential shut down of numerous flows during the summer holiday season. Understandably, this blog post was created to explain the forthcoming licensing enforcement in Power Automate.
Microsoft has announced that they will commence licensing enforcement in Power Automate, which implies that flows which don't meet the specified requirements will be deactivated. If these changes are not duly noted and necessary actions are not taken by administrators or makers, it may result in problems as the current functionality may abruptly stop working. This information aims at easing understanding and creating awareness for all Power Automate flow users.
With the new enforcement, there are implications for Power Automate flows. Essentially, Microsoft requires all flows to be licensed correctly. However, what does "correctly" mean in this context? If the flow owner has an appropriate license, then everything is fine. Thus, understanding what a "proper" license means is critical for operation continuity in light of these new changes. More information will be required on what constitutes a "proper" license.
Read the full article Upcoming Licensing enforcement in Power Automate explained
Microsoft is set to begin enforcing licensing requirements for Power Automate flows. This means that any flows that do not meet these requirements will be turned off. This enforcement will apply to any Power Automate flows, and Microsoft has outlined what they require from a flow in order for it to be considered compliant. In order to be compliant, a flow needs to be licensed correctly. This means that the owner of a flow must have a valid license from Microsoft. Valid licenses include Office 365, Business Premium, E3, or E5. It is important to note that even if a flow meets these requirements, it must still be used within the limits set by the license agreement. Additionally, any flows that are used by multiple people must be shared with all users, and the owner of the flow must have the proper license for each user.
In order to prevent any disruption to a flow's functionality, it is important to understand the licensing requirements and to ensure that the flow is properly licensed. If the flow is not properly licensed, the owner of the flow must take action to obtain the necessary license before the enforcement begins. Microsoft has outlined the upcoming enforcement and the licensing requirements in more detail on their learning sites. It is important to review this information and to make sure that any flows are compliant before the enforcement begins.
Power Automate Licensing Enforcement, Power Automate Licensing Requirements, Microsoft Licensing Enforcement, Microsoft Licensing Requirements, Upcoming Licensing Enforcement in Power Automate