Makers check out-of-office status before sending Power Automate approvals
Reviewed by Helen Jones
A community tip published 17 September 2026 shows a practical Power Automate pattern: check whether a person has an Outlook out-of-office automatic reply set before you send them an approval. The idea is simple. If someone is away, the flow can route elsewhere instead of parking the request on an unavailable assignee. Related recent tips on the same site cover list-column buttons for for-a-selected-item flows and self-healing connector retries. This is a practitioner pattern, not a new Microsoft product feature. It depends on Outlook or Graph access and correct expressions, with no official service guarantee.
Before this kind of check, many citizen-built approval flows still follow the happy path. You pick a manager or owner, fire the approval action, and hope they are at their desk. When they are not, the request sits. Colleagues chase in Teams, someone reassigns by hand, and the flow looks fine in run history even though the business process has stalled. What changed is not the platform itself but a clearer shared pattern for a failure mode you already feel: unavailable approvers. Routing around out-of-office reduces idle requests, but only if the fallback path is explicit. A wrong expression, missing mailbox permission, or silent connector hiccup can break the pre-check the same way a missing reminder breaks escalation. Reliability still means knowing who gets the request next and who learns when the check fails.
Analysis
Treat this as a pattern to test on one real approval that already stalls, not a reason to rebuild every flow. Add an out-of-office pre-check with a named backup assignee and a failure alert to you or a shared mailbox, then watch a week of real runs before you copy it elsewhere.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Makers check out-of-office status before sending Power Automate approvals", Collab365 Spaces. 1 source referenced.