Message ID: MC1056010
Starting in June 2025, we are updating the prerequisites for sharing cloud flows. With this update, users must be members of the environment where the flow is located.
How does this affect me?
Currently, a flow can be shared with a user who is not a member of the environment in which the flow resides. If shared as a co-owner, the user can modify and run the flow. Following this upcoming change, users will instead receive an error message indicating they do not have access to the flow.
What action do I need to take?
Please review your list of shared flows for users who have access to the flow but not the environment it resides and consider providing them with access to the environment.
Source: Microsoft
The upcoming changes to the flow sharing experience in Power Automate, set to take effect in June 2025, are certainly going to stir the pot for both admins and users alike.
For admins, this update means a bit of a shift in how access is managed. Currently, admins can share flows with users outside of the environment, which has its perks—think of it as inviting a friend to a party even if they don’t live in the neighborhood. However, come June 2025, it’s going to be more like a gated community where only residents can join in on the fun. This means admins will need to take a proactive approach, reviewing the list of shared flows and ensuring that all users have the necessary access to the environments where those flows reside. While this may seem like extra work, it could also lead to a more secure and organized flow management system in the long run.
For users, the impact is quite straightforward. If you’re someone who has been enjoying the luxury of using flows without being a member of the environment, brace yourself for a reality check. An error message will now greet you instead of the usual seamless access. This is a bit like showing up to a concert only to find out you forgot your ticket—disappointing, but it does encourage everyone to double-check their access before diving in.
Overall, the changes are likely to enhance security and clarity within the Power Automate ecosystem, though they may introduce some initial bumps along the way. The shift will encourage better collaboration and ensure that everyone involved is on the same page—like a well-rehearsed dance routine!
I’d love to hear what others think about this update! Do you foresee any challenges or benefits in your workflows? Feel free to share your thoughts and experiences in the comments below. And for more insights on Power Automate and other related topics, check out more posts at mwpro.co.uk!