Skip to content

Commit 95fadc0

Browse files
authored
Update concept-best-practices-accounts.md
1 parent 012a076 commit 95fadc0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: zeinam
66
ms.service: purview
77
ms.subservice: purview-data-map
88
ms.topic: conceptual
9-
ms.date: 01/27/2023
9+
ms.date: 01/28/2023
1010
---
1111

1212
# Microsoft Purview accounts architectures and best practices
@@ -88,7 +88,7 @@ Microsoft Purview is an Azure platform as a service solution. You can deploy a M
8888

8989
If Microsoft Purview is not available in your primary Azure region, consider the following factors when choosing a secondary region to deploy your Microsoft Purview account:
9090

91-
- 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).
91+
- 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](../networking/azure-network-latency.md).
9292

9393
- 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

0 commit comments

Comments
 (0)