Showing results for 
Search instead for 
Did you mean: 

Share your ideas and vote for future features

Status: Declined

Hi all,


After thoroughly reviewing this idea, we have decided not to proceed with this idea for a couple of reasons.

  • SharePoint events are no longer event receiver based and are performed using webhooks or polling where applicable
  • Other Office 365 applications and internal systems like auditing may and will rely on such changes like updates to items, files and other entities in SharePoint

However, that said, we understand the crux of the issue which is to help avoid loops. We will work with the flow team to come up with a generic model/pattern that applies across data source/connections for similar scenarios.


Thanks all for your input and please submit/vote your ideas as we are actively monitoring the ideas forum.




Status: Declined

We do not plan to allow the customization of the formatting of these emails. However, you can use rich text in the Approvals actions themselves (see here), and we plan on adding custom options to these actions (see here).

Status: Declined

We do not plan to allow the adding of comments for  these emails. However, we plan on adding custom options to the Approval connector actions (see here), which should accomplish this same scenario.

Status: Declined

We not plan on adding this feature, but you can already accomplish something almost identical to this via two different mechanisms. If you want a generic email like, that's supported via the Mail - Send an email notification action.

mail - send email action.JPG


This connector works the same as the normal connectors, but instead of using a user account it acts as its own Flow based connector. Therefore when you send emails using it, the message will read as coming from and display like the following:


mail send email header.JPG


Alternatively, if you want it to come from an email inside the domain you can do that by using a Shared mailbox, as called out below in the comments.


Status: Declined

We don't have any plans to change (or add to) the behavior of Switch Case. Switch case is a common programming concept, as as best as we can tell, each branch is always about each Case equaling a value. This type of scenario can already be accomplished today in 2 ways though:


1. You can use nested conditions -- in each condition you can evaluate using whatever expression you'd like.

2. You can use nested if() expressions inside the Switch On.


Personally, I would recommend #2 as that keeps your flow clean - rather than nested conditions which can be difficult to work with. If you had 3 cases it would look something like:



    or(contains(variables('foo'), 'good'), contains(variables('foo'), 'great')),



        contains(variables('foo'), 'bad'),


        if(contains('variables'), 'ok'), 'NeutralCase', 'DefaultCase')




One other thing I'd like to point out is that this approach also gives you much more flexibility than you could ever had if we added contains() to switch case -- for example, you could go down a branch if a string contained one string OR another string.

Status: Declined

This is an interesting idea. However, at this time we don't have any plans to allow the offline execution of flows. Flows are tied to the service and only are capable of running there. Thank you!

Status: Declined

There is a difference between licensing product features in an application (like Microsoft Flow) and permissions to access an application in the first place.


Licenses can be used to grant or remove features. For example, if I want to enable the custom connector feature I can assign the Flow Plan 1. If you enable/disable the Flow for Office 365 plan, that enables the features that come with that plan, such as Team flows.


However, licenses shouldn't be used as a mechanism to grant/remove access to the whole applications (to block/allow login in the first place). For that, Azure AD is the recommended approach. You can use Azure AD conditional access to ensure that users in your organization login in the right place, or even blocked entirely. You should be using conditional access if security is your concern, not licenses.

Status: Declined

We no longer plan any improvements with our Windows phone integration.

Status: Declined

We are no longer planning to build this connector as is being retired. please read more about this announcement here: