Business Central 2026 Wave 1: Read-Only Approval Workflow APIs for Auditing

With Dynamics 365 Business Central 2026 release wave 1 (tracked under Microsoft's AI at Work Roadmap ID 576864 and reaching general availability in June 2026 for Worldwide Standard Multi-Tenant Web environments, aligned with version 28.2 per Dynamics 365 Lab), Microsoft is changing how governance teams inspect the system. The update introduces a set of read-only APIs built specifically on top of the Business Central workflow approval system, paired with a dedicated, isolated permission set designed to keep standard users out while letting auditors, IT administrators, and external analytics engines look in.

Here is a deep dive into how these new approval workflow APIs work, what the underlying endpoints expose, and why separating audit telemetry from everyday ERP access is a major win for governance and AI-driven analytics.

Breaking Approval Data Out of the ERP Silo​

In Dynamics 365 Business Central, approval workflows are the guardrails of separation of duties. According to Microsoft Learn's documentation on approval workflows, organizations rely on these sequences of tasks to govern everything from purchase and sales documents to finance journals prior to posting, new user permissions, and sensitive master-data edits—such as changing a customer credit limit, an item sales price, or a vendor's bank account number. Workflows can run sequentially (where Approver A must sign off before Approver B ever sees the request) or in parallel (where multiple approvers receive requests simultaneously and every single one must approve before the step concludes).

Until now, analyzing how those guardrails actually perform in practice required working largely inside Business Central's boundaries or building bespoke data pipelines. Microsoft's release plan for this feature outlines a cleaner architectural approach: read-only APIs that allow organizations to establish security and auditing analytics outside Business Central.

According to Microsoft's roadmap and release plan documentation, the new read-only APIs allow querying across three core domains:

• Workflows: The structural definitions and states of the approval workflows themselves.
• Workflow and User mappings: How individual users and user groups are assigned, sequenced, and delegated within those approval chains.
• Workflow, User, and Action history: The chronological trail of what happened, who triggered it, and how requests moved from submission to resolution.

As noted in reporting by ERP Software Blog, this capability spans endpoints covering workflows, workflow steps, workflow approvers, posted and open approval entries, and approval user setup—allowing IT staff and auditors to pull approval history into external reporting tools without touching the underlying configuration. Microsoft specifically highlights two primary downstream destinations for this data: building compliance and auditing dashboards in Power BI, and creating intelligent agents using Microsoft Copilot Studio paired with the Model Context Protocol (MCP) Server for Business Central.

Section Summary:

• Feature Scope: Read-only APIs for the Dynamics 365 Business Central approval system (Roadmap ID 576864, GA June 2026).
• Three Query Pillars: Workflows; Workflow and User mappings; and Workflow, User, and Action history.
• Target Integrations: External reporting in Power BI and autonomous or conversational agents via Microsoft Copilot Studio and MCP Server for Business Central.

Under the Hood: Examining the API v2.0 Structure​

What does this look like when an IT administrator or BI developer actually queries the system? While the high-level roadmap announcement describes the conceptual buckets, Microsoft Learn's Business Central API v2.0 reference documentation reveals the exact mechanics of how workflow approver mappings work at the HTTP layer.

For instance, the workflowApprover resource in the Business Central REST API v2.0 exposes the specific approvers configured inside a workflow. To query this data, an external tool or agent issues a standard HTTP GET request requiring an OAuth Authorization: Bearer {token} header against the company route:

GET https://{businesscentralPrefix}/api/v2.0/companies({companyId})/workflowApprovers({workflowApproverId})

Omitting the specific ({workflowApproverId}) returns the collection of all workflow approvers for that company. A successful 200 OK JSON response returns a structured payload detailing the exact state of that approval step. Below is a breakdown of the key properties documented in Microsoft Learn for the workflowApprover object and why they matter to an auditor:

From a practical IT governance standpoint, having read-only GET access to these fields—alongside open and posted approval entry history —takes the guesswork out of compliance checks. Instead of taking screenshots of workflow setup pages to prove that purchase orders over a certain threshold require a direct approver, a Power BI report or a Copilot Studio compliance agent can query the API directly, flag any workflow where enabled flips to false, and cross-reference configured approvers against active directory departures.

Section Summary:

• Standard REST Architecture: Uses standard GET requests under /api/v2.0/companies({companyId})/ authenticated via Bearer tokens.
• Granular Telemetry: Exposes workflow state (enabled), step sequencing, approver limit types, user/group assignments, and modification timestamps.

The Security Boundary: Isolating API Access with Permission Sets​

Exposing approval hierarchies and transaction histories over an API raises an obvious cybersecurity question: If an API can read every approval workflow and user mapping in the company, how do we stop an curious employee from querying it?

Microsoft's answer is a dedicated permission set specifically for the approval APIs. In the feature release notes, Microsoft explicitly warns administrators that this new permission set should not be granted to standard users, though it may be included in security-related permission sets. (Notably, Microsoft Learn's 2026 release wave 1 plan also documents a parallel sister feature introducing read-only APIs for analyzing permissions for auditors and IT staff, showing a coordinated push toward externalized security auditing.)

