Microsoft Advertising · Status at source date: Announcements
Microsoft keeps new Advertising API features in SOAP until January 2027
Microsoft will continue delivering new Advertising API features through SOAP and REST until SOAP’s unchanged deprecation date of 31 January 2027.
What changed
Migration plan changes, not the deadline
Microsoft has revised its Advertising API migration plan. New features will continue to ship through both SOAP and REST until SOAP is deprecated on 31 January 2027. The previous plan was to make new features REST-only from 1 October 2026. The feature-delivery change therefore relates to the period beginning on 1 October, while the stated SOAP deprecation date remains unchanged.
This gives integrations that still use SOAP more near-term access to new features, but it is not an extension of SOAP’s stated lifetime. A vendor or internal tool that depends on SOAP still needs a working REST replacement before 31 January rather than treating continued feature delivery as permission to postpone migration.
Use the additional overlap for validation
The useful planning distinction is between feature access and operational readiness. Continued delivery in SOAP may reduce an immediate parity concern, while the overlap gives teams time to validate REST authentication, request construction, reporting outputs and error handling against an established process. The announcement does not demonstrate feature-by-feature parity or guarantee identical workflow behaviour.
Classify each integration by migration risk. A reporting-only job with a manual fallback may tolerate a later cutover than a bid, budget or campaign-management process with no fallback. Assign validation dates accordingly, while keeping every date comfortably ahead of the stated deprecation.
A sensible acceptance test would run a controlled REST process alongside the corresponding SOAP process and reconcile important fields, totals, failures and downstream effects. Differences should be investigated rather than automatically attributed to the API change. That comparison provides a more useful go-live decision than merely confirming that a REST request returned successfully.
Why it matters for advertisers
The revision eases the immediate pressure created by the former 1 October REST-only plan, but it leaves the January 2027 cut-off intact. Migration governance, testing and vendor accountability are still required.
What to check next
- Inventory every internal and vendor integration that still sends SOAP requests.
- Set REST validation and cutover milestones comfortably ahead of 31 January 2027.
- Reconcile critical reporting and automation outputs during a controlled SOAP-to-REST comparison.
Sources & contributor credit
- Original sourceMicrosoft Learn
Source cited in the published Week 40 newsletter. Article observation/reporting date is shown separately; this page’s original publication date is not inferred.
- Newsletter coverage · Paid Media Collective Week 40
Published edition used for story selection, copy, source credits and media; curation is distinct from original authorship.
Original creator unverified
Contributor roles follow the published newsletter and its linked evidence. Reporting, official discussion and visual authorship are kept separate; no independently unverified first-reporting priority is awarded.
Attribution evidence and limitations
Published story and credit line reconciled with the expanded article.
Original post, primary documentation and secondary reporting links retained.
Visible image content inspected for story relevance; image credit retained separately from reporting credit.
Attribution checked . This is a review date, not the original publication date.
- Published on this site
- Article updated
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.
