Skip to content

Commit 3e463f0

Browse files
Merge pull request #276056 from stevemunk/BME-updates
Updates/fixes to the BME migration guides
2 parents f756a0e + 7201834 commit 3e463f0

12 files changed

+39
-40
lines changed

articles/azure-maps/migrate-bing-maps-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Covered in this article:
2626

2727
Azure Maps is a set of mapping and geospatial services that enable developers and organizations to build intelligent location-based experiences for applications across many different industries and use cases. Use Azure Maps to bring maps, geocoding, location search, routing, real-time traffic, geolocation, time zone info, weather, and custom indoor maps into your web, mobile and server-side solutions. Azure Maps is an Azure service, so it inherently includes many of the Azure security and compliance promises that are important to enterprise customers. Azure Maps includes many of the same features as Bing Maps for Enterprise, along with more functionality, like:
2828

29-
- Multiple service authentication method options. For more information on security and authentication in Azure Maps, See [Authentication with Microsoft Azure Maps].
29+
- Multiple service authentication method options. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps].
3030
- Data residency compliance support. For more information, see [Azure Maps service geographic scope].
3131
- Azure regulatory compliance standards (GDPR, ISO, FedRAMP, HIPAA, etc.). For more information, see [Microsoft Compliance].
3232
- Support for programmatically creating and managing Azure Maps accounts (resources). For more information, see [Create your Azure Maps account using an ARM template].
@@ -65,7 +65,7 @@ With Bing Maps for Enterprise, the [Bing Maps Account Center] is where you manag
6565

6666
### Security and authentication
6767

68-
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple authentication methods, such as a [Shared Key], [Microsoft Entra ID], or [Shared access signature token authentication]. For more information on security and authentication in Azure Maps, See [Authentication with Microsoft Azure Maps].
68+
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple authentication methods, such as a [Shared Key], [Microsoft Entra ID], or [Shared access signature token authentication]. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps].
6969

7070
## Licensing and billing considerations
7171

@@ -163,7 +163,7 @@ More Azure Maps resources:
163163

164164
Developers can get migration support through the [Azure Maps Q&A] or through one of the many [Azure support options].
165165

166-
[Authentication with Microsoft Azure Maps]: azure-maps-authentication.md
166+
[Authentication with Azure Maps]: azure-maps-authentication.md
167167
[Authentication best practices]: authentication-best-practices.md
168168
[Autosuggest]: /bingmaps/rest-services/autosuggest
169169
[Azure Licensing]: https://azure.microsoft.com/pricing/purchase-options/azure-account
@@ -225,7 +225,7 @@ Developers can get migration support through the [Azure Maps Q&A] or through one
225225
[Search: Fuzzy (typehead)]: /rest/api/maps/search/get-search-fuzzy
226226
[Search: Fuzzy Search (typeahead)]: /rest/api/maps/search/get-search-fuzzy
227227
[Search: Fuzzy]: /rest/api/maps/search/get-search-fuzzy
228-
[Search: POI]:  /rest/api/maps/search/get-search-poi
228+
[Search: POI]: /rest/api/maps/search/get-search-poi
229229
[Search: Polygon]: /rest/api/maps/search/get-polygon
230230
[Search: Reverse Geocoding Batch]: /rest/api/maps/search/get-reverse-geocoding-batch
231231
[Search: Reverse Geocoding]: /rest/api/maps/search/get-reverse-geocoding

articles/azure-maps/migrate-calculate-route.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Bing Maps for Enterprise only supports API key authentication. Azure Maps suppor
3737

3838
The following table lists the Bing Maps _Calculate a Route_ request parameters and the Azure Maps equivalent:
3939

40-
| Bing Maps Request Parameter | Bing Maps Request Parameter Alias  | Azure Maps Request Parameter | Required in Azure Maps  | Azure Maps Data Type  | Description|
40+
| Bing Maps request parameter | Bing Maps request parameter alias  | Azure Maps request parameter | Required in Azure Maps  | Azure Maps data type  | Description|
4141
|-----------------------------------|------------------------------------|------------------------------------|-------------------------|-----------------------|------------|
4242
| avoid  | | avoid  | False | string  | Here are the Bing Maps Calculate a Route API to Azure Maps Route Directions API avoid equivalents, where supported: <br><br>tolls: tollRoads<br>ferry: ferries<br>borderCrossings: borderCrossings<br>minimizeDrivingSideTurn: Not supported<br><br>minimizeAgainstDrivingSideTurn: Not supported<br>minimizeUTurn: Not supported<br>minimizeTolls: Not supported<br>highways: limitedAccessHighways<br>minimizeHighways: Not supported<br> |
4343
| dateTime  | dt  | departAt  | False | string  | Azure Maps Route Directions API also supports arriveAt parameter that is used to specify the desired date and time of arrival. It can't be used with departAt.|

