Skip to content

Commit d336787

Browse files
authored
Update concept-best-practices-accounts.md
1 parent 615a10a commit d336787

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/purview/concept-best-practices-accounts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ If Microsoft Purview is not available in your primary Azure region, consider the
9090

9191
- Review the latency between your primary Azure region where data sources are deployed and your secondary Azure region, where Microsoft Purview account will be deployed. For more information, see [Azure network round-trip latency statistics](https://learn.microsoft.com/azure/networking/azure-network-latency).
9292

93-
- Review your data residency requirements. When you scan data sources in the Microsoft Purview Data Map, information related to your metadata is ingested and stored inside your data map in the Azure region where your Microsoft Purview account is deployed. For more information see, [Where is metadata stored](concept-best-practices-security#where-is-metadata-stored)
93+
- Review your data residency requirements. When you scan data sources in the Microsoft Purview Data Map, information related to your metadata is ingested and stored inside your data map in the Azure region where your Microsoft Purview account is deployed. For more information see, [Where is metadata stored](concept-best-practices-security.md#where-is-metadata-stored)
9494

9595
- Review your network and security requirements if private network connectivity for user access or metadata ingestion is required.
9696

0 commit comments

Comments
 (0)