|
| 1 | +--- |
| 2 | +title: Enable South Korea addresses in Azure Maps |
| 3 | +titleSuffix: Microsoft Azure Maps consent management |
| 4 | +description: This article describes how to configure the global data processing settings to enable South Korea addresses in Azure Maps. |
| 5 | +author: pbrasil |
| 6 | +ms.author: peterbr |
| 7 | +ms.date: 11/11/2024 |
| 8 | +ms.topic: how-to |
| 9 | +ms.service: azure-maps |
| 10 | +ms.subservice: manage-account |
| 11 | +--- |
| 12 | + |
| 13 | +# Enable South Korea addresses in Azure Maps |
| 14 | + |
| 15 | +To comply with South Korea's data residency laws, Azure Maps processes requests for South Korean addresses within the South Korean region. Customers can store private information in the region their Azure Maps account exists while sending specific South Korea data requests across regions. |
| 16 | + |
| 17 | +This article explains how to configure the global data processing settings in your Azure Maps account using the Azure portal. |
| 18 | + |
| 19 | +> [!NOTE] |
| 20 | +> This enables the configuration of where data processing occurs and does not impact where data is stored. |
| 21 | +
|
| 22 | +## Understanding geographic scope and consent |
| 23 | + |
| 24 | +Azure Maps is a global service that allows specifying a geographic scope, which enables limiting data residency to specific regions. For more information, see [Azure Maps service geographic scope](geographic-scope.md). |
| 25 | + |
| 26 | +In certain circumstances, it may be necessary to enable requests to be processed in a different region. For example, to expand coverage in a particular area that is restricted due to local data residency laws. In such cases, Azure Maps can be granted consent to process your data in other specified regions. |
| 27 | + |
| 28 | +> [!IMPORTANT] |
| 29 | +> If your scenarios don't involve South Korea data, you do not need to enable cross region processing. This is a specific regional requirement due to data residency laws. |
| 30 | +
|
| 31 | +## Configure global data processing |
| 32 | + |
| 33 | +The Azure Maps Resource location is enabled by default and can be configured in the **Process Data Globally** page of the Azure portal. |
| 34 | + |
| 35 | +To give consent to one or more regions: |
| 36 | + |
| 37 | +1. Sign in to your Azure Maps Account in the Azure portal. |
| 38 | +1. In settings, select **Process data globally**. |
| 39 | +1. In the map that appears, select the regions you wish to add or remove. |
| 40 | + |
| 41 | + :::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."::: |
| 42 | + |
| 43 | +1. Once all desired regions are chosen, select **Save**. |
| 44 | + |
| 45 | +> [!NOTE] |
| 46 | +> Your data is always stored in the region you created your Azure Maps Account, regardless of your global data processing settings. |
0 commit comments