Skip to content

Commit 8d2bc0e

Browse files
stevemunkstevemunk
committed
Added concept article and removed render coverage as it does not apply to consent management.
1 parent 4d41e67 commit 8d2bc0e

File tree

3 files changed

+101
-12
lines changed

3 files changed

+101
-12
lines changed

‎articles/azure-maps/consent-management.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: Microsoft Azure Maps consent management
3+
description: This article describes consent management in Azure Maps as it applies to data residency laws.
4+
author: pbrasil
5+
ms.author: peterbr
6+
ms.date: 11/19/2024
7+
ms.topic: conceptual
8+
ms.service: azure-maps
9+
ms.subservice: manage-account
10+
---
11+
12+
# Consent management
13+
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+
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].
17+
18+
> [!NOTE]
19+
> 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.
20+
21+
For more information on geographic scope in Azure Maps, see [Azure Maps service geographic scope].
22+
23+
## Next Steps
24+
25+
> [!div class="nextstepaction"]
26+
> [Configure global data processing]
27+
28+
[Azure Maps service geographic scope]: geographic-scope.md
29+
[Configure global data processing]: how-to-manage-consent.md

‎articles/azure-maps/how-to-manage-consent.md

Lines changed: 71 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
---
2-
title: Microsoft Azure Maps consent management
3-
description: This article describes how to configure the global data processing settings to comply with data residency laws in Azure Maps.
2+
title: Configure global data processing
3+
description: This article describes how to configure the global data processing settings in Azure Maps to comply with data residency laws.
44
author: pbrasil
55
ms.author: peterbr
6-
ms.date: 11/15/2024
6+
ms.date: 11/19/2024
77
ms.topic: how-to
88
ms.service: azure-maps
99
ms.subservice: manage-account
1010
---
1111

12-
# Consent management
12+
# Configure global data processing
1313

14-
In some cases, it may be necessary to process requests in a region different from your Azure Maps Account's region due to local data residency laws. When this happens, you can grant Azure Maps consent to process your data in other specified regions.
14+
In some cases, it may be necessary to process requests in a region different from your Azure Maps Account's region due to local data residency laws. When this happens, you can grant Azure Maps consent to process your data in other specified regions. For more information, see [Consent management].
1515

16-
This article guides you on configuring global data processing settings in your Azure Maps account in the Azure portal to comply with data residency laws. This allows Azure Maps to process address requests within the specified country's region, regardless of your Azure Maps Account's region.
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-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.
1717

1818
> [!IMPORTANT]
1919
> 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.
@@ -46,7 +46,66 @@ Once your updates are saved, one or more new selections appear in the list of re
4646
> [!NOTE]
4747
> Your data is always stored in the region you created your Azure Maps Account, regardless of your global data processing settings.
4848
49-
<!--## Configure global data processing using ARM deployment template-->
49+
## Configure global data processing using REST API
50+
51+
Consent can be managed using [Azure Maps Account Management REST APIs]. To Configure global data processing, send an [Accounts - Update] `PATCH` request and pass in the `properties.locations` parameter in the body of the request.
52+
53+
Be sure to include the appropriate [subscription key], respurce group and Azure Maps account name.
54+
55+
```html
56+
https://management.azure.com/subscriptions/<subscription-key>/resourceGroups/<resource-group-name>/providers/Microsoft.Maps/accounts/<account-name>?api-version=2024-07-01-preview
57+
```
58+
59+
**Header**
60+
61+
- Content-Type: application/json
62+
- Authorization: Bearer <access-token>
63+
64+
**Body**
65+
66+
```json
67+
{
68+
"properties": {
69+
"locations": [
70+
{
71+
"locationName": "Korea Central"
72+
}
73+
]
74+
},
75+
}
76+
```
77+
78+
## Configure global data processing using an ARM deployment template
79+
80+
The following template will add _West Europe_ to the list of valid global data processing regions.
81+
82+
Be sure to include the appropriate Azure Maps account name and location.
83+
84+
```json
85+
{
86+
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
87+
"contentVersion": "1.0.0.0",
88+
"resources": [
89+
{
90+
"type": "Microsoft.Maps/accounts",
91+
"apiVersion": "2024-07-01-preview",
92+
"name": "<account-name>",
93+
"location": "<account-location>",
94+
"sku": {
95+
"name": "G2"
96+
},
97+
"properties":
98+
{
99+
"locations": [
100+
{
101+
"locationName": "West Europe"
102+
}
103+
]
104+
}
105+
}
106+
]
107+
}
108+
```
50109

51110
## Next steps
52111

@@ -55,6 +114,9 @@ Azure Maps is a global service that allows specifying a geographic scope, which
55114
> [!div class="nextstepaction"]
56115
> [Azure Maps service geographic scope]
57116
58-
117+
[Accounts - Update]: /rest/api/maps-management/accounts/update
118+
[Azure Maps Account Management REST APIs]: /rest/api/maps-management/accounts
59119
[Azure portal]: https://ms.portal.azure.com
60-
[Azure Maps service geographic scope]: geographic-scope.md
120+
[Azure Maps service geographic scope]: geographic-scope.md
121+
[Consent management]: consent-management.md
122+
[subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account

‎articles/azure-maps/render-coverage.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -95,13 +95,11 @@ The render coverage tables below list the countries/regions that support Azure M
9595
| New Zealand | ✓ |
9696
| Philippines | ✓ |
9797
| Singapore | ✓ |
98-
| South Korea<sup>1</sup> | ◑ |
98+
| South Korea | ◑ |
9999
| Taiwan | ✓ |
100100
| Thailand | ✓ |
101101
| Vietnam | ✓ |
102102

103-
<sup>1</sup> Coverage is dependent on enabling data processing in South Korea. For more information, see [Enable South Korea addresses in Azure Maps](how-to-manage-consent.md)
104-
105103
## Europe
106104

107105
| Country/Region | Coverage |

0 commit comments

Comments
 (0)