Skip to content
home

Power Automate Approvals with Multiple Approvers

One approver is easy. The questions start when a request needs two managers, a whole committee, or finance after the line manager. Power Automate handles all of these. You only need to pick the right approval type and read the results correctly. Here is how I set each pattern up.

Quick answer

Send one approval to several people in Power Automate: first to respond, everyone must approve, majority votes, sequential steps and approvers from a list.

Daniel AwokunleDaniel AwokunleUpdated 11 November 2026 4 min read

1. Add several approvers to one approval

In the action 'Start and wait for an approval', the Assigned to box takes more than one email address. Separate them with a semicolon:

anna@yourcompany.com;ben@yourcompany.com;carla@yourcompany.com

Each person gets the request by email and in the Approvals app in Microsoft Teams. What happens next depends on the approval type, which is the next step.

2. Choose between first to respond and everyone must approve

The Approval type decides who has to answer:

  • Approve/Reject - First to respond: the first answer closes the approval. Use it when any one of several people can sign off, such as a team inbox of managers.
  • Approve/Reject - Everyone must approve: the outcome is Approve only if all assigned people approve. Use it when every person has to agree, such as two directors.

Once the approval is closed, other people who open the request see that it has already been answered.

3. Use custom responses when two options are not enough

Custom Responses - Wait for one response and Custom Responses - Wait for all responses work the same way, but you write the options yourself, for example Approve, Reject and Needs more info. In the flow, the Outcome is then the text of the option chosen, so your Condition must compare against that exact text.

4. Read each person's answer and comments

After the approval finishes, the action returns a Responses list with one entry per approver. Each entry has the responder, the response and their comments. To list them all in an email, add a Select action and use this as the input:

body('Start_and_wait_for_an_approval')?['responses']

Map the text to something like the responder's name, a dash, the response and the comments. Then put the output of the Select in your email or Teams message. Change the action name in the expression if you renamed yours, with underscores in place of spaces.

5. Approve by majority

There is no built-in majority option, but it takes one expression. Everyone must approve is the wrong type here, because it needs every vote. Use 'Custom Responses - Wait for all responses' with the options Approve and Reject, then count the approvals yourself in a Condition:

length(filter(body('Start_and_wait_for_an_approval')?['responses'], equals(item()?['response'], 'Approve')))

Compare that number with half of the total approvers. If it is greater, treat the request as approved.

6. Run approvals one after another

When the order matters, chain the approvals. Add a first 'Start and wait for an approval' for the line manager. Then add a Condition that checks the Outcome is Approve. Only in the Yes branch, add a second approval for finance or the director. A rejection at stage one ends the process there, and the requester is told straight away.

To run approvals at the same time instead, put two approval actions in parallel branches, and join them with a Condition after both finish.

7. Take the approvers from a SharePoint list

Do not hard-code emails into the flow. If the list has a Person column set to allow multiple selections, the value is a list of people. Add a Select action over that column, map its Email, then join the result into the text that Assigned to expects:

join(body('Select'), ';')

Now changing the approvers means editing a list item, not the flow.

8. Handle approvers who never answer

Open the approval action's Settings and set a timeout, for example P3D for three days. Then add a path that runs when the action times out, using Configure run after. Use it to remind the approvers, escalate to a manager, or tell the requester what is happening. Always test the rejection and the timeout path as well as the happy path.

Want this done for you?

I build this for clients every week. Book a free 30-minute call and I'll tell you exactly what your team needs.

Free: the Microsoft 365 clean-up checklist

The 12 checks I run before building anything in a client's tenant: security, sharing, files and quick wins. Two pages, PDF.

Used only to send the checklist and the odd useful tip. Never shared or sold.

Daniel Awokunle · replies within a day

Tell me what's slowing your team down.

Thirty minutes, no cost, no pitch deck. You'll leave knowing exactly what to build and what it should cost.

Book a free 30-min call
  1. Step 1

    Free 30-min call

    Show me the problem. I'll tell you what I'd build and how long it takes.

  2. Step 2

    Clear quote

    A fixed price and timeline in writing, usually within a day.

  3. Step 3

    Built and handed over

    Built in your own Microsoft 365, with a walkthrough for your team.