We have had an issue that seems to be caused by a microsoft update or something of that nature...
In the past everyone in our team (every one that was members of the IDP Group on SharePoint) could see flows created by other team members under the team flows section of PowerApps:
Now, we can only see flows that were specifically created by us or that have been specifically shared with our email account...
See the screen shot below. In the past, We could see flows as long as they were shared with "IDP Group" (highlighted in yellow).
Now we can only see flows directly shared with us personally (highlighted in red).
This is an issue, because members of the IDP group are constantly changing! We do not want to have to share every flow that is ever created with every team member!
Thanks for your time
Hello Ethan,
Perfect and Awesome, so this means the issue is not with the O365 group but with your environment, that's why I wanted you to test this.
I would request you in this case to immidiately talk to the Support guys, this is looking a bit weird and does not happen by design.
https://flow.microsoft.com/en-us/support/
If this reply has answered your question or solved your issue or helped you get insights on the issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
So we created a new flow and shared it with our team and then we were able to see all of our flows again! Unfortunately, they all disappeared again in about 20-30 minutes...so it seems like a quick fix is to create a flow and share it with the team, but it does not permanently fix our issue...
Hello Team,
Doesn't seem like there is update of any kind around this.
One thing is sure that if the GROUP that you shared the Flow with is an O365 group then all the members in that group should be able to see that Flow as a team flow.
I think something might have gone bad in your environment or to be more specific with your O365 group.
For debugging this you may want to create a simple Flow with a trigger and an action, share it with the O365 Group and check if the Flow is becoming visible as a team flow to all the members belonging to that group as a Team flow.
If you still experience this, create a new group and test with that, this has to give you some insights if the Issue is with your Environment or your O365 group.
If the issue is with the GROUP well this is fixable but if this is with the Flow environment nothing you can do other than raising a ticket with Microsoft.
https://flow.microsoft.com/en-us/support/
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
Michael E. Gernaey
497
Super User 2025 Season 2
David_MA
436
Super User 2025 Season 2
Riyaz_riz11
244
Super User 2025 Season 2