Merge pull request #290097 from stevemunk/consent-management

Information on consent management

Author: Jill Grant

articles/azure-maps/consent-management.md

@@ -0,0 +1,36 @@
+---
+title: Microsoft Azure Maps consent management
+description: This article describes consent management in Azure Maps as it applies to data residency laws.
+author: pbrasil
+ms.author: peterbr
+ms.date: 11/19/2024
+ms.topic: conceptual
+ms.service: azure-maps
+ms.subservice: manage-account
+---
+
+# Consent management
+
+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).
+
+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].
+
+For more information on geographic scope in Azure Maps, see [Azure Maps service geographic scope].
+
+## Frequently asked questions
+
+**My scenario doesn't have any South Korea data. Do I still need to enable cross region processing to use Azure Maps?**
+
+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.
+
+**Where will my data be stored if I enable cross region processing in South Korea?**
+
+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.
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Configure global data processing]
+
+[Azure Maps service geographic scope]: geographic-scope.md
+[Configure global data processing]: how-to-manage-consent.md

articles/azure-maps/geocoding-coverage.md

@@ -133,7 +133,7 @@ The ability to geocode in a country/region is dependent upon the road data cover
 | Samoa                                               |                 |                |              |      ✓     |       ✓        |
 | Singapore                                           |        ✓        |        ✓      |       ✓      |      ✓     |       ✓        |
 | Solomon Islands                                     |                 |                |              |      ✓     |       ✓        |
-| South Korea                                         |                 |                |              |      ✓     |       ✓        |
+| South Korea<sup>1</sup>                             |                 |                |              |      ✓     |       ✓        |
 | Sri Lanka                                           |                 |                |              |      ✓     |       ✓        |
 | Taiwan                                              |        ✓        |        ✓      |       ✓      |      ✓     |       ✓        |
 | Thailand                                            |        ✓        |                |       ✓     |      ✓     |       ✓        |
@@ -146,6 +146,8 @@ The ability to geocode in a country/region is dependent upon the road data cover
 | Vietnam                                             |        ✓        |                |       ✓     |      ✓     |       ✓        |
 | Wallis & Futuna                                     |                 |                |              |      ✓     |       ✓        |
 
+<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).
+
 ## Europe
 
 | Country/Region                                      | Address points  |House numbers  | Street level  | City level | Points of interest |

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

@@ -0,0 +1,127 @@
+---
+title: Configure global data processing
+description: This article describes how to configure the global data processing settings in Azure Maps to comply with data residency laws.
+author: pbrasil
+ms.author: peterbr
+ms.date: 11/19/2024
+ms.topic: how-to
+ms.service: azure-maps
+ms.subservice: manage-account
+---
+
+# Configure global data processing
+
+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].
+
+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.
+
+> [!IMPORTANT]
+> 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.
+
+## Configure global data processing in the Azure portal
+
+The Azure Maps Resource location is enabled by default and can be configured in the **Process Data Globally** page of the Azure portal.
+
+To give consent to one or more regions:
+
+1. Sign in to your Azure Maps Account in the [Azure portal].
+1. In **Settings**, select **Process data globally**.
+
+   A map of the world appears with a plus sign for each region that can be selected.
+
+   :::image type="content" source="./media/consent-management/process-data-globally.png" lightbox="./media/consent-management/process-data-globally.png" alt-text="Screenshot showing the process data globally screen in the Azure portal.":::
+
+1. Additionally you can select **Add region**, then select the region you wish to add or remove.
+
+   :::image type="content" source="./media/consent-management/select-korea-central.png" lightbox="./media/consent-management/select-korea-central.png" alt-text="Screenshot showing the process data globally screen in the Azure portal with the Korea Central region selected.":::
+
+1. Once you all desired regions are chosen, select **Save**.
+
+   :::image type="content" source="./media/consent-management/save-selection.png" lightbox="./media/consent-management/save-selection.png" alt-text="Screenshot showing the save button highlighted in process data globally screen in the Azure portal.":::
+
+Once your updates are saved, one or more new selections appear in the list of regions.
+
+:::image type="content" source="./media/consent-management/new-region-added.png" lightbox="./media/consent-management/new-region-added.png" alt-text="Screenshot showing the process data globally screen in the Azure portal with the Korea Central region added to the list of supported regions.":::
+
+## Configure global data processing using REST API
+
+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.
+
+Be sure to include the appropriate [subscription key], resource group and Azure Maps account name.
+
+```html
+https://management.azure.com/subscriptions/<subscription-key>/resourceGroups/<resource-group-name>/providers/Microsoft.Maps/accounts/<account-name>?api-version=2024-07-01-preview
+```
+
+**Header**
+
+Be sure to include a correct [access-token].
+
+```html
+Content-Type: application/json
+Authorization: Bearer <access-token> 
+```
+
+**Body**
+
+```json
+{
+  "properties": {
+    "locations": [
+      {
+        "locationName": "Korea Central"
+      }
+    ]
+  },
+}
+```
+
+## Configure global data processing using an ARM deployment template
+
+The following template will add _West Europe_ to the list of valid global data processing regions.
+
+Be sure to include the appropriate Azure Maps account name and location.
+
+```json
+{
+  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+  "contentVersion": "1.0.0.0",
+  "resources": [
+    {
+      "type": "Microsoft.Maps/accounts",
+      "apiVersion": "2024-07-01-preview",
+      "name": "<account-name>",
+      "location": "<account-location>",
+      "sku": {
+        "name": "G2"
+      },
+      "properties":
+      {
+        "locations": [
+          {
+            "locationName": "West Europe"
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+> [!NOTE]
+> Your data is always stored in the region you created your Azure Maps Account, regardless of your global data processing settings.
+
+## Next steps
+
+Azure Maps is a global service that allows specifying a geographic scope, which enables limiting data residency to specific regions.
+
+> [!div class="nextstepaction"]
+> [Azure Maps service geographic scope]
+
+[access-token]: azure-maps-authentication.md#microsoft-entra-authentication
+[Accounts - Update]: /rest/api/maps-management/accounts/update
+[Azure Maps Account Management REST APIs]: /rest/api/maps-management/accounts
+[Azure portal]: https://ms.portal.azure.com
+[Azure Maps service geographic scope]: geographic-scope.md
+[Consent management]: consent-management.md
+[subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account

articles/azure-maps/media/consent-management/new-region-added.png

@@ -50,6 +50,8 @@ items:
     href: choose-pricing-tier.md
   - name: Azure Maps geographic scope
     href: geographic-scope.md
+  - name: Consent management
+    href: consent-management.md
   - name: Creator for Indoor maps
     items:
     - name: Indoor map concepts
@@ -437,6 +439,8 @@ items:
     href: how-to-use-feedback-tool.md
   - name: Show right attribution
     href: how-to-show-attribution.md
+  - name: Manage consent
+    href: how-to-manage-consent.md
 - name: Reference
   items:
   - name: Creator Indoor Maps