Starting with Business Central version 30 (2027 Release Wave 1), Microsoft-authored pages, the ones inside the Base Application, System Application, and other first-party apps, can no longer be exposed as OData web service endpoints.
Only custom pages built by a developer will still support OData after that point. The real deadline pressure lands earlier than most companies realize: SOAP endpoints are already being phased out in version 26 and fully removed in version 29 (2026 Wave 2).
If your reporting tools, RPA flows, or third-party connectors touch Business Central through OData or SOAP today, this is a migration project, not a footnote in a release notes document.
Why OData Web Services on Microsoft Pages Are Being Retired
Business Central‘s UI pages were built to be looked at and clicked through by people, not queried by machines. Microsoft has used those same pages as a convenient backdoor into OData for years, which is exactly the problem. A page can change shape with any update, a field can move or get renamed, and an integration built against that page breaks without warning. That instability shows up as timeouts, inconsistent payloads, and reports that silently stop matching the ledger.
The fix Microsoft has chosen is a hard separation between UI and API. Business Central’s standard APIs (API pages and API queries) are versioned, documented, and built specifically for machine-to-machine access. Microsoft wants every integration standing on that foundation instead of a UI page that happens to expose data today.
Business Central OData and SOAP Retirement Timeline
Most coverage of this change leads with 2027, which makes it easy to assume there is time to spare. The rollout has been happening in stages, and two of them land well before the final cutoff.
- Version 26, 2025 Release Wave 1: Administrators start seeing warnings when a Microsoft UI page is exposed as an OData endpoint. SOAP endpoints are blocked by default through feature management.
- Version 29, 2026 Release Wave 2: SOAP endpoints are removed entirely. Anything still calling Business Central over SOAP stops working on this release, not in 2027.
- Version 30, 2027 Release Wave 1: OData support for Microsoft-authored pages is removed. Custom pages you build yourself can still be exposed as OData, but Microsoft’s own guidance points teams toward API pages and API queries going forward.
If your organization is only tracking the 2027 date, the SOAP removal in 2026 Wave 2 is the one likely to catch you off guard first.
Common OData Dependencies Organizations Miss
The OData conversation tends to focus on custom-built integrations, but in practice the exposure is wider than that.
Teams routinely find OData dependencies in places nobody flagged as an integration in the first place: Power BI reports built directly against a Microsoft page instead of a published API, Excel Add-in workbooks pulling live data through a web service, RPA or Power Automate flows that were stood up quickly and never revisited, and ISV or middleware connectors (payment processors, EDI tools, industry-specific add-ons) that were configured years ago and have not been touched since. None of these show up if you only ask your integration team what is connected to Business Central. You have to ask finance, ops, and whoever owns your BI stack too.
3 Steps to Replace Business Central OData Dependencies
An audit and migration for this kind of change holds up whether it is happening to your business or your client’s, and it comes down to three phases.
1. Audit what is connected.
Open the Web Services page in Business Central and review every entry. Microsoft-owned objects generally fall in the 1 to 49999 object ID range, which is a fast way to separate your own custom pages from Microsoft’s.
Cross-reference that list against telemetry for incoming OData and SOAP requests so you are not relying on institutional memory to know what is live.
2. Match each dependency to a replacement.
Business Central’s standard API library already covers most common scenarios, financials, sales, purchasing, inventory, and it is the right first stop because it is maintained and versioned by Microsoft.
Where a standard API does not cover what you need, the fallback is a custom API page built in AL, scoped to exactly the fields and logic your integration requires, which also means it will not shift under you the way a UI page can.
3. Cut over and validate before you retire the old path.
Reconfigure the integration or report against the new endpoint, run it in parallel with the old connection where possible, and confirm the output matches before you turn the legacy path off. Financial data and reporting are not places to find out something is off after the fact.
Why This Migration Matters Beyond Compliance
We would push back a little on treating this purely as a compliance deadline.
Gartner has projected that more than 70% of recently implemented ERP initiatives will fail to fully meet their original business goals, and fragile, undocumented integrations are a recurring reason why. A mandatory OData migration is a legitimate reason to get a real inventory of every system touching Business Central, not just patch the ones Microsoft is forcing you to fix.
Organizations that treat this as a full integration health check tend to walk away with fewer surprises at go-live for whatever comes next, not just a passing grade on this one deprecation.
Frequently asked questions
When does Business Central actually remove OData access to Microsoft pages?
Version 30, released as part of 2027 Release Wave 1. Custom pages you build yourself will still support OData after that release.
Does this affect Power BI and Excel reports built on Business Central?
Yes, if those reports connect through a Microsoft-owned page exposed as an OData service rather than through a published API. This is one of the most commonly missed dependencies because reporting is rarely classified as an integration.
What should I do first if I have not started planning for this?
Open the Web Services list in Business Central and check which entries are Microsoft-owned pages versus your own custom pages, then cross-check that against telemetry for OData and SOAP traffic. That gives you a real inventory instead of a guess.
Is SOAP being removed at the same time as OData?
No, SOAP is removed earlier, in version 29 (2026 Release Wave 2), a full release before the OData change in version 30.
