cancel
Showing results for 
Search instead for 
Did you mean: 

Share your ideas and vote for future features

Status: Under Review
Status: Under Review
Status: Under Review

Thank you for your patience as we review this idea. We do understand the points made in all the comments, and the business justifications. I may reach out to some of you to discuss further, and look foward to exploring options with you!

 

Thank you again,

Audrie

Status: Under Review
Status: Under Review
Status: Under Review

Thank you for your patience as we consider opportunities related to this excellent idea. We will keep you updated as we solidify options.

 

Audrie

Status: Under Review

Thank you for your feedback. We need some more details to understand your suggestion better. Can you please give us a scenario in which there are multiple rules running concurrently and in which adding extra condition checks (IF...ELSE) before the actual actios would not solve work around the issue?
 
Sincerely,
Carlos Mendonça
PM, Microsoft

Status: Under Review
Status: Under Review
Status: Under Review
Status: Under Review
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: Under Review
Status: Under Review

Thank you for the suggestion, this is a great idea.

Status: Under Review

We recognize the high value of this ask, and are evaluating dependencies and timelines for roll-out. I'll keep you posted here as roadmap planning progresses.

 

Thank you,

Audrie

Status: Under Review

This is a great idea, thank you!

Status: Under Review

Thank you for your suggestion.

Status: Under Review
Status: Under Review

Today this can be accomplished by using multiple flows pointing at the same business logic via an HTTP trigger. So for example:

 

Flow 1 with Trigger 1 and HTTP action

Flow 2 with Trigger 2 and HTTP action

Flow 3 with Trigger 3 and HTTP action

Flow 4 with HTTP trigger and your actions

 

This requires n+1 flows (where n is the number of triggers) but enables you to accomplish the scenario. Thanks!

Status: Under Review

We are looking at this. Thank you!

Labels
>