Microsoft's Business Central 2026 Wave 1 release plan covers April through September 2026 and includes AI-agent capabilities for sales and purchase workflows. Each feature has its own release status. Before enabling one, verify that the tenant version, data, workflow rules, permissions, exception paths, and human oversight are ready.
What changed in Wave 1
The 2026 Wave 1 release plan for Business Central marks a shift from Copilot-assisted suggestions to agents that initiate and complete order tasks. The wave covers April through September 2026, with individual capabilities releasing on different schedules.
According to Microsoft's Business Central 2026 Wave 1 planned features page, the enhanced Sales Order Agent — supporting multiple agents per company, smarter item matching, relevance filtering, and streamlined setup — is scheduled for general availability in July 2026.
The Wave 1 release notes for Business Central update 28.0 document the dedicated agent task pane and stop-all-tasks capability, which reached GA on April 1, 2026. Microsoft documents these as controls for monitoring and halting agent activity. Verify their availability, permissions, and behavior in your tenant version before relying on them.
Turn the Release Plan Into Tenant Readiness Questions
Microsoft's release documentation describes sales and purchase scenarios, a July 2026 target for the enhanced Sales Order Agent, and April availability for the task pane and stop-all-tasks controls. Metrotechs guidance is to turn those capabilities into tenant-specific readiness questions about record ownership, required fields, permissions, approvals, exceptions, monitoring, and recovery before enabling production actions.
The governance risk that makes this decision urgent
Microsoft describes Business Central agents that can initiate sales and purchase workflow actions. That makes configured data, workflow rules, permissions, and oversight part of the operating risk review.
Consider an incomplete vendor record: a purchase-order line has no active pricing agreement, or two codes could match. Metrotechs analysis is that the deployment test should verify whether the configured agent stops, routes the exception, requests review, or applies a defined rule. If the expected path is not observable and repeatable in testing, keep that case out of the production pilot. The same test applies to sales-order exceptions.
The scenarios above are Metrotechs analysis based on the cited agent architecture and the data dependencies documented in Microsoft's Wave 1 release materials.
What to audit now
The following audit steps are Metrotechs recommendations based on the cited agent architecture and data dependencies.
Sales order master data: Audit customer records, item master entries, pricing tables, and quantity fields for completeness and consistency. Use missing or ambiguous records as test cases, document the expected outcome, and flag unresolved cases before enabling.
Purchase order master data: Review vendor records, product codes, pricing agreements, and approval authority rules. Use a vendor record without an active pricing agreement as an exception test. Resolve the data or document the review path before production use.
Approval workflows and exception paths: Document your current sales and purchase order approval workflows, exception-handling procedures, and escalation rules. Confirm these are configured inside Business Central — not just understood by your team — before any agent runs in production.
Rule-based versus judgment-dependent processes: Identify which order processes follow clear, repeatable rules and which require contextual human judgment. Start pilots with bounded cases whose expected results and exception paths can be tested. Keep the latter in manual or assisted workflows until you have evidence the agent handles edge cases correctly. If your current access configuration does not distinguish agent-initiated actions from user-initiated actions, close that gap before deployment.
Agent task pane and stop-all-tasks controls: Verify that the agent task pane is accessible to the people responsible for oversight, and that the stop-all-tasks capability has been tested in a non-production environment. Knowing how to halt an agent before something goes wrong is not optional.
Expense Agent timing: The Expense Agent with approval-process support is planned for public preview in August 2026, per Microsoft's Wave 1 planned features page. Treat a public-preview feature as non-production scope unless your risk policy explicitly allows preview testing. Revisit its status when Microsoft publishes later release information.
What to watch as Wave 1 continues
The enhanced Sales Order Agent's July 2026 GA target is the next concrete milestone. Confirm the shipped scope against Microsoft's release notes before changing production permissions or workflows.
The Expense Agent's August 2026 public preview may offer early signal on how approval-workflow governance for agents behaves in practice. Whether that preview informs Wave 2 production decisions will depend on what Microsoft publishes at preview and GA. That assessment is Metrotechs analysis based on the cited Wave 1 release plan; treat it as a watch item, not a confirmed capability.
Use the Wave 1 schedule as a prompt to verify tenant availability and readiness, not as automatic permission to enable every capability. Audit first. Enable second.