Skip to main content
Partner Stories

Business Central 2026 Release Wave 2: The SOAP Retirement Deadline Every CIO Should Know About

Microsoft will remove support for publishing Microsoft UI pages as SOAP web services in Dynamics 365 Business Central version 29, arriving with 2026 release wave 2 in October. If your finance system talks to a bank portal, an EDI hub, a legacy warehouse scanner, or a homegrown reporting tool through a SOAP endpoint built on a standard Business Central page, that connection stops working the day you upgrade to version 29. This is not a minor patch note buried in a changelog. It is a hard cutoff with a fixed date, and most organizations will not discover the problem until an integration silently fails during month-end close.

This piece breaks down exactly what changes, what does not, why the distinction matters more than most partner commentary suggests, and what a business leader should ask their IT team or their Microsoft partner before October 2026. It also places the change in context: Microsoft is retiring an old integration method at the same time it is expanding AI agents and automated order processing, which tells you where the platform is heading and what "doing nothing" actually costs.

Microsoft's Ten-Year Push Toward Modern APIs

SOAP web services have existed in the NAV and Business Central platform since Microsoft Dynamics NAV 2009. For over fifteen years, they were a default way for partners and internal developers to expose pages and codeunits to external systems: bank reconciliation tools, EDI providers, custom .NET applications, and reporting layers all grew up around SOAP endpoints because, for a long time, there was no better option.

That changed with the introduction of OData and, later, REST API web services built on OData v4. Microsoft has stated plainly in its own developer documentation that "SOAP is replaced by OData V4" and that organizations should migrate their integrations "as soon as possible." Access keys (Basic Auth) for web service authentication were deprecated back in October 2022, pushing everyone toward OAuth2. The SOAP retirement scheduled for version 29 is the next domino, not a surprise policy reversal.

What makes this moment different is specificity. Microsoft has now attached a version number and a release wave to the change. Starting in Business Central 2025 release wave 1 (version 26), Microsoft UI pages could no longer be published as SOAP web services by default, though a feature key let organizations re-enable the capability temporarily while they migrated. That feature key itself gets removed in version 29, meaning the transition window closes for good in October 2026.

A Deadline Hiding Inside a Feature List

Most Business Central customers experience release waves as a list of new capabilities: better Copilot skills, tighter Shopify integration, improved reporting. Deprecations get a line item, if that. Finance directors and operations leaders rarely read developer documentation, and IT teams that inherited a Business Central environment from a previous partner or a departed employee often do not have a complete map of every integration touching the system.

That combination, an easy-to-miss deprecation notice plus incomplete integration documentation, is exactly how outages happen. A SOAP-based connection to a shipping carrier, a payroll bureau, or a custom Power BI dataset can run quietly for years without anyone touching the code. Nobody remembers it exists until it stops working, usually at the worst possible time: during a period close, a peak shipping week, or a customer-facing order cutoff.

The financial exposure is not abstract. A broken EDI connection with a retail customer can trigger chargebacks. A failed bank reconciliation feed can delay a treasury close by days. A dead reporting integration can leave a board without the numbers it needs for a quarterly review. None of this requires a data breach or a catastrophic bug, only a missed deprecation notice and an upgrade that proceeds on schedule.

Why So Many Integrations Still Run on SOAP

Three patterns explain why SOAP dependency persists even now.

First, SOAP page-based web services were, for years, the path of least resistance. Publishing a page as a SOAP endpoint required almost no custom development. A generation of partner-built integrations took this shortcut because it worked and shipped faster than building a proper API layer.

Second, ownership gaps. Many mid-market companies have changed implementation partners at least once, and integration inventories rarely transfer cleanly between vendors. A new partner inherits a working system and has little incentive to audit legacy connections that are not causing visible problems.

Third, telemetry blindness. Business Central logs every web service call, including the endpoint type, to partner telemetry, but almost no organization actively monitors that telemetry unless a partner has specifically configured alerting on it. The data needed to answer "does this affect us" already exists inside most environments. It is simply never queried.

What Actually Changes in Version 29, and What Does Not

