cancel
Showing results for 
Search instead for 
Did you mean: 

Share your ideas and vote for future features

Most Recent
Status: Under Review

Thank you for the suggestion. Today, we already support running in user context when there is a user present. For example, if I select a file in SharePoint and start a workflow on that file, that workflow can run in either my context, or the context set up by the author of the flow (as decided by the author). This is possible because we have the user's AAD identity and token when the user is invoking the flow.

 

However, for automated flows that run in the background, we no longer have any securable identity from the end user who happens to cause that event. As a result, we have no way to run on behalf of that user. That being said, we understand that this is important scenario and one we will see if there's some other way to solve.

Status: Completed

You can now organize your flows into solutions. Solutions are like tags or folders. They are like folders in that they can contain flows, plus they can contain other assets like PowerApps, CDS entities etc.... They are also like tags in that a single flow can be in more than one solution - so your not tied to one strict heirarchy. The new Solutions tab is available for any envirnomnet that has CDS enabled. Read more here: https://flow.microsoft.com/blog/solutions-in-microsoft-flow/

Labels

Helpful resources

Labels