Governance First Power Automate Approvals for Professional Firms

Power Automate gives you native approval actions, chiefly Start and wait for an approval, that collect, route and record human sign-off across SharePoint, Teams, Outlook and external connectors. The best next step is building a simple flow around a trigger such as a SharePoint “When an item is created” event. Check two things first: whether your environment has a Dataverse database and licence, and whether the approval might run longer than 30 days, which changes how you should design it.

TL;DR:

• Approval flows require a Dataverse database and appropriate licensing, with missing elements causing most initial failures.
• Sequential approvals route requests step-by-step, but approvers cannot be duplicated within the same chain, and clear step naming is essential.
• Custom response options are limited to five buttons in email and Teams, so plan accordingly for more complex decisions or rely on the approvals center.
• Long approval processes over 30 days should split into separate flows to avoid timeout issues, and approvals must be actively surfaced in the approvals center.
• Proper governance includes owner attribution, audit trails, and careful planning to prevent orphaned or unaccountable approvals as workflows scale.

Table of Contents

• What do you need before building approvals in Power Automate?
• What do the approval actions in Power Automate actually do?
• How do you create an approval flow in Power Automate?
• How do you set up sequential approvals in Power Automate?
• Custom responses, Teams cards and Outlook button limits
• How do you test and manage long-running approvals?
• What limits and errors should you plan around?
• A governance checklist for safe approval automation
• What breaks most approval workflows in practice?
• Get help designing approval workflows that hold up under scrutiny
• Sources
• FAQ

What do you need before building approvals in Power Automate?

Approvals in Power Automate rely on a working Dataverse database in your environment. If your environment does not have one, the first approval action you run will typically trigger automatic provisioning, and that step needs an admin present or pre-configured, because it cannot always complete silently in the background.

Licensing matters just as much as the technical setup. Your plan needs to cover the standard connectors, Power Automate itself, Office 365, and often Dynamics 365 components, depending on how the flow is triggered and where approvals get stored, according to Microsoft’s approvals documentation.

Before you build anything, confirm the following:

• Your environment has a provisioned Dataverse database, or you have admin rights to trigger provisioning.
• Your licence tier includes the connectors your flow will use, not just Power Automate’s core plan.
• Non default environments have the Approvals User Dataverse security role assigned to anyone who needs to create or respond to approvals.
• Guest users are checked against your tenant’s external sharing rules, since guest access to approvals can behave inconsistently.
• You have decided between the new designer and the classic designer, since the interface and available triggers differ slightly between the two.

Skipping this checklist is the single most common reason a first approval flow fails on its very first test run.

What do the approval actions in Power Automate actually do?

Power Automate offers three core approval actions, and picking the wrong one is the most frequent design mistake outside of licensing problems.

Create an approval starts an approval request without waiting for a response, letting the flow continue immediately. Use this when you need to fire off a request and handle the response asynchronously, elsewhere in the flow or in a separate flow entirely.

Start and wait for an approval is the one most people need. It pauses the flow until someone responds, then lets you branch on the outcome. Microsoft recommends it as the starting point for most approval scenarios, and it’s what the official get started guide walks through first.

Wait for an approval pauses execution for an approval that a separate action already created, useful when the creation and the waiting happen in different parts of a more complex flow.

Layered on top of these actions are the approval types themselves, and each behaves differently:

• Everyone must approve: every named approver has to respond before the flow moves on, useful for compliance sign off where one dissenting voice should block progress.
• First to respond: the flow proceeds as soon as any one approver answers, ideal for time-sensitive requests with interchangeable approvers.
• Custom responses: you define response labels beyond simple Approve/Reject, useful for nuanced outcomes such as “Approve with conditions.”
• Sequential: approvers respond in a defined order, one after another, rather than simultaneously.

The approvals connector reference notes that response values are case-sensitive in some downstream conditions, so a condition checking for “Approve” will not match a response of “approve” unless you normalise the text first. Pick custom responses when Approve/Reject genuinely doesn’t capture the decision you need recorded, not by default, since more response options mean more condition branches to maintain later.

How do you create an approval flow in Power Automate?

Building a working approval flow follows a predictable sequence, and the step-by-step tutorial from Microsoft uses a vacation request scenario to demonstrate exactly this pattern.

