Microsoft warns publishers using the old AppNexus ad connection to replace it before an early-2027 shutdown. The company says the adapter will be removed from Prebid.js and its legacy endpoint retired, ending that route for requesting advertising bids.
The warning appears in Microsoft’s October 21 Monetize update. Publishers are directed to the Microsoft Prebid Adapter, which connects their available ad placements to Microsoft’s advertising exchange. The notice does not give an exact shutdown day.
The replacement changes the information your site sends
Prebid is software publishers use to request bids for their ad space. An adapter supplies the connection to a particular advertising system, so replacing it can affect both the request from the page and how the resulting bid reaches the ad server.
The Microsoft adapter documentation lists concrete changes for existing integrations. The placement identifier moves from placementId to placement_id and accepts an integer; several other fields move into standardized request settings.
Publishers whose ad-server rules still look for AppNexus-specific bidder keys also need to revise those rules for msft. Otherwise, replacing the website’s adapter can leave the ad server expecting the old bidder’s labels.
Check the bid path through to the ad server
That gives the migration two separate checkpoints: whether Microsoft receives a valid request, and whether a returned bid matches the publisher’s ad-server setup. Seeing the new adapter loaded on a page answers neither question on its own.
Native ads add another dependency. Prebid says the Microsoft adapter requires its standardized native-ad setup and will not process requests using the legacy structure. Teams using that format need to include their native inventory in migration testing, rather than checking only standard display placements.
Prebid also warns that Microsoft’s auction-debug mode replaces the normal bid response, preventing an ad from appearing even when the diagnostic output shows a winning bid. Use that mode for diagnosis outside production, then verify delivery with it turned off.
The recommended version includes a consent fix
Microsoft specifically points publishers to Prebid.js 11.36.0 for consent support, warning of possible effects on buyer spending, particularly Google’s Display & Video 360. The release notes list a Microsoft-adapter fix for passing additional consent information.
The same Monetize announcement adds Copilot deal troubleshooting and charts for reporting results. Those tools may help investigate delivery problems, but the adapter replacement remains an implementation task for the publisher’s advertising stack.
Source: Microsoft Advertising
Start the conversation by posting the first comment