Migrate a Microsoft Advertising SOAP API integration to REST ahead of the October 2026 feature freeze
domain: learn.microsoft.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Note the timeline: starting with the April 2026 announcement, all new Microsoft Advertising API features/enhancements ship REST-only from October 1, 2026, and the SOAP API is fully deprecated January 31, 2027.
If using a Microsoft-provided SDK, follow the SDK migration documentation to switch the SDK's transport from SOAP to REST with minimal code changes.
If calling SOAP directly without an SDK, replace SOAP endpoint URLs and XML request/response handling with the equivalent REST URLs and JSON payloads documented per operation in the API reference.
Re-test authentication end to end, since REST and SOAP can differ in header/token placement even when using the same OAuth credentials.
For complex integrations needing more time, contact your Microsoft Advertising account team or support to discuss an extended migration plan before the October 2026 cutoff.
Known gotchas
Existing SOAP integrations keep running with no immediate impact during the transition window — but any new feature or enhancement released after October 1, 2026 is only accessible via REST.
The SOAP sunset date (January 31, 2027) is a hard deprecation, not a soft one — integrations not migrated by then stop working entirely.
REST migration is a genuine rewrite of request/response handling (JSON vs. XML, different auth header conventions), not just a URL swap — budget real engineering time, especially for non-SDK integrations.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?