articles/azure-maps/migrate-calculate-truck-route.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Bing Maps for Enterprise only supports API key authentication. Azure Maps suppor
3636

3737
The following table lists the Bing Maps _Calculate a Truck Route_ request parameters and the Azure Maps equivalent:
3838

39-
| Bing Maps Request Parameter | Bing Maps Request Parameter Alias  | Azure Maps Request Parameter | Required in Azure Maps  | Azure Maps Data Type  | Description|
39+
| Bing Maps request parameter | Bing Maps request parameter alias  | Azure Maps request parameter | Required in Azure Maps  | Azure Maps data type  | Description|
4040
|-----------------------------------|------------------------------------|------------------------------------|-------------------------|-----------------------|------------|
4141
| avoid  | | avoid  | False  | string  | Here are the Bing Maps to Azure Maps Route Directions API _avoid_ equivalents, where supported:<br><br>- tolls: tollRoads<br>- ferry: ferries<br>- borderCrossings: borderCrossings<br>- highways: limitedAccessHighways<br>- minimizeDrivingSideTurn: Not supported<br>- minimizeAgainstDrivingSideTurn: Not supported<br>- minimizeUTurn: Not supported <br>- minimizeTolls: Not supported<br>- minimizeHighways: Not supported  |
4242
| borderRestriction  | | Not supported  | Not supported  | Not supported  | In Azure Maps Route Directions API, _avoid=borderCrossings_ can be used to restrict routes from crossing country borders however specifying a region list for border restriction isn't supported.  |
@@ -579,6 +579,7 @@ Support
579579
[Microsoft Q&A Forum]: /answers/tags/209/azure-maps
580580
[Post Directions Batch]: /rest/api/maps/route/post-directions-batch
581581
[Route Directions]: /rest/api/maps/route/post-directions
582+
[RouteOutputOption]: /rest/api/maps/route/post-directions#routeoutputoption
582583
[Security section]: /rest/api/maps/route/get-route-range?#security
583584
[Shared Access Signature (SAS) Token]: azure-maps-authentication.md#shared-access-signature-token-authentication
584585
[subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account

articles/azure-maps/migrate-find-location-address.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -31,22 +31,21 @@ This article explains how to migrate the Bing Maps [Find a Location by Address]
3131

3232
## Security and authentication
3333

34-
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps].
34+
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps] and the [Security section] in the Azure Maps Get Geocoding documentation.
3535

3636
## Request parameters
3737

3838
The following table lists the Bing Maps _Find a Location by Address_ request parameters and the Azure Maps equivalent:
3939

