Evolving Bing Maps Enterprise into the Azure Maps Platform

Bing Maps for Enterprise had a decade of accumulated content, demos, and developer surface area. Moving it into Azure meant preserving every entry point for paying customers while adopting Azure's IA, design system, and motion language end-to-end.

Each capability — isochrones, truck routing, multi-itinerary optimization, mixed reality — got an in-browser demo with copy-paste code. AI-assisted prompts let developers ask, "show me a 15-min drive-time polygon around Seattle" and see the result live.

Bing Maps for Enterprise had 15+ years of accumulated SKUs, SDKs, sample code, and support contracts. Every URL was potentially load-bearing for someone's production system — fleet dispatchers, logistics platforms, government GIS tooling. The mandate: adopt Azure's identity, IA, and design language end-to-end while preserving every entry point, every code sample, and every billing relationship.

We treated the developer surface as a product in its own right: capability pages that read like case studies, in-browser sandboxes for every SDK method, and copy-paste snippets that stay in sync with the live API via a generated pipeline. AI-assisted prompts let devs describe intent in natural language ("15-minute drive-time polygon around Seattle") and get runnable code back. Every legacy route now redirects semantically — zero broken deep links at cutover.

Azure Maps now stands next to Cognitive Services, App Service, and the rest of the Azure PaaS family as a first-class developer surface. Time-to-first-successful-request dropped meaningfully in Microsoft's internal telemetry, sales enablement teams stopped having to translate between two brands, and the docs pattern we built for map demos was adopted by adjacent Azure teams as reference material.