Skip to content

Commit e88baf4

Browse files
authored
Update concept-best-practices-network.md
1 parent 0a64ca1 commit e88baf4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/purview/concept-best-practices-network.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-catalog
88
ms.topic: conceptual
9-
ms.date: 01/21/2022
9+
ms.date: 01/26/2022
1010
---
1111

1212
# Azure Purview network architecture and best practices
@@ -202,7 +202,7 @@ For performance and cost optimization, we highly recommended deploying one or mo
202202

203203
#### Name resolution for single Azure Purview account
204204

205-
If you have one Azure Purview account in your tenant, and you have enabled private endpoints for account, portal and ingestion, you can use any of [the supported scenarios](catalog-private-link-name-resolution#deployment-options) for name resolution in your network.
205+
If you have one Azure Purview account in your tenant, and you have enabled private endpoints for account, portal and ingestion, you can use any of [the supported scenarios](catalog-private-link-name-resolution.md#deployment-options) for name resolution in your network.
206206

207207
#### Name resolution for multiple Azure Purview accounts
208208

0 commit comments

Comments
 (0)