This is the section where most coverage of the SOAP retirement gets sloppy, and where the practical difference between "your integrations break" and "your integrations are fine" actually lives.

What is confirmed

Support for publishing Microsoft's own, out-of-the-box UI pages as SOAP web services is deprecated and will be removed entirely in Business Central version 29. The "Disable SOAP web services on Microsoft UI pages" feature key, which currently lets organizations re-enable SOAP for standard pages while they migrate, is itself removed in that same version. After version 29 ships, there is no toggle left to bring the old behavior back. Microsoft's recommended replacement paths are the built-in REST API web services, OData v4, or replicating the page as a per-tenant extension object and publishing that extension page as a SOAP endpoint instead.

What is not confirmed yet

Here is the nuance that gets flattened in most partner blog posts: this specific, dated removal applies to Microsoft's standard UI pages. Codeunit-based SOAP web services and SOAP endpoints built on custom, per-tenant extension pages are a separate category. Microsoft's own web services comparison documentation states that full SOAP support "will be removed in a later release" without naming that release or a date. In other words, version 29 closes one specific door with a hard deadline. It does not yet announce a hard deadline for every SOAP scenario, and treating the two as identical will either cause unnecessary panic about connections that still work, or false confidence about connections that will not.

The practical takeaway: an integration audit for version 29 needs to identify, specifically, which SOAP endpoints are built on standard Microsoft pages versus codeunits versus per-tenant extensions, because only the first category has a confirmed expiration date attached to it right now.

The AI agent expansion running in parallel

While Microsoft retires a fifteen-year-old integration method, it is simultaneously accelerating investment in autonomous AI agents. The 2026 release wave 1 overview describes a Payables Agent that automates accounts payable end to end, reading invoices, matching vendors and accounts, and preparing documents for approval with human oversight, alongside expanded Copilot skills covering guidance, comparison, analysis, and summarization, all included at no extra cost with a standard Business Central license. Reporting from industry coverage points to further B2B order automation across email, Microsoft Teams, Shopify, and EDI channels arriving as the platform matures through 2026 and into 2027.

Read those two facts together and the direction is unmistakable. Microsoft is not simply cleaning up old code. It is retiring the manual, developer-heavy integration model at the same time it builds native, AI-driven automation into the same workflows those old integrations used to serve manually. Organizations that ignore the SOAP deadline are not just risking a broken connection. They are falling two steps behind: still running legacy plumbing while competitors move onto agent-driven processes that need modern APIs to function at all.

Real-World Implementation Lessons

Engagements involving legacy web service migrations tend to surface the same three lessons regardless of company size or industry.

The audit always takes longer than the fix. Identifying every SOAP dependency, including ones built by long-departed consultants or embedded inside a third-party add-on, typically consumes more project time than rewriting the actual integration once it is found. Budget and schedule accordingly rather than assuming the technical rebuild is the bottleneck.

Telemetry beats guesswork every time. Rather than interviewing every department about what "might" still use an old integration, pulling incoming web service request telemetry and filtering by SOAP endpoint calls gives a definitive, evidence-based list of what is actually running in production right now. This single step usually cuts audit time by more than half.

Replacement is also an opportunity to consolidate. Many companies discover during a SOAP migration that they have three or four overlapping integrations doing similar jobs, built by different vendors at different times. Moving to REST API or OData is a natural checkpoint to retire redundant connections rather than simply porting every old endpoint one for one.

Common Pitfalls

Treating this as a pure IT ticket instead of a cross-functional risk item is the most common mistake. Finance, supply chain, and customer service teams all depend on integrations that IT may not fully understand from a business-process perspective, so leaving this exclusively to the development team increases the odds of missing a business-critical connection.

Waiting for the version 29 upgrade itself to surface the problem is the second common mistake. By the time the upgrade runs, the outage has already started. The audit needs to happen well before the upgrade window, not during it.

A third pitfall is assuming a general "we use REST APIs now" statement from a partner or an ISV vendor means every connection is covered. Point solutions, older Insight Works or Continia configurations, and homegrown Power Automate flows can still route through SOAP behind the scenes even when the primary vendor relationship has moved on. Verify at the endpoint level, not the vendor level.