40-
| Bing Maps Request Parameter | Bing Maps Request Parameter Alias  | Azure Maps Request Parameter | Required in Azure Maps  | Azure Maps Data Type  | Description|
40+
| Bing Maps request parameter | Bing Maps request parameter alias  | Azure Maps request parameter | Required in Azure Maps  | Azure Maps data type  | Description|
4141
|-----------------------------|------------------------------------|------------------------------|-------------------------|-----------------------|------------|
42-
| Bing Maps Request Parameter Name  | Bing Maps Request Parameter Alias  | Azure Maps Request Parameter Name  | Required in Azure Maps  | Azure Maps Data Type  | Note  |
42+
| Bing Maps request parameter | Bing Maps request parameter alias  | Azure Maps request parameter | Required in Azure Maps  | Azure Maps data type  | Note  |
4343
| addressLine  | | addressLine  | False  | string  | In Azure Maps Get Geocoding API, a street address, or street address with locality and `adminDistrict`, is supported input for `addressLine`|
4444
| adminDistrict  | | adminDistrict  | False  | string  | |
4545
| countryRegion  | | countryRegion  | False  | string  | |
4646
| locality  | | locality  | False  | string  | |
4747
| postalCode  | | postalCode  | False  | string  | |
4848
| culture  || Request Header:  Accept-Language   | False  | string  | As specified in the Azure Maps [request header], `culture` defines the language used in search results when using the Azure Maps Get Geocoding API. For more information, see [Supported Languages]. |
49-
| | | | | | |
5049
| include  | incl  | Not needed  | Not needed  | Not needed  | In Bing Maps Find a Location by Address API, the ‘include’ input parameter is required in order to get a two-letter ISO country code for the location result in the response (_include=ciso2_). In Azure Maps Get Geocoding API, the two-letter ISO country code is returned by default.  |
5150
| includeNeighborhood  | inclnb  | Not needed  | Not needed  | Not needed  | In Azure Maps Get Geocoding API, neighborhood info is returned in the response by default, when available.  |
5251
| maxResults  | maxRes  | top  | False  | Integer (int32)  | In Azure Maps Get Geocoding API, the default number of responses returned is 5. The minimum is 1 and the maximum is 20.  |
@@ -286,9 +285,10 @@ Support
286285
[Microsoft Q&A Forum]: /answers/tags/209/azure-maps
287286
[Migrate Bing Maps Find a Location by Query API]: migrate-find-location-query.md
288287
[request header]: /rest/api/maps/search/get-geocoding?#request-headers
288+
[Security section]: /rest/api/maps/search/get-geocoding#security
289289
[Shared Access Signature (SAS) Token]: azure-maps-authentication.md#shared-access-signature-token-authentication
290290
[subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
291291
[Supported Languages]: supported-languages.md
292292
[Supported Views]: supported-languages.md#azure-maps-supported-views
293293
[Understanding Azure Maps Transactions]: understanding-azure-maps-transactions.md
294-
[URI Parameters]: /rest/api/maps/search/get-geocoding#uri-parameters
294+
[URI Parameters]: /rest/api/maps/search/get-geocoding#uri-parameters

articles/azure-maps/migrate-find-location-by-point.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -30,23 +30,20 @@ This article explains how to migrate the Bing Maps [Find a Location by Point] AP
3030

3131
## Security and authentication
3232

33-
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps].
33+
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps] and the [Security section] in the Azure Maps Get Geocoding documentation.
3434

3535
## Request parameters
3636

3737
The following table lists the Bing Maps _Find a Location by Point_ request parameters and the Azure Maps equivalent:
3838

39-
| Bing Maps Request Parameter | Bing Maps Request Parameter Alias | Azure Maps Request Parameter | Required in Azure Maps | Azure Maps Data Type | Description |
39+
| Bing Maps request parameter | Bing Maps request parameter alias | Azure Maps request parameter | Required in Azure Maps | Azure Maps data type | Description |
4040
|-----------------------------|-----------------------------------|------------------------------|------------------------|----------------------|-------------|
4141
| culture | c | Request Header: Accept-Language | False | string | In Azure Maps Get Reverse Geocoding API, this is the language in which search results should be returned. This is specified in the Azure Maps [request header]. Please refer to [Supported Languages] for details. |
42-
| | | | | | |
4342
| include | incl | Not needed | Not needed | Not needed | In Bing Maps Find a Location by Point, the ‘include’ input parameter is required to get a two-letter ISO country code for the location result in the response. In Azure Maps Get Reverse Geocoding API, the two-letter ISO country code is returned by default. |
4443
| includeEntityTypes | | resultTypes | False | query | |
45-
| | | | | | |
4644
| includeNeighborhood | inclnb | Not needed | Not needed | Not needed | In Azure Maps Get Reverse Geocoding API, neighborhood info is returned in the response by default, when available. |
4745
| point | | coordinates | True | number[] | In Bing Maps Find a Location by Point API, the coordinates in the request and the response are in latitude/longitude format, whereas Azure Maps Get Reverse Geocoding API requires the coordinates in the request and the coordinates in the response use longitude/latitude format, as defined by [GeoJSON]. |
48-
| userRegion | ur | view | False | string | A string that represents an [ISO 3166-1 Alpha-2 region/country code]. This will alter geopolitical disputed borders and labels to align with the specified user region. By default, the View parameter is set to “Auto” even if you haven’t defined it in the request. |
49-
| | | | | | Please refer to [Supported Views] for details and to see the available Views. |
46+
| userRegion | ur | view | False | string | A string that represents an [ISO 3166-1 Alpha-2 region/country code]. This will alter geopolitical disputed borders and labels to align with the specified user region. By default, the View parameter is set to “Auto” even if you haven’t defined it in the request.<br><br> Please refer to [Supported Views] for details and to see the available Views. |
5047
| verboseplacenames | vbpn | Not supported | Not supported | Not supported | Azure Maps Get Reverse Geocoding API only supports returning [adminDistricts] short name (FL instead of Florida). |
5148

