Dynamics 365 Business Central 2026 Release Wave 2 (BC29): Architectural Guide, Features & Mandatory SOAP Deprecation
An authoritative technical guide to Microsoft Dynamics 365 Business Central version 29 (2026 Release Wave 2): Autonomous Payables and Expense Agents, native EDI exchange preview, Page Scripting reaching General Availability (GA), report themes via the Word add-in, manufacturing subcontracting, and the mandatory deprecation of legacy SOAP UI page web services.
1. Executive Summary: The Architectural Shift in Business Central 29 (BC29)
Every six months, Microsoft delivers a major functional release wave for Dynamics 365 Business Central. The 2026 Release Wave 2 (Business Central version 29 / BC29), officially General Available on October 1, 2026, marks a watershed transition from conversational assistive AI into autonomous agentic execution. Concurrently, Microsoft is enforcing long-signaled infrastructural cleanups—most notably the mandatory disabling of legacy SOAP web services on Microsoft UI pages.
Dynamics 365 Business Central 29 (2026 Release Wave 2) introduces autonomous Payables and Expense Agents, General Availability (GA) of the web-based Page Scripting regression tool, a native EDI exchange preview inside E-Documents, unified Word add-in report styling themes, and advanced subcontracting manufacturing workflows. Crucially, Microsoft has enacted the mandatory retirement of SOAP web services published on base UI pages, requiring immediate migration to API pages across all external integrations before the 5-month upgrade window closes in February 2027.
For Chief Information Officers, Controllers, and IT Steering Committees, BC29 requires an active governance posture. Evergreen SaaS delivery removes multi-year reimplementation friction, but it makes continuous sandbox regression testing, integration interface audits, and release scheduling non-negotiable disciplines.
2. Release Cadence & The 5-Month Upgrade Window (October 2026 – February 2027)
Microsoft enforces a strict five-month lifecycle window for major release waves. Tenant administrators do not have an open-ended timeframe to absorb BC29; they must proactively manage their cutover schedule within the Business Central Admin Center:
| Milestone Phase | Operational Window | Target Environment | Mandatory Enterprise IT Action |
|---|---|---|---|
| Early Access Preview | August – September 2026 | Sandbox Only | Spin up preview sandboxes on v29 build to review functional feature management toggles and compile custom PTEs. |
| General Availability (GA) | October 1, 2026 | Global Cloud SaaS | BC29 becomes generally available worldwide. Production environments become eligible for administrator-scheduled cutover. |
| Customer Scheduling Window (5 Months) | October 2026 – February 2027 | Production & Sandboxes | IT leads select an off-peak production cutover date outside critical accounting closing cycles or holiday fulfillment peaks. |
| Mandatory Automated Tenant Cutover | February 2027 Deadline | Unscheduled Tenants | Microsoft automatically applies BC29 to any production environment that has not executed a scheduled upgrade date. |
We strongly counsel enterprise organizations against allowing Microsoft to force an automated cutover in February 2027. Production upgrades should be scheduled intentionally over a planned maintenance window—ideally on a Friday evening following month-end ledger reconciliation—allowing the ERP practice to run automated sanity tests before Monday operations commence.
3. Critical Breaking Change: Mandatory Disabling of SOAP Web Services on UI Pages
While new functional capabilities generate executive excitement, the most urgent technical consideration in Business Central 29 is a hard breaking architectural boundary:
Permanent Retirement of SOAP Web Services on Microsoft Base UI Pages
In Business Central version 29, Microsoft has permanently disabled SOAP endpoints published directly from base UI pages (such as Page 21 Customer Card or Page 26 Vendor Card). Any legacy handheld barcode scanner, mobile warehouse client, legacy EDI gateway, or external portal still communicating via SOAP UI page endpoints will immediately fail with hard HTTP 404/410 errors upon upgrading to BC29.
Historically, legacy implementations used SOAP web services published directly from standard Business Central client pages because they were effortless to toggle in the Web Services page. However, UI pages execute full page-trigger logic, calculate unnecessary FlowFields, and introduce severe locking contention.
The Immediate Remediation Path: Every external service communicating with Business Central via SOAP must be refactored to modern API pages (PageType = API) or OData V4 unbound actions. API pages bypass the UI layout layer, support batch operations with exponential throughput gains, and adhere to zero-trust Microsoft Entra ID authentication. If your organization has not inventoried active web service bindings, requesting a comprehensive BC29 Upgrade & SOAP Audit is an urgent operational priority.
4. The Real Headline Highlights of Business Central 29 (BC29)
Filtering out industry speculation, Microsoft's official 29.0 release deliverables introduce substantial operational leverage across finance, manufacturing, logistics, and quality assurance:
Payables & Expense Autonomous Agents
Building upon conversational Copilot, BC29 introduces dedicated autonomous AI agents for Accounts Payable and Employee Expenses. The Payables Agent ingests electronic invoices, validates PO matching tolerances, and creates purchase invoice drafts automatically. The Expense Agent audits policy compliance and flags out-of-bounds line items before manager sign-off.
EDI Exchange Preview in E-Documents
Microsoft expands the native E-Documents core framework with a preview of direct business-to-business EDI exchange. Organizations can configure electronic purchase order ingestion and electronic invoice dispatch natively without maintaining expensive external Value Added Network (VAN) middleware subscriptions.
Page Scripting Tool General Availability (GA)
The Page Scripting tool inside the Business Central Web Client officially reaches General Availability. Business analysts and QA leads can record end-to-end user transactions, capture parameter variations, and replay automated regression test suites across standard and customized pages without writing custom AL test codeunits.
Word Add-In & Centralized Report Themes
Report layout engineering receives a major usability upgrade. Using the modernized Microsoft Word add-in, marketing and accounting teams can author document layouts with unified corporate branding themes, shared typography, and dynamic color palettes across invoices, purchase orders, and customer statements without RDLC complexity.
Subcontracting Manufacturing Enhancements
Discrete manufacturers gain streamlined subcontractor purchase order generation directly linked to production routing operations. BC29 simplifies sending materials to external vendors, tracking subcontractor inventory at third-party locations, and automatically factoring subcontract fees into finished goods inventory valuation.
Shopify Plus B2B Multi-Location Sync
The native Shopify connector expands native support for Shopify Plus B2B company structures. Organizations can synchronize multiple B2B customer locations, custom tiered price catalogs, draft order approval pipelines, and specific B2B credit terms directly with Business Central sales ledgers.
5. Model Context Protocol (MCP) & Enterprise AI Tool Endpoints
Beyond out-of-the-box Copilot prompts, BC29 refines the foundation for external cognitive reasoning engines. By expanding standardized REST endpoints and structured schema endpoints, Microsoft enables secure connectivity with the Model Context Protocol (MCP).
Through MCP, advanced reasoning models such as Anthropic Claude can safely query customer balances, inventory across multi-bin warehouses, and open purchase orders under zero-trust Microsoft Entra ID OAuth 2.0 credentials without exposing direct SQL access or requiring custom middleware. For comprehensive technical architecture on implementing MCP securely, explore our guide on Claude and Business Central MCP Integration.
6. The 4-Step Enterprise Governance & Upgrade Playbook
To eliminate operational disruption and guarantee business continuity throughout the five-month BC29 deployment window, our enterprise consulting practice executes this four-step engineering roadmap:
Provision Cloned BC29 Preview Sandbox
Inside the Business Central Admin Center, clone your active production environment into a dedicated sandbox running the version 29 preview build. Testing against authentic company data volumes, open orders, and historical master files ensures complete fidelity during validation runs.
Automated Regression Testing via Page Scripting GA & AL-Go
Leverage the newly General Available Page Scripting tool to replay core transactional flows: sales order booking, warehouse release, inventory picking, purchase invoice matching, and payment journal posting. Pair this with AL-Go for GitHub CI/CD pipelines to verify that custom Per-Tenant Extensions (PTEs) compile without obsolete compiler warnings.
Mandatory Web Services Audit (SOAP to API Migration)
Inspect the active Web Services catalog in Business Central. Identify all legacy SOAP entries pointing to base Microsoft UI pages. Refactor external integrations—including warehouse RF scanners, 3PL portals, and e-commerce pipelines—to modern API pages or OData V4 services before scheduling cutover.
Scheduled Off-Hours Cutover & Trial Balance Parity
Schedule the production upgrade date in the Admin Center during an off-peak weekend maintenance window. Once Microsoft completes the cloud database update, our team executes end-to-end trial balance reconciliation, posts test transactions, verifies API heartbeat telemetry, and signs off before Monday morning operations resume.
7. Frequently Asked Questions
Key operational, architectural, and licensing considerations for IT leadership evaluating Business Central 29:
When is the upgrade window for Business Central 2026 Release Wave 2 (BC29)?
General Availability for Business Central 29 (2026 Release Wave 2) began on October 1, 2026. Microsoft provides a 5-month customer-controlled scheduling window that runs through February 2027. During this 5-month period, tenant administrators can schedule their specific off-peak cutover date in the Business Central Admin Center. Once the window closes in February 2027, Microsoft automatically updates any remaining unscheduled production environments.
What is the most critical breaking change in Business Central 29 (BC29)?
The most critical breaking change is that disabling SOAP web services on Microsoft UI pages is now strictly mandatory. Any legacy external integration, handheld warehouse scanner, or desktop utility communicating with SOAP endpoints published from base UI pages (such as Page 21 or Page 26) will fail with hard HTTP errors. Integrations must be refactored to modern API pages (PageType = API) or OData V4 unbound actions prior to tenant cutover.
What are the standout enterprise features introduced in Business Central 29.0?
BC29 headline highlights include autonomous Payables and Expense Agent updates for automated invoice matching and policy auditing, the native EDI Exchange preview within the E-Documents framework, Word add-in report styling themes for non-technical branding, enhanced subcontracting operations in manufacturing, Shopify Plus B2B multi-location support, and the Page Scripting tool reaching General Availability (GA).
How does Page Scripting reaching General Availability (GA) improve regression testing?
With Page Scripting reaching GA in the Business Central Web Client, IT leads and business analysts can record end-to-end user workflows, parameterize input datasets, and replay test scripts directly in preview sandboxes. This provides automated, codeless user acceptance testing (UAT) across critical posting routines without requiring pro-code developer toolchains.
How should enterprise IT teams govern the BC29 major release update?
Enterprise organizations should follow a disciplined 4-step governance framework: 1) Spin up a cloned preview sandbox running the BC29 build; 2) Execute automated regression tests across all custom Per-Tenant Extensions (PTEs) using Page Scripting GA and AL-Go; 3) Audit active web service endpoints to eliminate deprecated SOAP UI page calls; and 4) Execute an off-hours production cutover following month-end close with full trial balance sign-off.
8. Related Modernization & Support Resources
For detailed architectural blueprints and enterprise upgrade services, explore our resource center:
- Dynamics 365 Business Central Implementation Services USA
- Dynamics 365 Business Central SLA Managed Support (15-Min P1 Response)
- Business Central AL Customization & API Integration Services
- Dynamics NAV vs. Business Central: 2026 Architectural Comparison & Upgrade Guide
- Claude and Business Central Model Context Protocol (MCP) Architecture
- Business Central Customization Best Practices: Upgrade-Safe AL Guide
