Business Central 2026 Wave 2 (v29): the most important changes at a glance

Key takeaways

• SOAP web services for Microsoft standard pages are permanently removed in v29 — affected integrations must be migrated beforehand.
• The new Unified Copilot Chat combines Business Central data, web search and general knowledge in one interface.
• The MCP Server opens Business Central to external AI tools such as Claude Desktop or Copilot Studio.
• Table extensions now store fields in the base table instead of separate tables — this eliminates SQL joins and significantly improves performance.
• The Payables Agent can now match order lines with receipts and the Expense Agent automatically detects duplicate documents.

1. SOAP web services: the end of an era

Perhaps the most consequential change in v29 is not a new feature but a removal: Microsoft eliminates the ability to publish standard UI pages as SOAP endpoints. The feature key that previously allowed re-enabling this is also removed.

For companies with EDI connections, banking interfaces or BI reporting via SOAP this means: these integrations will stop working after the upgrade. The recommended migration path leads directly to native Business Central APIs — not OData, which will also be retired for Microsoft pages from v30 (2027).

Check via the RT0053 telemetry signal whether your environment is affected. Test in the v29 sandbox. And plan the development effort now, not after the update.

2. Unified Copilot Chat: one interface for everything

Copilot in Business Central gets a fundamentally redesigned interface modelled on the Microsoft 365 Copilot design. Instead of individual Copilot features distributed across different pages, there is now a central chat access via a new icon in the app bar.

What makes it special: the chat integrates not only Business Central data but also web search and general knowledge. A question like 'How has customer Mueller's revenue developed compared to last year and what market trends exist in their industry?' can now be answered by Copilot in a single response.

Users with an additional Microsoft Copilot licence gain access to extended features such as Work IQ — the ability to link BC data with information from SharePoint, Teams and Outlook.

3. MCP Server: opening Business Central for external AI

Business Central can now act as an MCP Server (Model Context Protocol) — an open standard through which external AI agents access ERP data in a structured way. Whether Claude Desktop, Copilot Studio or a custom chatbot: via MCP these tools can query customers, check inventory or create orders.

Setup is done via Feature Management in Business Central. You define which API pages are available as tools and what permissions the AI agent has. The BC permission model applies unchanged — there is no special pathway for AI access.

For companies wanting to connect their own AI applications to ERP data beyond the built-in Copilot features, the MCP Server is a turning point: no more custom connectors, no manual data exports.

4. Table extensions: performance leap through new data model

A technical change that makes a big difference in practice: fields from table extensions are now stored in the base table instead of separate database tables. This means: the SQL joins that were previously required for every query on extended tables are eliminated.

For companies with many installed extensions — which is the norm in the mid-market — this can deliver noticeable speed improvements, especially for reports, list pages and API queries. Additionally, developers can now create indexes combining fields from the base table and extensions.

For developers: development principles remain the same. Partial Records (SetLoadFields) should continue to be used consistently to load only the fields actually needed.

5. Payables Agent and Expense Agent: now smarter

The AI agents introduced in Wave 1 receive significant extensions in Wave 2. The Payables Agent can now match invoice lines with order lines — specifically by amounts and expected receipt dates. This significantly reduces manual review during invoice approval.

The Expense Agent now automatically detects duplicate documents, validates expense reports against stored policies and supports mileage claims with configurable rates. A relevant advancement for companies with high travel and expense volumes.

6. Peppol BIS 3 and Shopify B2B: sales and e-invoicing

For companies already working with e-invoicing requirements, v29 brings extended support for the Peppol BIS 3 standard for E-Documents. This simplifies electronic document exchange within the European Economic Area.

In e-commerce, the Shopify integration is extended with B2B features. Companies using Shopify as a B2B sales channel can now synchronise customer-specific prices and conditions directly from Business Central.

7. Manufacturing: production orders directly from the Planning Worksheet

Manufacturing companies benefit from a long-requested simplification: released production orders can now be created directly from the Planning Worksheet without the detour via planned orders. This is complemented by improved routing instructions for subcontracting and automatic quality inspection quantities.

For mid-sized manufacturing companies with subcontracting this is a noticeable process simplification — fewer clicks, fewer error sources, faster throughput.

What you should do now

First check whether SOAP integrations are active in your environment — this is the only change in v29 that can cause outages. Use the RT0053 telemetry signal or manual review via the Web Services page for this.

Create a v29 sandbox and test your extensions and integrations. Especially if you use many table extensions, a performance comparison with the new data model is worthwhile.

Plan the Copilot rollout strategically: the Unified Copilot Chat and MCP Server open new possibilities, but they require clean master data and a well-thought-out permission structure.

Frequently asked questions

When will Business Central 2026 Wave 2 be released?

General availability of version 29 is planned for the first week of October 2026. The public preview has been available in sandbox environments since September 2026.

Do I need to do anything after updating to v29?

If you use SOAP web services on Microsoft standard pages, you must migrate to Native APIs before the update — otherwise these integrations will stop working. All other changes are optional and can be introduced gradually.

Do I need an additional licence for the new Copilot Chat?

The basic Copilot Chat is included in the Business Central licence and uses Copilot credits. For extended features such as Work IQ — linking BC data with SharePoint, Teams and Outlook — an additional Microsoft Copilot licence is required.

Does the new table extension data model affect my existing extensions?

The switch happens automatically and transparently. Your existing extensions work without modification. However, you can benefit from improved performance — especially for reports and list pages with many extension fields.

Is Business Central 2026 Wave 2 available on-premises?

Platform updates (performance, AL improvements) are available on-premises as well. AI features — Copilot Chat, MCP Server, agent enhancements — require Business Central Online (cloud).