Skip to content

Multi-Level Automated Approval Chains with Power Automate

Global electronics manufacturer

In short

How do you build a multi-level approval chain in Power Automate?

Getting one approval can take a string of reminder emails, and nobody can say where a request is stuck. We built one reusable Power Automate approval flow that asks each approver in turn and records every answer.

At a glance

  • Approvers asked in order, without reminder emails
  • Approvers see what and why
  • Every decision recorded with time and comment

The client

The client is a global electronics manufacturer where requests such as spend, access and changes need sign-off from several people in different departments. This use case is a shared approval service, not tied to one application.

What it was costing them

  • Chasing: requesters send repeated reminders to get one approval.
  • No view: nobody can see which approver a request is waiting on.
  • Missing context: approvers get an email without the reason, amount or attachments.
  • Weak audit trail: approvals live in mailboxes and are hard to find later.

What we built

We built one parent flow with child flows per request type, so approvals follow rules and not individual mailboxes.

  • Approvers in the right order: the next approver is asked only when the previous one approves.
  • Rules, not people: approver levels are set by amount, category or department in a table, so a rule change needs no flow edit.
  • Context in the request: approvers see what, why, amount and attachments, and decide in Teams or Outlook.
  • No stalling: reminders go out after a set time, then escalate to a delegate.
  • Absences handled: a deputy list covers holidays and leavers.
  • A full audit trail: every decision, time and comment is stored in one table.

Results

  • Result: an automated approval chain, with all approvers taken in sequence and better visibility of what and why.
  • Result: fewer reminder emails, as the flow sends them on a schedule.
  • Result: shorter time to final approval, as stuck requests escalate automatically.

The risk most teams miss

Approval rules go stale. By month three people have changed roles, thresholds have moved and the flow still asks someone who left. We kept approvers in a maintained table with a named owner, used deputies and escalation for gaps, and ran flows under a service account. Requests changed after submission restart the chain.

What we would add today

Improvements we would add on top of what is live.

  • Use Dataverse-based approvals in Power Automate, so approvals are stored in tables you can report on.
  • Run the flows under a service principal with connection references, deployed by Power Platform pipelines.
  • Add a Copilot Studio agent so requesters can ask where a request is and who must approve next.
  • Report cycle time by approval step in Power BI or Fabric to find the slowest step.

Technology

Power Automate (approvals), Dataverse, Microsoft Teams, Outlook, Power BI.

Tell us which approval takes the most chasing today, and we will tell you how to turn it into one automated chain.

Products and capabilities

  • Power Automate
  • Dataverse
  • approval workflow
  • multi-level approvals
  • escalation
  • audit trail

Have a Microsoft project in mind?

Tell us what you need built, fixed or supported. A senior consultant replies within one business day.