To understand why this isolation works so well, it helps to look at how Business Central handles access control under the hood. According to Microsoft Learn's developer documentation on entitlements and permission sets, Business Central separates access into two layers:

1. Entitlements: What a customer is licensed to use based on their Microsoft purchase or Microsoft Entra role assigned in the Microsoft 365 admin center.
2. Permissions and Permission Sets: Which specific database objects an administrator or partner grants to a user, bundled into logical sets.

Since Business Central 2021 release wave 1 (version 18.0), Microsoft has defined System permission sets as uneditable AL code objects (PermissionSet and PermissionSetExtension) rather than raw database tables. In Business Central online, end users and administrators cannot directly alter Microsoft's predefined System permission sets; instead, they can assign them as-is or copy them into User-Defined permission sets stored in the tenant database.

By shipping a dedicated permission set for the approval APIs, Microsoft applies the principle of least privilege at the data layer:

• Standard ERP users continue to trigger workflows and approve documents inside the Business Central web client using their normal operational permissions, completely blocked from querying the system-wide approval APIs.
• Service principals, Copilot Studio agents, Power BI connectors, and external auditors can be assigned the isolated approval-API permission set (or a custom security permission set that includes it). They get clean, read-only visibility into the approval logs without needing broad operational write permissions inside the ERP.

Furthermore, because the endpoints are strictly read-only, an external reporting tool or AI agent using these APIs cannot accidentally—or maliciously—approve a bogus invoice, alter a workflow sequence, or delegate an approval to an unauthorized account.

Section Summary:

• Dedicated Permission Set: Microsoft includes a specific permission set to govern access to the new approval APIs.
• Least-Privilege Design: Standard users are excluded by design; access is reserved for security-focused roles, IT staff, and auditing accounts.
• Read-Only Guarantee: External tools can inspect workflow configurations and history without any capability to mutate records or trigger approvals.

How Admins Can Discover and Verify Endpoints​

If you are a Business Central administrator preparing to hand these endpoints over to your BI team or wire them up to an MCP Server for Microsoft Copilot Studio, how do you verify what is live in your tenant?

Beginning in Business Central 2026 release wave 2, Microsoft Learn documents a built-in administrative tool called the API Overview page that streamlines endpoint discovery, though standard API v2.0 discovery methods apply across modern environments. According to Microsoft Learn, administrators using the API Overview page can inspect published APIs directly in the client:

1. Select Search (Alt+Q) in the upper-right corner of Business Central, enter API Overview, and select the related link.
2. Filter the view by API Pages, API Queries, or API v2.0 to narrow down the list of Microsoft and extension-published endpoints.
3. Inspect the Type column: Microsoft notes that while API pages can support read and write operations, API queries provide strictly read-only data.
4. Review the Entity name and select the API URL column to open the endpoint, inspect its metadata, or test a request.

Important Administrative Caveat: Microsoft Learn emphasizes that viewing an endpoint on the API Overview page does not configure the API or grant access to it. You must still configure web services authentication (such as OAuth 2.0 bearer tokens in Microsoft Entra ID) and assign the appropriate approval API permission set to the querying identity before your Power BI dataflow or Copilot agent will receive a 200 OK response.

Expert Analysis: Why Read-Only Audit APIs Are Essential for the Agentic Era​

Looking beyond the immediate convenience of easier SOX or ISO compliance audits, why is Microsoft investing heavily in read-only governance APIs right now?

Based on general industry analysis of enterprise ERP trends, the answer lies right in the roadmap description: Microsoft Copilot Studio and MCP Server for Business Central. As enterprises rush to connect Large Language Models (LLMs) and autonomous agents to their financial backends via the Model Context Protocol (MCP), the biggest hurdle isn't AI capability—it's enterprise risk management. Chief Information Security Officers (CISOs) and CFOs are understandably terrified of giving an AI agent read-write access to an approval engine where a hallucination or prompt injection could theoretically approve a fraudulent wire transfer or alter a vendor workflow.

By carving out strictly read-only APIs backed by an isolated permission set, Microsoft gives IT architects a safe sandbox for AI-assisted governance. You can build a Copilot Studio agent that answers natural-language questions from a controller—such as "Which purchase order workflows had the longest approval bottlenecks last quarter?" or "Show me every workflow where a user group mapping was modified in August"—knowing that the underlying API architecture physically prevents the agent from changing a single byte of ERP data.

Still, IT teams and auditors should keep a few practical realities in mind:

• An API is not a compliance policy: Pulling workflowApprovers and approval history into Power BI gives you visibility, not automatic governance. If an organization builds a sloppy workflow in Business Central that skips a crucial approval step, the API will faithfully report that sloppy configuration.
• Validate completeness and retention: Before retiring legacy audit procedures, compliance teams should test the API responses against Business Central's internal Archived Workflow Step Instances and ledger entries to confirm that their Power BI filters capture every iteration, rejection, and delegation required by their specific regulatory framework.

For Windows and Microsoft 365 administrators who frequently wear the "Business Central admin" hat in small-to-medium enterprises, this update is a welcome relief. You no longer have to choose between locking down your ERP and giving your auditors the data they demand. With read-only approval APIs and granular permission sets, you can hand the compliance team a Power BI dashboard, keep standard users in their lane, and let the data speak for itself.