• Choose or build a trigger. A SharePoint “When an item is created” trigger works well for most business scenarios: pick the site and list, and make sure the list has the fields your approval will reference (requester name, amount, category, and so on).
• Add “Start and wait for an approval.” Set the Title to something specific and searchable, not “Approval Needed” but “Expense Approval, £2,400, J. Carter.” Set Assigned to with the approver’s email or a dynamic value pulled from a manager lookup. Write the Details field in Markdown so links, bold text and line breaks render properly for the approver, as recommended in how to automate meeting notes for better operational record-keeping. Choose your approval type based on the logic covered above.
• Add a Condition action that checks the dynamic value Responses Approver response equals “Approve.”
• Configure the True branch to send a confirmation email and update the source SharePoint item’s status column to “Approved.”
• Configure the False branch to send a rejection notice and update the status column to “Rejected,” including the approver’s comments if you captured them.
• Save and test the flow manually, then check that the pending approval appears correctly in the approvals centre before relying on it in production.

Pro Tip: Run your first test with yourself as the sole approver and a dummy record. If the approval doesn’t appear in the approvals centre within a minute, the fault is almost always a missing Dataverse role or a licence gap, not a broken flow.

Common test failures trace back to three causes: the assigned approver’s email doesn’t match an active account, the trigger’s list permissions block the flow’s service account, or a dynamic value from the trigger step wasn’t actually populated when the record was created. Check the flow’s run history for the specific action that failed rather than guessing.

How do you set up sequential approvals in Power Automate?

Sequential approvals route a request through approvers one at a time, each seeing the request only after the person before them has responded. You configure this by selecting the Sequential approval type inside “Start and wait for an approval,” then adding each approval step in the order you want them actioned, as detailed in Microsoft’s guide to setting up sequential approvals.

A common real-world pattern looks like this:

• Step one: the requester’s line manager reviews and approves, often using a dynamic manager token pulled from Azure AD rather than a hardcoded email, so the flow adapts automatically as staff change roles.
• Step two: for spending above a defined threshold, the request routes to finance for final sign off, keeping day-to-day approvals fast while high-value cases still get proper scrutiny.

There’s a hard constraint worth flagging early: you cannot assign the same approver to two different steps in one sequential chain. If your organisational structure means a manager sometimes doubles as the finance approver, you need conditional logic before the approval action, not a workaround inside it.

Name each step clearly, “Line Manager Review” and “Finance Sign Off” rather than “Approval 1” and “Approval 2,” because sequential chains get difficult to audit later if the step names don’t describe what actually happened.

Custom responses, Teams cards and Outlook button limits

Custom responses let approvers pick from labels you define, rather than a plain Approve or Reject. Decide upfront whether you need wait for one response or wait for all responses, because that setting changes whether the flow proceeds after the first answer or holds until every named approver has replied.

There’s a UX ceiling worth knowing before you design a custom response list: Outlook and OWA actionable messages support a maximum of five response buttons. Beyond that limit, Microsoft’s guidance on custom response options confirms that additional choices need to be handled through the approvals centre or a non-actionable message instead.

• Keep custom response labels short and unambiguous, since they render as physical buttons in email and Teams.
• If you need more than five options, plan for approvers to respond through the approvals centre or the mobile app rather than an email button.
• Post approvals into Teams as adaptive cards when your approvers live in Teams day to day, since response rates there tend to beat email for busy staff.
• Reserve email as the primary channel when you need a durable, searchable audit trail outside the Power Platform’s own logs.

Pro Tip: For approvals tied to regulatory sign off, default to email over Teams. Email creates an independent, exportable record that sits outside the Power Platform, which auditors tend to prefer.

How do you test and manage long-running approvals?

Test every approval flow manually before switching on the trigger for live data, then run it again with a genuinely awkward test case (a blank field, a rejected response, a slow approver) to see how the branches behave. Confirm the pending item appears correctly in the approvals centre, since a flow that runs without error can still fail silently if the approval record itself never surfaces there.

Some approvals need to stay open for weeks, not hours: think annual contract renewals or long procurement cycles. Power Automate’s flow runs have their own timeout limits, so for anything that might exceed 30 days, store the approval record in Dataverse and split the process into two flows: one that creates the approval and exits immediately, and a second, separately triggered flow that resumes work once a response arrives, a pattern detailed in the modern approvals tutorial.

