API
Microsoft
Microsoft retires the Azure Maps Render v1 REST API — after 17 September 2026 calls to the Render v1 endpoints stop working and must move to Render v2
left 17 Sept 2026
Quick answers
- Is it true that Azure Maps Render v1 API is retired on 17 September 2026?
- Yes. Microsoft has officially announced it, effective 17 Sept 2026. Microsoft's Azure Maps Render v1 REST API is deprecated and retires on 17 September 2026.
- When does it take effect?
- 17 Sept 2026. Verified against the vendor's own announcement.
- What should I use instead?
- Move Render v1 calls to the Azure Maps Render v2 API before 17 September 2026.
What this means for you
Microsoft's Azure Maps Render v1 REST API is deprecated and retires on 17 September 2026. Its own documentation states the Render v1 service "is now deprecated and will be retired on 9/17/26" and that all calls to the Render v1 API must be updated to the latest version by that date to avoid service disruptions. This is the API behind server-side map images and tiles — map image, static image, map tile, and imagery calls under the `rest-maps-1.0` API version. After the retirement date, applications still calling Render v1 endpoints lose their map imagery: static maps in reports and emails, cached tile pipelines, and any backend that renders a map server-side will break rather than degrade. A related change lands two days earlier — Microsoft automatically upgrades any remaining Azure Maps Gen1 (S0/S1) accounts to Gen2 on 15 September 2026 — so teams on older Azure Maps accounts are dealing with both a pricing-tier migration and an API retirement in the same week.
Where to go
Move Render v1 calls to the Azure Maps Render v2 API before 17 September 2026. In practice that means updating the API version from `1.0` to the current Render v2 version and adjusting request and response handling to the v2 shapes for the endpoints you use (map image / static image, map tile, imagery). Microsoft positions Render v2 as offering improved data quality and performance. Inventory every place your code or scripts call `atlas.microsoft.com` Render endpoints with the v1 API version, test the v2 responses against what your app expects (image formats, tile addressing, and parameters differ in places), and cut over before the date. Separately, confirm whether your Azure Maps account is Gen1 — if so, plan for the automatic Gen2 upgrade on 15 September 2026 and review the Gen2 pricing model.
- Azure Maps Render v2 API — the direct replacement, with improved data quality and performance per Microsoft
Microsoft is retiring the Azure Maps Render v1 REST API on 17 September 2026. The official Render v1 REST reference now carries a retirement banner: the Render v1 service “is now deprecated and will be retired on 9/17/26,” and all calls to the Render v1 API must be updated to the latest version by that date “to avoid service disruptions.”
This is the API that turns Azure Maps data into images on the server — the map image, static image, map tile, and imagery calls served under the rest-maps-1.0 API version. It is the machinery behind a static map dropped into a PDF report or an email, a backend tile cache, or any service that renders a map without a browser. After 17 September 2026, code still calling the v1 endpoints does not degrade gracefully; the map imagery simply stops coming back.
There is a second date to watch in the same week. Microsoft is automatically upgrading any remaining Azure Maps Gen1 (S0/S1) accounts to Gen2 on 15 September 2026 — two days before the Render v1 retirement. Teams still on an older Azure Maps account are therefore handling a pricing-tier migration and an API retirement almost simultaneously.
The fix is to move to the Azure Maps Render v2 API, which Microsoft positions as the successor with better data quality and performance. Find every place your application or scripts call atlas.microsoft.com Render endpoints on the v1 API version, switch the version and adapt to the v2 request and response shapes for the endpoints you use — image formats, tile addressing, and some parameters differ — and test before cutting over. If your Azure Maps account is Gen1, plan separately for the automatic Gen2 upgrade on 15 September and review the Gen2 pricing model so the bill doesn’t surprise you.
Entry changelog
- — last reviewed.
- — Entry created from Microsoft's official Azure Maps Render v1 REST API reference, which carries the retirement banner: the Render v1 service is deprecated and retires 17 September 2026, with calls to be moved to Render v2 by that date. Surfaced via Layer-2 discovery (Azure September end-of-life roundup) and verified directly against the learn.microsoft.com primary source. detect left empty: the Render v1 REST paths and the `api-version=1.0` marker overlap with v2 and unrelated Azure APIs, so no fingerprint is specific enough to avoid false alarms (SOURCING §5).
Put this countdown in your README
Building on Microsoft? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/azure-maps-render-v1-api-retirement)Spot an error or a changed date? Tell us and it’s corrected the same night.