Skip to content

Commit 556a69b

Browse files
committed
Minor updates.
1 parent 944ca1b commit 556a69b

File tree

2 files changed

+13
-6
lines changed

2 files changed

+13
-6
lines changed

articles/azure-maps/consent-management.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,18 @@ Azure Maps is a global service that is available worldwide. When creating your A
1515

1616
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].
1717

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-
2118
For more information on geographic scope in Azure Maps, see [Azure Maps service geographic scope].
2219

20+
## Frequently asked questions
21+
22+
**My scenario doesn't have any South Korea data. Do I still need to enable cross region processing to use Azure Maps?**
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.
25+
26+
**Where will my data be stored if I enable cross region processing in South Korea?**
27+
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.
29+
2330
## Next Steps
2431

2532
> [!div class="nextstepaction"]

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,9 +43,6 @@ Once your updates are saved, one or more new selections appear in the list of re
4343

4444
:::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.":::
4545

46-
> [!NOTE]
47-
> Your data is always stored in the region you created your Azure Maps Account, regardless of your global data processing settings.
48-
4946
## Configure global data processing using REST API
5047

5148
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.
@@ -111,6 +108,9 @@ Be sure to include the appropriate Azure Maps account name and location.
111108
}
112109
```
113110

111+
> [!NOTE]
112+
> Your data is always stored in the region you created your Azure Maps Account, regardless of your global data processing settings.
113+
114114
## Next steps
115115

116116
Azure Maps is a global service that allows specifying a geographic scope, which enables limiting data residency to specific regions.

0 commit comments

Comments
 (0)