Timeline for Azure Maps Deprecated Functionality Replacement and Beta Status.

Question

The Azure Maps Service Module is deprecated and slated for retirement 2026/09/30.

We need to migrate to Azure Maps JavaScript REST SDK to avoid disruptions.

As it stands, all the functionality was not yet available in the SDK, and all the SDK components are - at best - still labeled as beta.

Some of our installs are on-premises and we cannot force updates, so we need to decide pretty soon whether we go with a Beta version assuming the functionality is available today, or risk losing support of certain functions.

---

When can we expect to have a replacement for these deprecated functions?

Or when can we expect @azure-rest/maps-geolocation, @azure-rest/maps-route and @azure-rest/maps-search to exit beta?

Answer 1

If you are using a subscription key, call the Azure Maps REST API's directly for the few queries you need. The main benefit of the client libraries is support for more advanced auth methods like Microsoft Entra (Active directory). The responses from the latest Azure Maps REST API's are in GeoJSON format which is the native format that the Azure Maps Web SDK supports. The main purpose of the older search module was to convert the response from the older services into an easy format for the map to understand, but this is no longer required. Here is a really simple example:

var AZURE_MAPS_KEY = 'Your Azure Maps Key';

async function geocode(query){
	var r = await fetch(`https://atlas.microsoft.com/geocode?api-version=2025-01-01&query=${query}&subscription-key=${AZURE_MAPS_KEY}`);
	return r.json();
}

Running this code in the browser console as a test (with a real key) using the following code returns a GeoJSON Feature collection of results. In the Web SDK, you can add this directly into a data source and display the results on the map if you wanted.

geocode('New York').then(r => console.log(r))

Answer 2

Hi ,

Thanks for reaching out to Microsoft Q&A.

Considering your on-prem installations and the inability to force updates, it's crucial to plan your migration carefully. Relying on beta versions in production environments carries inherent risks, including potential API changes and limited support.

Current Status of Azure Maps REST SDKs

The following Azure Maps REST SDK packages are currently in beta:

• @azure-rest/maps-geolocation: Latest version is 1.0.0-beta.5, published recently
• @azure-rest/maps-route: Also at version 1.0.0-beta.5, with the latest release about a month ago
• @azure-rest/maps-search: Remains in beta, with no specific release date for a stable version provided

Recommendations:

Engage with Microsoft Support: Reach out to your Microsoft account representative or support channels to inquire about the roadmap for these SDKs and express the importance of stable releases for your use case.

Assess Beta SDK Stability: Conduct thorough testing of the beta SDKs in a controlled environment to evaluate their stability and compatibility with your existing systems.

Implement Version Control: If you decide to proceed with beta versions, ensure you have robust version control and deployment strategies to manage potential updates or changes.

Monitor SDK Updates: Keep a close eye on the SDK repositories and release notes for any updates or announcements regarding stable releases.

By proactively engaging with Microsoft and evaluating the beta SDKs, you can make an informed decision that can can balance the need for timely migration with the stability requirements of your on-prem installations.

Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.