Request access to Azure Maps RouteRangeHD preview (high-definition isochrones)

Question

Request access to Azure Maps RouteRangeHD preview (high-definition isochrones)

Eliot MacDonald 25

Hello,

I would like to request access to the RouteRangeHD preview feature in Azure Maps, which was previously offered as a public preview (documentation: https://learn.microsoft.com/en-us/azure/azure-maps/how-to-use-route-range#access-high-definition-isochrones-ranges).

I'm developing Web applications that depend on high-resolution isochrone boundaries being shown on maps similar to the previous Bing Maps Isochrones API. The standard Route Range output is far too coarse for our requirements.

We have already set up our Azure Maps account (subscription id d123273e-eb35-4db4-9fa9-d6b45a9d092f) and have a Bing Maps account (ID 2006426) to use the previous Bing Maps Isochrone API and we have a paid developer support plan now. Specifically, we'd like to change our API requests from https://atlas.microsoft.com/route/range/json?api-version=1.0 (running successfully now) to https://atlas.microsoft.com/route/range/json?api-version=2024-07-01-preview and be able to set parameter isSimplifiedPolygon to true or false. Trying to do so now returns an "unauthorized" error message since it requires this access to be granted.

For reference:

Azure Maps resource name: mvmapsresource

Subscription ID: (d123273e-eb35-4db4-9fa9-d6b45a9d092f)

Please advise how we can gain access to this preview feature as soon as possible or if an updated preview or production alternative is now available.

Thank you!

Faraz Siddiqui 420 Reputation points Microsoft Employee

2025-07-23T21:30:09.39+00:00

The preview remains available and will continue to be until detailed polygon reaches GA. Could you please share the complete Route Range request with body and response?
Eliot MacDonald 25 Reputation points

2025-07-24T13:00:47.31+00:00
Thanks so much for following up. Desperately trying to get this in place. Here's the url we're trying to use (one specific example):

https://atlas.microsoft.com/route/range/jsonapi-version=2024-07-01-preview&query=40.67520040263743,-111.88699784130823&travelMode=car&timeUnit=minute&timeBudgetInSec=300&traffic=true&isSimplifiedPolygon=false&departAt=2025-07-25T21%3A00%3A00.000Z&subscription-key={myKey}

It returns the following:

{

"error": {

"code": "Unauthorized", "message": "Bearer realm=\"https://atlas.microsoft.com/\", SharedKey realm=\"https://atlas.microsoft.com/\"", "target": "WWW-Authenticate", "details": []

}

}

And here's a url that works right now , but only offers VERY simplified polygons that the app's users are rejecting and sending complaints about to me:

https://atlas.microsoft.com/route/range/json?api-version=1.0&query=40.63337595328692,-111.88758057757259&travelMode=car&timeUnit=minute&timeBudgetInSec=300&traffic=true&departAt=2025-07-25T21%3A00%3A00.000Z&subscription-key={myKey}

Please let me know what we can do. Trying to get this resolved as soon as I can while they wait for an update from me.

Thanks again!
Eliot MacDonald 25 Reputation points

2025-07-24T13:19:03.57+00:00

FYI, the previous Bing Maps version had a url like the following:

https://dev.virtualearth.net/REST/v1/Routes/Isochrones?waypoint=40.61953024766538, -111.8942731639112&maxTime=5&timeUnit=minute&optimize=timeWithTraffic&dateTime=07/25/2025 17:00:00&travelMode=driving&key={myBingMapsKey}

It returned a very good, detailed polygon each time but when inquiring about continuing to use it we were just given the option to pay a very large annual fee through a third party (> $5k) that includes 600,000 uses/transactions of this API. We only use a few hundred per month and previously at no cost. If there's anything else we can do through Microsoft to continue to use the Bing Maps API until it's gone at a reasonable cost, that would be a good solution too
Eliot MacDonald 25 Reputation points

2025-07-25T13:11:55.7966667+00:00

Oh! I didn't realize that https://atlas.microsoft.com/route/range/json could not be used the same way for the preview. We had been given feedback from others that it was an issue with our key/account not being given access the preview. We've gone ahead and reprogrammed it to use the POST requests structured as suggested...AND IT NOW WORKS!!! Thank you so much again for your help! It's very much appreciated! Have a great weekend!
IoTGirl 3,716 Reputation points Microsoft Employee Moderator

2025-07-29T23:43:00.28+00:00

@Eliot MacDonald Thank you for confirming that Faraz's answer worked for you! Could you please mark it as accepted so that others that have the same issue can confirm what you found worked?

Accepted answer

1 additional answer

Your answer

Faraz Siddiqui 420 Reputation points Microsoft Employee

2025-07-23T21:30:09.39+00:00

The preview remains available and will continue to be until detailed polygon reaches GA. Could you please share the complete Route Range request with body and response?
Eliot MacDonald 25 Reputation points

2025-07-24T13:00:47.31+00:00

Thanks so much for following up. Desperately trying to get this in place. Here's the url we're trying to use (one specific example):

https://atlas.microsoft.com/route/range/jsonapi-version=2024-07-01-preview&query=40.67520040263743,-111.88699784130823&travelMode=car&timeUnit=minute&timeBudgetInSec=300&traffic=true&isSimplifiedPolygon=false&departAt=2025-07-25T21%3A00%3A00.000Z&subscription-key={myKey}

It returns the following:

{

"error": {

"code": "Unauthorized", "message": "Bearer realm=\"https://atlas.microsoft.com/\", SharedKey realm=\"https://atlas.microsoft.com/\"", "target": "WWW-Authenticate", "details": []

}

}

And here's a url that works right now , but only offers VERY simplified polygons that the app's users are rejecting and sending complaints about to me:

https://atlas.microsoft.com/route/range/json?api-version=1.0&query=40.63337595328692,-111.88758057757259&travelMode=car&timeUnit=minute&timeBudgetInSec=300&traffic=true&departAt=2025-07-25T21%3A00%3A00.000Z&subscription-key={myKey}

Please let me know what we can do. Trying to get this resolved as soon as I can while they wait for an update from me.

Thanks again!
Eliot MacDonald 25 Reputation points

2025-07-24T13:19:03.57+00:00

FYI, the previous Bing Maps version had a url like the following:

https://dev.virtualearth.net/REST/v1/Routes/Isochrones?waypoint=40.61953024766538, -111.8942731639112&maxTime=5&timeUnit=minute&optimize=timeWithTraffic&dateTime=07/25/2025 17:00:00&travelMode=driving&key={myBingMapsKey}

It returned a very good, detailed polygon each time but when inquiring about continuing to use it we were just given the option to pay a very large annual fee through a third party (> $5k) that includes 600,000 uses/transactions of this API. We only use a few hundred per month and previously at no cost. If there's anything else we can do through Microsoft to continue to use the Bing Maps API until it's gone at a reasonable cost, that would be a good solution too
Eliot MacDonald 25 Reputation points

2025-07-25T13:11:55.7966667+00:00

Oh! I didn't realize that https://atlas.microsoft.com/route/range/json could not be used the same way for the preview. We had been given feedback from others that it was an issue with our key/account not being given access the preview. We've gone ahead and reprogrammed it to use the POST requests structured as suggested...AND IT NOW WORKS!!! Thank you so much again for your help! It's very much appreciated! Have a great weekend!
IoTGirl 3,716 Reputation points Microsoft Employee Moderator

2025-07-29T23:43:00.28+00:00

@Eliot MacDonald Thank you for confirming that Faraz's answer worked for you! Could you please mark it as accepted so that others that have the same issue can confirm what you found worked?

Answer 1

@Eliot MacDonald Route Range version 2024-07-01-preview and all other latest Route APIs uses POST requests and input params should be included in the request body. Please note the params names are different from the previous API version 1.0. Please refer to the API doc for complete spec.

You Azure Maps account does need any additional resources to access the preview. If you are authenticating using subscription key, please include it in the request header. For example:

Header
Key: subscription-key
Value: <<YourKey>>

Endpoint
POST https://atlas.microsoft.com/route/range?api-version=2024-07-01-preview

{
  "type": "Feature",
  "geometry": {
     "type": "Point",
     "coordinates": [
       -111.88699784130823,
       40.67520040263743
     ]
  },
  "properties": {
    "departAt":"2025-07-25T21:00:00.000Z",
    "timebudgetinsec": 300,
    "isSimplifiedPolygon":false,
    "travelMode":"driving",
    "optimizeRoute":"fastestWithTraffic"
  }
}

Answer 2

rbrundritt 21,191 Microsoft Employee Moderator

Not sure a preview is available any longer, I'll ask the Azure Maps Product Group team.

There was this thread recently that says that there are plans to have this generally available to all by the end of this year: https://learn.microsoft.com/en-us/answers/questions/2276495/isochrones-support-in-azure-maps

Eliot MacDonald 25 Reputation points

2025-07-24T12:17:53.94+00:00

Thank you! Please let me know when you can. Many users of my Web app waiting to see the "non-simplified" drive time zones (isochrones) made available in the preview and I don't think they would go from having it in the preview to no access for anyone. I think it just needs to be authorized by request now (like what I'm doing now)

Share via

Request access to Azure Maps RouteRangeHD preview (high-definition isochrones)

1 additional answer

Your answer