An approval flow using Power Automate’s “Start and wait for an approval” action can be set up in a few minutes. The real work is what the flow does when the approver goes on leave, the request changes midway or a connection drops. In corporate approvals such as purchasing, leave, document publishing and access rights, problems almost always come from these exceptions. The framework below explains step by step how to design an approval process that produces audit evidence and doesn’t silently stop. Track approvals and version changes of flows put into production with IT change and configuration management records.
1. Write down the approval matrix
Before the flow is drawn, these questions should be answered: Who approves? Under what conditions (amount, category, department) does the approver change? Are approvals sequential or parallel? On rejection, does the request go back to the requester or close? Example:
| Condition | Step 1 | Step 2 | Step 3 |
|---|---|---|---|
| Amount ≤ 10,000 TL | Department manager | — | — |
| 10,000 – 100,000 TL | Department manager | Finance | — |
| > 100,000 TL | Department manager | Finance | General manager |
Threshold values and approvers shouldn’t be written into the flow; they should be read from a SharePoint list, so that the flow can be updated without being changed when the organization changes.
The picture we come across most often in the field is this: the finance manager’s email address is hard-coded in the flow, the manager changes and the new person never receives an approval. Requests go to the old address. Nobody notices. Resolve the approver through a role: “Finance approver” is a list record, and the person is a field inside that record. For the department manager, the “Get manager” action in the Office 365 Users connector can be used; but this depends on the manager field in Entra ID being kept accurate.
2. Choose the right approval type
- Approve/Reject – everyone must approve: Situations that need a joint decision (e.g. both quality and production approval).
- Approve/Reject – first to respond: When any one of several people with the same authority is enough (e.g. anyone from the finance team).
- Custom responses: Options such as “Approve”, “Reject” and “Request information”.
- Sequential approvals: The result of each step triggers the next; on rejection, the flow stops.
The “Request information” option looks easy on paper but requires a loop in the flow: a notification goes to the requester, the requester updates the record and the approval restarts. This loop is built with “Do until” and must be given an upper limit (a maximum number of iterations or a duration). Without a limit, the flow waits forever.
3. Design the exceptions
- Delegation: If the approver is on leave, who is the delegate? A delegation list should be kept and checked before approval.
- Reminders and escalation: A reminder if there’s no response after 2 business days, and redirection to the senior manager after 5 business days.
- Request changed or withdrawn: The pending approval should be cancelled and the requester notified.
- Approving your own request: If the requester is also the approver, it should be redirected to a senior manager (segregation of duties).
For reminders and escalation, a single-action “start and wait for an approval” structure isn’t enough, because that action blocks the flow until a response arrives. The practical solution is to create the approval with “Create an approval”, then wait with “Wait for an approval” and give the wait step a timeout. When the timeout expires, the “Configure run after: has timed out” branch runs; there a reminder is sent or the request is reopened to the senior manager. Give durations in ISO 8601 format (for example P2D for two days).
4. Write the decision to a record
Flow run history is kept for a limited time on the platform and isn’t suitable as audit evidence. The result of each approval step should be written, with the approver, decision, comment and timestamp, to the request record or to a separate “approval history” list. That way reporting is possible, and in an audit the question “who approved this request, and when?” is answered with one click.
The approval history list should carry at least these fields: request ID, step number, approver, whether a delegate, decision, comment, decision time. Only the service account the flow runs under should have edit rights to this list. A log where users can change their own approval record isn’t evidence.
5. Error handling
In corporate flows, errors shouldn’t go unnoticed. The recommended structure: the main operations in a “Try” scope, a “Catch” scope that runs on error (Configure run after: has failed / has timed out), and within that scope an error notification and a write to an error log list. For transient errors, a retry policy is defined at action level.
Add the flow name, run ID and request number to the notification in the Catch scope; the workflow() expression gives the run information and lets you link directly to the run history in the notification. The notification should go to a distribution group or a Teams channel, not to a single person. An error that drops while the flow owner is on leave is an error nobody sees.
6. Ownership and connections
A flow created with an employee’s personal account can stop when that person leaves or changes their password. Corporate flows should run within a solution, with connection references and a service account or application identity; more than one owner should be defined. Environment-level DLP policies prevent business data from being passed to unapproved connectors.
Separate the environments from the start too: development, test and production. A purchasing flow built in the Default environment and running with personal connections stops on the day an employee who has left has their account closed. A flow inside a solution, on the other hand, is moved to another environment by changing the connection reference; there’s no need to rebuild the same flow by hand.
7. Test scenarios
- Does the approval chain go to the right people for each threshold?
- Do the rejection, request-information and withdrawal scenarios work?
- If the approver is on the delegation list, does it go to the delegate?
- Are reminder and escalation times correct?
- When a connection error is simulated, does the error notification arrive?
In threshold tests, also try the boundary values: exactly 10,000 TL and exactly 100,000 TL. Mixing up “less than” and “less than or equal to” in the condition expression is the most common logic error, and it only shows up at the boundary value. For escalation tests, reduce the durations to minutes in the test environment; waiting two business days isn’t a test.
A note on licensing
Flows built with standard connectors such as SharePoint, Outlook, Teams and Approvals can be used on most Microsoft 365 plans. Premium connectors such as HTTP, SQL Server, Dataverse or ERP connectors require Power Automate Premium or per-app/per-flow licensing; this should be verified at the design stage.
Don’t leave the licensing check to the end of the project. A single step that writes to the ERP makes the whole flow premium; this may require a license for every user who triggers the flow, or for the flow itself. Verify current licensing terms in Microsoft’s Power Platform licensing guide.
Frequently asked questions
What’s the difference between “everyone must approve” and “first to respond”?
In the Approvals action, the “Everyone must approve” option waits for all approvers to approve; if one rejects, the outcome is rejection. “First to respond” takes the decision of the first person to respond as the outcome; it’s for cases where any one of several people with the same role is enough.
What happens if an approval waits longer than 30 days?
Cloud flow run time is limited; a timeout should be defined for long-waiting approvals, and when it expires the approval should be escalated, or the request managed with a status field and a new flow triggered.
What if the approver doesn’t use Teams?
The Approvals action accepts decisions through Outlook email, Teams and the Power Automate approvals center; the user can respond from whichever channel they prefer.
To design your approval processes together, see our Power Automate approvals and automation and form, request and approval systems services.