Strategic Recommendations

Immediate (next 30 days)

Pull incoming web service telemetry and identify every call currently hitting a SOAP endpoint, tagged by page or codeunit. This is a data-gathering exercise, not a development task, and it should be treated as high priority regardless of your current release wave.

Before October 2026

For every SOAP endpoint confirmed to be built on a standard Microsoft UI page, plan a migration to the built-in REST API web services or OData v4, prioritizing anything tied to revenue-generating processes such as EDI order intake, bank feeds, or customer-facing shipment data. Where a genuine business reason exists to keep a page-based integration on SOAP past version 29, replicate that page as a per-tenant extension object rather than relying on Microsoft's standard page, since that path remains supported.

Beyond the deadline

Use the migration as the trigger to evaluate whether Business Central's expanding native automation, the Payables Agent, Copilot skills, and deeper Shopify and Teams integration, can now replace what used to require a custom SOAP-based workaround in the first place. In several cases, the old integration existed only because the native platform could not do the job. That may no longer be true.

Future Outlook

Expect Microsoft to continue tightening the API surface around Business Central release after release, not loosening it. The pattern across the last four release waves is consistent: expand AI agents and native automation, harden security defaults such as the 2022 access key deprecation, and retire legacy integration paths on a fixed schedule rather than an open-ended one. Organizations that build a habit of reviewing deprecation notices and web service telemetry with every release wave, rather than only when forced to, will avoid repeating this scramble when the next legacy feature reaches its own expiration date.

Key Takeaways

Business Central version 29, shipping with 2026 release wave 2 in October, permanently removes the ability to publish Microsoft's standard UI pages as SOAP web services, along with the feature key that currently allows a temporary opt-back-in. Codeunit-based and per-tenant extension SOAP endpoints are a separate category without a confirmed removal date yet, and conflating the two leads to either wasted panic or false confidence. Telemetry, not departmental memory, is the fastest and most accurate way to find every SOAP dependency in a live environment. Microsoft is retiring this legacy integration method at the same time it expands AI agents and native automation, which means the real cost of inaction is not just a broken connection, it is falling behind on the automation your competitors are already adopting.

Conclusion

A software deprecation rarely generates headlines, but a broken bank feed during a treasury close or a failed EDI connection during a peak order week absolutely will. The SOAP retirement in Business Central version 29 is entirely predictable, well-documented by Microsoft, and completely avoidable with a modest amount of proactive auditing. The organizations that treat this as a scheduling exercise now will spend a few hours pulling telemetry and planning a migration. The organizations that treat it as a surprise in October 2026 will spend considerably more time explaining an outage to customers, auditors, or their own board. If you want a second opinion on what your Business Central environment actually depends on before that deadline arrives, our team has run this exact audit for organizations preparing for Business Central integration changes across the UK, and we can walk through the same process for your API integration footprint in the US or your broader Business Central implementation in Canada.

Frequently Asked Questions

Does the SOAP retirement in Business Central version 29 affect every integration built on SOAP? 

No. It specifically removes the ability to publish Microsoft's standard, out-of-the-box UI pages as SOAP web services. SOAP endpoints built on codeunits or on custom per-tenant extension pages are a separate category, and Microsoft has not yet published a confirmed removal date for those.

When exactly does this change take effect? 

Business Central version 29 ships as part of 2026 release wave 2, which Microsoft has scheduled for October 2026, with continued rollout through the wave into early 2027.

What should we migrate our SOAP integrations to? 

Microsoft recommends REST API web services as the primary replacement, with OData v4 as a secondary option. If a genuine reason exists to keep a page-based SOAP integration, replicating the affected page as a per-tenant extension and publishing that extension as a SOAP endpoint remains a supported path.

How do we find out if we are affected without guessing? 

Business Central logs every web service call to partner telemetry, including the endpoint type. Reviewing incoming web service request telemetry for SOAP calls gives a definitive list of live dependencies, rather than relying on staff memory or vendor assurances.