Does Business Central have native approval workflows?

Yes. Business Central ships with a built-in Approvals feature using workflow rules tied to approval user setup. It handles simple, single-approver chains well, but has no native Microsoft Teams approval card, and notifications depend on the BC job queue running on schedule.

Why do Business Central teams use Power Automate for approvals?

Power Automate is Microsoft's own suggested workaround for routing Business Central approvals into Teams or Outlook, since BC has no native Teams card. It works, but it adds per-user licensing cost at scale and creates a dependency on whoever built the flow — a documented risk when the institutional knowledge of how it works lives with one person.

What's the alternative to Power Automate for Business Central approvals?

OpsGrid routes Business Central approval decisions directly into Microsoft Teams with a named owner, a full audit trail, and human-in-the-loop write-back to BC — without a per-user Power Automate license or a single-builder dependency.

Does adding an approval layer slow down Business Central operations?

Not when it's built as a governed routing layer rather than a manual escalation chain. The goal is getting the decision to the named right person with the context they need — not adding approval steps that don't already exist today.

← All insights

Collection

Business Central approvals — native limits and real alternatives

Business Central ships with a working Approvals feature. It also ships with real limits: no native Microsoft Teams approval card, routing rules that don't flex by amount or department without customization, and notifications that silently stop the moment the job queue goes down.

Most teams patch this with Power Automate — Microsoft's own suggested workaround. It works, until the person who built the flow leaves and nobody else knows which SharePoint list it's watching.

The piece below covers both ends: where Business Central's native approval engine actually breaks down, and what a governed alternative looks like when licensing cost and continuity risk both matter.

Article

Business Central · Approvals · Power Automate

Business Central's approval engine can't approve anything alone — and neither could the flow you built to fix it

A purchase order sits in approval limbo for six days — not because no one wants to approve it, but because the Power Automate flow that used to route it was built by someone who left in March. What BC's native approval engine actually covers, where Power Automate picks up the slack and what it costs, and what a governed alternative looks like.

Why this cluster exists

Business Central's approval engine is often treated as a solved problem — it exists, it technically routes approvals, so the conversation moves on. In practice, most mid-market teams running BC hit the same three walls: no native way to approve from Microsoft Teams, routing logic that requires developer time to change, and notifications that depend entirely on a background job queue nobody watches until it's already broken.

The default fix is Power Automate — reasonable, since Microsoft recommends it. But a workaround built by one person, undocumented, and never reviewed for what happens when that person leaves is not a governance model. It's a new single point of failure wearing the old one's clothes. This cluster covers what actually breaks, what the workaround costs at scale, and what a named-owner, audited approval layer looks like instead.