You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-maps/consent-management.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,17 +13,17 @@ ms.subservice: manage-account
13
13
14
14
Azure Maps is a global service that is available worldwide. When creating your Azure Maps account, you select a _Region_. The Region selection is the accounts geographic scope, which allows you to limit data residency to the selected region. All requests (including input data) are processed and stored exclusively in the specified geographic area (region).
15
15
16
-
In some cases, you will need to enable your search requests to be processed in a region or geography other than the one your Azure Maps Account is in. For example, due to local data residency laws, all South Korean addresses must be processed in South Korea, which is the _Korea Central_ region in Azure Maps. To do this, you must give Azure Maps consent to process your data in the _Korea Central_ region. For more information on how to give Azure Maps consent to process data in a different region, see [Configure global data processing].
16
+
In some cases, you will need to enable your search requests to be processed in a region or geography other than the one your Azure Maps Account is in. For example, due to local data residency laws, all Korean addresses must be processed in Korea, which is the _Korea Central_ region in Azure Maps. To do this, you must give Azure Maps consent to process your data in the _Korea Central_ region. For more information on how to give Azure Maps consent to process data in a different region, see [Configure global data processing].
17
17
18
18
For more information on geographic scope in Azure Maps, see [Azure Maps service geographic scope].
19
19
20
20
## Frequently asked questions
21
21
22
-
**My scenario doesn't have any South Korea data. Do I still need to enable cross region processing to use Azure Maps?**
22
+
**My scenario doesn't have any Korean data. Do I still need to enable cross region processing to use Azure Maps?**
23
23
24
-
No, if your scenario doesn't require South Korea data, you don't need to enable cross region processing. This is a specific regional requirement due to data residency laws.
24
+
No, if your scenario doesn't require Korean data, you don't need to enable cross region processing. This is a specific regional requirement due to data residency laws.
25
25
26
-
**Where will my data be stored if I enable cross region processing in South Korea?**
26
+
**Where will my data be stored if I enable cross region processing in Korea?**
27
27
28
28
Giving consent to process data in a different region will not affect where your metadata and logs are stored. Those are still contained within the region specified when creating your Azure Maps Account.
Copy file name to clipboardExpand all lines: articles/azure-maps/geocoding-coverage.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,6 +110,7 @@ The ability to geocode in a country/region is dependent upon the road data cover
110
110
| Indonesia | ✓ | ✓ | ✓ | ✓ | ✓ |
111
111
| Japan |||| ✓ | ✓ |
112
112
| Kiribati |||| ✓ | ✓ |
113
+
| Korea<sup>1</sup> |||| ✓ | ✓ |
113
114
| Laos | ✓ || ✓ | ✓ | ✓ |
114
115
| Macao SAR | ✓ | ✓ | ✓ | ✓ | ✓ |
115
116
| Malaysia | ✓ | ✓ | ✓ | ✓ | ✓ |
@@ -133,7 +134,6 @@ The ability to geocode in a country/region is dependent upon the road data cover
133
134
| Samoa |||| ✓ | ✓ |
134
135
| Singapore | ✓ | ✓ | ✓ | ✓ | ✓ |
135
136
| Solomon Islands |||| ✓ | ✓ |
136
-
| South Korea<sup>1</sup> |||| ✓ | ✓ |
137
137
| Sri Lanka |||| ✓ | ✓ |
138
138
| Taiwan | ✓ | ✓ | ✓ | ✓ | ✓ |
139
139
| Thailand | ✓ || ✓ | ✓ | ✓ |
@@ -146,7 +146,7 @@ The ability to geocode in a country/region is dependent upon the road data cover
146
146
| Vietnam | ✓ || ✓ | ✓ | ✓ |
147
147
| Wallis & Futuna |||| ✓ | ✓ |
148
148
149
-
<sup>1</sup> Coverage is dependent on enabling data processing in South Korea. For more information, see [Configure global data processing](how-to-manage-consent.md).
149
+
<sup>1</sup> Coverage is dependent on enabling data processing in Korea. For more information, see [Configure global data processing](how-to-manage-consent.md).
Copy file name to clipboardExpand all lines: articles/azure-maps/how-to-manage-consent.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ In some cases, it may be necessary to process requests in a region different fro
16
16
This article guides you on configuring global data processing settings to comply with data residency laws using multiple approaches including the [Azure Portal](#configure-global-data-processing-in-the-azure-portal), [REST APIs](#configure-global-data-processing-using-rest-api) or an [ARM deployment template](#configure-global-data-processing-using-an-arm-deployment-template). This allows Azure Maps to process address requests within the specified country's region, regardless of your Azure Maps Account's region.
17
17
18
18
> [!IMPORTANT]
19
-
> If your scenarios don't involve South Korea data, there is no need to enable cross-region processing. This requirement is specific to South Korea due to its data residency laws.
19
+
> If your scenarios don't involve Korean data, there is no need to enable cross-region processing. This requirement is specific to Korea due to its data residency laws.
20
20
21
21
## Configure global data processing in the Azure portal
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-find-location-address.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ This article explains how to migrate the Bing Maps [Find a Location by Address]
26
26
- Bing Maps Find a Location by Address API returns coordinates in latitude/longitude format, while Azure Maps Get Geocoding API returns coordinates in longitude/latitude format, as defined by the [GeoJSON] format.
27
27
- Bing Maps Find a Location by Address API supports XML and JSON response format. Azure Maps Get Geocoding API supports GeoJSON.
28
28
- Unlike Bing Maps Find a Location by Address API, Azure Maps Get Geocoding API has a `view` input parameter, which is a string that represents an [ISO 3166-1 Alpha-2 region/country code]. The `view` input parameter alters geopolitical disputed borders and labels to align with the specified user region. For more information, see [URI Parameters].
29
-
- Unlike Bing Maps Find a Location by Address API, Azure Maps Get Geocoding API doesn’t currently support address geocoding for China, Japan, or South Korea.
29
+
- Unlike Bing Maps Find a Location by Address API, Azure Maps Get Geocoding API doesn’t currently support address geocoding in China.
30
30
- Unlike Bing Maps for Enterprise, Azure Maps is a global service that supports specifying a geographic scope, allowing limits to data residency to the European (EU) or United States (US) geographic areas (geos). All requests (including input data) are processed exclusively in the specified geographic area. For more information, see [geographic scope].
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-find-location-by-point.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ This article explains how to migrate the Bing Maps [Find a Location by Point] AP
24
24
25
25
- Bing Maps Find a Location by Point API supports XML and JSON response formats. Azure Maps Get Reverse Geocoding API supports the [GeoJSON] response format.
26
26
- Bing Maps Find a Location by Point API uses coordinates in the latitude/longitude format. Azure Maps Get Reverse Geocoding API uses coordinates in the longitude/latitude format, as defined by [GeoJSON].
27
-
- Unlike Bing Maps Find a Location by Point API, Azure Maps Get Reverse Geocoding API doesn’t currently support address or street level data for China, Japan or South Korea.
27
+
- Unlike Bing Maps Find a Location by Point API, Azure Maps Get Reverse Geocoding API doesn’t currently support address or street level data for China.
28
28
- Unlike Bing Maps Find a Location by Point API, Azure Maps Get Reverse Geocoding API has a `view` input parameter, which is a string that represents an [ISO 3166-1 Alpha-2 region/country code]. The `view` input parameter will alter geopolitical disputed borders and labels to align with the specified user region. For more information, see [URI Parameters].
29
29
- Unlike Bing Maps for Enterprise, Azure Maps is a global service that supports specifying a geographic scope, which allows you to limit data residency to the European (EU) or United States (US) geographic areas (geos). All requests (including input data) are processed exclusively in the specified geographic area. For more information, see [Azure Maps service geographic scope].
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-find-location-query.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ This article explains how to migrate the Bing Maps [Find a Location by Query] AP
26
26
- Bing Maps Find a Location by Query API returns coordinates in latitude/longitude format, while Azure Maps Get Geocoding API returns coordinates in longitude/latitude format, as defined by the [GeoJSON] format.
27
27
- Bing Maps Find a Location by Query API supports XML and JSON response format. Azure Maps Get Geocoding API supports GeoJSON.
28
28
- Unlike Bing Maps Find a Location by Query API, Azure Maps Get Geocoding API has a `view` input parameter, which is a string that represents an [ISO 3166-1 Alpha-2 region/country code]. The `view` input parameter alters geopolitical disputed borders and labels to align with the specified user region. For more information, see [URI Parameters].
29
-
- Unlike Bing Maps Find a Location by Query API, Azure Maps Get Geocoding API doesn’t currently support address geocoding for China, Japan, or South Korea.
29
+
- Unlike Bing Maps Find a Location by Query API, Azure Maps Get Geocoding API doesn’t currently support address geocoding in China.
30
30
- Unlike Bing Maps for Enterprise, Azure Maps is a global service that supports specifying a geographic scope, allowing limits to data residency to the European (EU) or United States (US) geographic areas (geos). All requests (including input data) are processed exclusively in the specified geographic area. For more information, see [geographic scope].
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments