BuilderVault
FreeIntermediatePower AutomatePower AutomateMicrosoft 365SharePoint

Route approval to a user's manager

Learn how to use Power Automate Route approval to a user's manager with practical Power Automate guidance, implementation steps, common mistakes, troubleshooting, and related BuilderVault patterns.

Power Automate Route approval to a user's managerhigh intentIntermediate

What this pattern solves

Power Automate Route approval to a user's manager is a practical BuilderVault pattern for makers and developers who need a repeatable way to handle route approval to a user's manager inside a real Microsoft business app. The goal is to move past trial-and-error and give the builder a clear structure they can adapt to their own screens, flows, lists, tables, or environments.

Use this page when you are deciding how the pattern should work, what supporting data or permissions are needed, and what should happen when the happy path fails. The notes below focus on implementation fit, common mistakes, troubleshooting, and internal links to adjacent patterns so the build stays consistent.

Search intent

Help a Power Platform builder understand when to use Power Automate Route approval to a user's manager, how to implement it, and what mistakes to avoid before using it in a production business app.

Problem

Manual approver selection creates routing mistakes when approval should follow the organizational reporting line.

What the finished pattern should include

  • The flow has a clear trigger, scoped actions, tracked outcomes, and an exception path.
  • Notifications or approvals tell users what happened and what action is required.
  • Support owners can review failed runs without reverse-engineering the workflow.

Solution

Formula / code
Power Automate manager approval route:
1. Trigger from Power Apps or SharePoint item creation.
2. Get item and read RequesterEmail.
3. Office 365 Users - Get manager (V2) using RequesterEmail.
4. If manager mail is empty, route to BackupApproverEmail.
5. Start and wait for an approval assigned to manager mail.
6. Update ApprovalStatus, ApproverEmail, DecisionDate, and DecisionComments on the source record.

Implementation checklist

  • Confirm the Power Automate scenario and the business user this pattern supports.
  • Identify the data source, owner, security model, and exception path before building.
  • Build the smallest reusable version first, then add optional branches or polish.
  • Test with realistic data, permissions, edge cases, and handoff expectations.
  • Link this pattern to its collection, topic hub, and related implementation patterns.

Step-by-step instructions

  • Store requester email in SharePoint.
  • Use Get manager V2 with that email.
  • Handle cases where no manager is returned.
  • Start the approval assigned to the manager's mail.

When to use

  • Employee requests
  • Access requests
  • Expense or exception approvals

When not to use

  • Matrix organizations where manager is not the correct approver
  • Processes with delegated approval rules

Common mistakes

  • Assuming every user has a manager in the directory.
  • Using display name instead of mail for approval assignment.

Troubleshooting

  • If manager lookup fails, test the same user in the Office 365 Users connector and add a fallback approver.

FAQ

When should I use Power Automate Route approval to a user's manager?

Use Power Automate Route approval to a user's manager when the same Power Automate scenario is likely to appear in more than one app, flow, list, table, or environment and needs a repeatable implementation approach.

Does this pattern work with Power Automate, Microsoft 365, SharePoint?

Yes. This pattern is written for Power Automate, Microsoft 365, SharePoint scenarios, but you should still confirm connectors, licensing, permissions, delegation limits, and environment rules before using it in production.

What usually causes this Power Automate pattern to fail?

The most common failure points are unclear ownership, missing validation, weak exception handling, undocumented permissions, and testing only the happy path.

Is Power Automate Route approval to a user's manager beginner friendly?

This pattern is rated Intermediate. Beginners can use the fit guidance and checklist first, while experienced builders can move directly into the formula, flow, schema, or governance details.

Related patterns