Microsoft restores Power Automate after intermittent flow failures
Microsoft 365 service status records show Power Automate issues on 1 June 2026 affecting app and flow behaviour. The notice also lists failures around approvals, flow management operations, manual flow invocation, and desktop-flow portal views. The service was later marked restored. The public status mirror does not provide a detailed root cause or a complete regional breakdown.
Before this incident, most non-developer makers assumed a failed flow meant something was wrong with their trigger, connector, data, or permissions. A platform-level interruption often only becomes visible after an approval stalls or a notification never arrives. That is the practical lesson here. Power Automate can still fail outside the maker’s control, so production flows need visible owners, failure alerts, and a manual fallback for the work that cannot simply wait.
Analysis
Add a failure notification and owner check to every production flow. For critical approval or request flows, keep a simple manual fallback so work can continue if Power Automate is degraded.
Source note
Pulse published by Collab365 Spaces. Cite as "Microsoft restores Power Automate after intermittent flow failures", Collab365 Spaces. 1 source referenced.