Automating Flow for Sending Email

[warren]

Hi,

I have a scenario where i maintain a list of subscribers (external users) in sharepoint online list. The idea is to then send an email to whoever is in this list whenever there's an update in an event.

Looks like there is a limit of 500 recipients that can be sent in a single e-mail from office exchange 

https://technet.microsoft.com/en-us/library/exchange-online-limits.aspx#RecipientLimits

As the subscriber list grows, it can potentially go over 500 records of users.

I had a look at the other connector, called 'Mail', but there's no documentation around what is the maximum number of recipient i can have in a single e-mail. 

Are there other connectors or workaround in Flow which can facilitate the scenario in the event that the e-mail has to go out to more than 500 subsribed users?

Advice much appreciated! Thanks

[efialttes]

@warren

I haven't tested it myself, but... assuming the 500 recipents limits applies to a single Flow execution, also that your distribution list is less than 10,000 recipents; and finally there are few updates per day, a potential workaround is to apply nested flows (https://flow.microsoft.com/en-us/blog/build-nested-flows/) 

The main flow would be the trigger itself, then it would get items from the sharepoint list; and calculate the distribution list size. If bigger than 500, this main flow would trim the whole collection into 500 recipents slots, and iterate the slot collection. Each iteration would:

1.-invoke a second flow in charge of sending the notification email to the current 500 recipents slot, and

2.-point to the next 500 recipents slot

Hope this helps

[v-xida-msft]

Hi @warren,

There is no email connector could accept more than 500 external recipients that can be sent in a single email in Microsoft Flow currently, if you would like this feature to be improved in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

Best regards,

Kris

[warren]

Hi @efialttes

Thanks for the idea. The nested flow is quite a good read (something i've not come across before), and although it might not entirely work for our case here, it is something interesting which i can bear in mind for future implementation. 

Cheer!