Adding user to Microsoft Automatic email about Power Flow Failures

[Anonymous]

Hello - I hope this is the correct board for this.

My peer created some Flows for our business, and when they fail, he receives an automated email from Microsoft listing the failures and errors.

He'll be going on LOA in Q4 and I'd like to be added to that email from Microsoft (the alternative is to add an email portion to each flow, which would be time consuming).

Is anyone aware how or where to make this change?

Thank you.

Dan Kay

[trice602]

Hi @Anonymous 

A best practice is to have production flows run on a service account (as the owner) and you can monitor those emails in that inbox.  Plus there's a lot of business continuity advantages not running production flows on an individual account, as-in, when they are LOA or PTO, or resign, there are issues in production.

Those failure emails automatically go to the registered flow owner, here's a easy work around band aid alternative:

You can have your associate create a rule in their inbox and forward emails from PowerAutomateNoReply@microsoft.com to you.

Please mark as a solution and give me a thumbs up if that works for you!  Always glad to help!  Tom

[trice602 · Accepted solution]

Another option, if you are only monitoring a handful of flows, you could be added as a co-owner (provided you have the licensing), and you can go directly to the flow page and see the run history there too (and see failures).

[Anonymous]

Thank you for your replies, Tom (-:  We discussed using the forwarding option, and there's a danger that his system access will be removed during his LOA and if that happens the emails would just bounce back to Microsoft.  It sounds like there's no "easy fix" and the next solution is to add a failure condition that sends me an email for every failed flow.

Again, thank you for taking the time to respond to my question!

Dan Kay

[trice602]

Understood.  If his account is inactivated during an extended period, the flows will not be available if you add steps to email you since he is flow owner.  Instead of editing each flow and trying to add notifications for you (if you can't use a service account option), another easy way may be to make you the flow owner on each flow and add your colleague as a co-owner.  That's an easy fix and will also solve the LOA issue.  Always glad to help! Tom

[Anonymous]

That's a terrific idea - swapping ownership while he's out.  Thank you again for your help.