Microsoft to Retire Legacy Ad Integration by Early 2027
Publishers must migrate to the new Microsoft Prebid Adapter to maintain ad bid requests on the company's exchange.
Updated on Oct. 25, 2026 in Advertising
Live Poll
Do you trust that major advertising platforms prioritize the needs of publishers when updating their technical requirements?
Microsoft is retiring its legacy AppNexus ad connection, requiring publishers to migrate to the Microsoft Prebid Adapter by early 2027. This shift mandates technical updates to bidder keys and placement identifiers to ensure continued ad revenue flow.
Why it matters
The change forces publishers to overhaul their programmatic integration, as the legacy AppNexus endpoint will cease to function. Failing to migrate will result in broken bid requests, directly impacting the ability to monetize digital inventory.
Publishers must adopt Prebid.js version 11.36.0 to maintain consent compatibility, transitioning away from the retired AppNexus connection. This migration involves updating all existing ad-server rules to recognize new msft bidder keys.
The players
Microsoft
A technology conglomerate that provides software, cloud computing, and a global advertising exchange for programmatic media buying.
The details
Operators must swap the legacy AppNexus adapter for the Microsoft Prebid Adapter to maintain connectivity with the Microsoft exchange. The transition requires developers to update the placement identifier from placementId to placement_id and transition all bidder keys from AppNexus to msft. Additionally, publishers must ensure their native-ad setup conforms to Microsoft’s standardized requirements to clear ad auctions.
Timeline
October 21, 2026: Microsoft released the Monetize update.
Early 2027: The AppNexus adapter will officially shut down.
Market Landscape
This transition follows the standard consolidation lifecycle of the Prebid.js open-source framework. Major exchange providers are increasingly deprecating legacy third-party adapters in favor of unified, proprietary connectors.
Teams must prioritize the update of bidder keys and placement_id fields in their ad-server rules immediately to avoid a sudden loss of bid demand. Operators should ensure their ad-tech stack is updated to Prebid.js version 11.36.0 to maintain consent compliance.
The takeaway
The move to the Microsoft adapter standardizes auction participation but creates a significant maintenance requirement for ad operations teams. Verify that all your active placements have been converted to the msft key structure well before the 2027 deadline to prevent inventory under-performance.
What happens next
Publishers should audit their existing ad-server configurations for AppNexus dependencies before the early 2027 shutdown date.
Further reading
For broader trends in digital revenue, see our latest coverage on Advertising.
Source note: This article includes information reported by Search Engine Watch.
Live Poll
Do you trust that major advertising platforms prioritize the needs of publishers when updating their technical requirements?