• Cancel a stuck approval directly from the approvals centre, which stops the flow waiting on it without deleting the underlying record.
• Reassign approvals to a different approver when the original is unavailable, but only users with the right Dataverse role or ownership on that record can do this, not any flow editor.
• Capture a run log entry every time an approval is created, resolved or reassigned, since this becomes your evidence trail if a decision is ever questioned later.

What limits and errors should you plan around?

Throttling affects high-volume approval scenarios more than most people expect. Connectors, including the approvals connector, enforce call limits per connection, so a flow triggering hundreds of approvals in a short burst can start failing with throttling errors rather than a clean rejection.

Recipient formatting causes a disproportionate share of support tickets. The Assigned to field expects valid email addresses in a specific format, and guest users or shared mailboxes sometimes fall outside what the connector accepts, per the connector reference documentation.

Oversized payloads are the other quiet failure mode: a custom response list with too many options, or a Details field carrying huge amounts of Markdown, can push an approval past size limits and cause the action to fail without an obvious error message.

Work through this checklist when a flow misbehaves:

• Confirm the account running the flow has the correct Dataverse role and an active licence.
• Check every dynamic value populated correctly at the point the approval was created, not just at design time.
• Look for throttling errors in the run history if approvals are created in bulk.
• Verify recipient email formatting, especially for guest or shared accounts.
• Check whether a timeout, rather than a genuine failure, is why a long-running approval never resolved.

A governance checklist for safe approval automation

Before automating any approval, map the decision itself: who currently makes this call, what information they need to see, and who owns the outcome if something goes wrong. Skipping this step is how organisations end up with orphaned approvals nobody actually owns once the person who built the flow moves on, a pattern Pattrn Data’s own governance guidance flags repeatedly across client work.

Start with a small, controlled pilot rather than automating every approval process at once. One flow, one clear owner, one measurable outcome, then expand once you know it holds up under real use.

• Keep human review in place for any approval step where judgement, not just data, decides the outcome.
• Persist approval records in Dataverse whenever retention, traceability or long-running timelines matter, not only when a flow technically requires it.
• If Copilot or another AI tool suggests wording, routing or a recommended decision inside an approval flow, treat that suggestion as an input for the human approver to weigh, never as the decision itself.
• Build the audit trail into the flow from day one, not retrofitted after the first audit request arrives.

Pro Tip: Name every approval action after the decision it represents, not the system it touches. “Client Onboarding Sign Off” tells an auditor more in six months than “Approval 3” ever will.

Pattrn Data’s Medical Survey Copilot case study shows this approach applied in a regulated, document-heavy setting, where approval gates and evidence capture sit at the centre of the workflow rather than bolted on afterwards.

What breaks most approval workflows in practice?

The technical build is rarely the problem. Teams automate approvals without deciding who owns each step, and six months later nobody can say who’s actually accountable when a request stalls for a week.

Notifications matter more than most designers give them credit for. An approver who doesn’t know a request is waiting hasn’t refused it, they’ve simply never seen it, and a flow that can’t distinguish between those two outcomes will frustrate everyone involved.

Resist the urge to automate every approval process across the business in one project. A small pilot, measured properly, teaches you more about where governance actually breaks than a comprehensive rollout ever will.

— Rohit

Get help designing approval workflows that hold up under scrutiny

Building the flow is the easy part. Deciding who owns each approval step, what gets logged, and how AI suggestions stay inputs rather than decisions is where most Power Automate projects quietly go wrong. Pattrn Data works with professional services firms and operations-heavy SMEs to map those decisions before a single flow gets built, using AI workflow automation that keeps humans accountable for judgement calls.

If your firm is looking at Copilot, Dataverse or approval-led automation and wants a clear-eyed view of where the risk actually sits, an AI readiness assessment is the sensible next step. It maps your current workflow, flags where governance gaps sit, and gives you a controlled pilot to start from rather than a big-bang rollout. Book an assessment and get a plan you can actually defend to a client or a regulator.

Recommended

• How should professional services firms connect AI governance and workflow controls
• What ethics and review rules should a professional services firm apply when automating client work
• How should a firm decide which AI tools are approved, including risk tiers, for client work
• What client-data boundaries should a professional services firm maintain when using AI