Dynamics 365 Business Central 2025 Wave 1 release: the state of SOAP deprecation.
Starting with Business Central 2025 Wave 1 (version 26), exposing Microsoft UI pages as SOAP endpoints is off by default. It can be turned back on with a Feature Management key, and it will be removed for good in version 29. Custom pages exposed as SOAP still work but should move to OData. Exposing Microsoft UI pages as OData now gives warnings and stops being possible in version 30, so custom OData pages should move to APIs.
post Stefano Demiliani
"With version 26, the possibility to expose a Microsoft page as SOAP endpoint will be disabled by default."
Key points
- SOAP exposure for Microsoft UI pages is disabled by default in version 26, with permanent removal planned for version 29
- Custom UI pages using SOAP will continue working but should migrate to OData endpoints
- New RT0053 telemetry signal available in version 26 to identify tenants using deprecated SOAP endpoints
- Microsoft UI pages exposed as OData endpoints will receive warnings starting version 26 and be disabled in version 30
- Custom OData endpoints for UI pages continue working in version 26 but should migrate to API endpoints
Quotes
- “With version 26, the possibility to expose a Microsoft page as SOAP endpoint will be disabled by default.” (Clarifies that the deprecation is implemented as a default change that customers can temporarily override)
- “Please remember that in Dynamics 365 Business Central version 29 the possibility to expose a Microsoft page as SOAP endpoint will be removed forever.” (Sets a hard deadline for SOAP migration, giving customers a defined window for action)
Context
- Features: SOAP web services on Microsoft UI pages, OData endpoints for Microsoft UI pages, RT0053 telemetry signal, Feature Management control, API endpoints
- Versions: 26, 29, 30
Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.