5249
For more information about the Azure Maps Get Reverse Geocoding API request parameters, see [URI Parameters].
@@ -69,7 +66,7 @@ http://atlas.microsoft.com/reverseGeocode?api-version=2023-06-01&coordinates=2.3
6966

7067
The following table lists the fields that can appear in the HTTP response when running the Bing Maps _Find a Location by Point_ request and the Azure Maps equivalent:
7168

72-
| Bing Maps Response | Azure Maps Response | Description |
69+
| Bing Maps response | Azure Maps response | Description |
7370
|---------------------------|------------------------|-------------------------------|
7471
| address: addressLine (JSON)<br>Address: AddressLine (XML) | address: addressLine | |
7572
| address: adminDistrict (JSON)<br>Address: AdminDistrict (XML) | address: adminDistricts | |
@@ -255,6 +252,7 @@ Support
255252

256253
- [Microsoft Q&A Forum]
257254

255+
[adminDistricts]: /rest/api/maps/search/get-reverse-geocoding#admindistricts
258256
[Authentication with Azure Maps]: azure-maps-authentication.md
259257
[Azure Account]: https://azure.microsoft.com/
260258
[Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account
@@ -268,6 +266,7 @@ Support
268266
[Microsoft Entra ID]: azure-maps-authentication.md#microsoft-entra-authentication
269267
[Microsoft Q&A Forum]: /answers/tags/209/azure-maps
270268
[request header]: /rest/api/maps/search/get-reverse-geocoding?#request-headers
269+
[Security section]: /rest/api/maps/search/get-reverse-geocoding#security
271270
[Shared Access Signature (SAS) Token]: azure-maps-authentication.md#shared-access-signature-token-authentication
272271
[subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
273272
[Supported Languages]: supported-languages.md

articles/azure-maps/migrate-find-location-query.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,17 +31,16 @@ This article explains how to migrate the Bing Maps [Find a Location by Query] AP
3131

3232
## Security and authentication
3333

34-
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps].
34+
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps] and the [Security section] in the Azure Maps Get Geocoding documentation.
3535

3636
## Request parameters
3737

3838
The following table lists the Bing Maps _Find a Location by Query_ request parameters and the Azure Maps equivalent:
3939

40-
| Bing Maps Request Parameter | Bing Maps Request Parameter Alias  | Azure Maps Request Parameter | Required in Azure Maps  | Azure Maps Data Type  | Description|
40+
| Bing Maps request parameter | Bing Maps request parameter alias  | Azure Maps request parameter | Required in Azure Maps  | Azure Maps data type  | Description|
4141
|-----------------------------|------------------------------------|------------------------------|-------------------------|-----------------------|------------|
4242
| culture | c | Request Header:  Accept-Language   | False | string | As specified in the Azure Maps [request header], `culture` defines the language used in search results when using the Azure Maps Get Geocoding API. For more information, see [Supported Languages].|
4343
| include | incl  | Not needed  | Not needed  | Not needed | In Bing Maps Find a Location by Query API, the `include` input parameter is required to get a two-letter ISO country code for the location result in the response (_include=ciso2_) and to specify that the response shows how the query string was parsed into address values (_include=queryParse_). In Azure Maps Get Geocoding API, the two-letter ISO country code is returned by default and doesn’t support a queryParse equivalent. |
44-
| || Not supported | Not supported  | Not supported  | |
4544
| includeNeighborhood  | inclnb  | Not needed  | Not needed  | Not needed | In Azure Maps Get Geocoding API, neighborhood info is returned in the response by default, when available.  |
4645
| maxResults | maxRes  | top  | False | Integer (int32)  | In Azure Maps Get Geocoding API, the default number of responses returned is 5. The minimum is 1 and the maximum is 20. |
4746
| query | q | query  | True | string | |
@@ -280,6 +279,7 @@ Support
280279
[Microsoft Q&A Forum]: /answers/tags/209/azure-maps
281280
[Migrate Bing Maps Find a Location by Address API]: migrate-find-location-address.md
282281
[request header]: /rest/api/maps/search/get-geocoding?#request-headers
282+
[Security section]: /rest/api/maps/search/get-geocoding#security
283283
[Shared Access Signature (SAS) Token]: azure-maps-authentication.md#shared-access-signature-token-authentication
284284
[subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
285285
[Supported Languages]: supported-languages.md

0 commit comments

Comments
 (0)