Skip to content

Commit 8f5b681

Browse files
authored
Merge pull request #185733 from zeinab-mk/patch-5
minor updates
2 parents d6186cd + 5ed665a commit 8f5b681

File tree

2 files changed

+3
-4
lines changed

2 files changed

+3
-4
lines changed

articles/purview/catalog-private-link-name-resolution.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: viseshag
66
ms.service: purview
77
ms.subservice: purview-data-catalog
88
ms.topic: how-to
9-
ms.date: 01/10/2022
9+
ms.date: 01/21/2022
1010
# Customer intent: As an Azure Purview admin, I want to set up private endpoints for my Azure Purview account, for secure access.
1111
---
1212

@@ -175,7 +175,6 @@ If you do not use DNS forwarders and instead you manage A records directly in yo
175175
| `Contoso-Purview.proxy.purview.azure.com` | A | \<account private endpoint IP address of Azure Purview\> |
176176
| `Contoso-Purview.guardian.purview.azure.com` | A | \<account private endpoint IP address of Azure Purview\> |
177177
| `gateway.purview.azure.com` | A | \<account private endpoint IP address of Azure Purview\> |
178-
| `Contoso-Purview.web.purview.azure.com` | A | \<portal private endpoint IP address of Azure Purview\> |
179178
| `manifest.prod.ext.web.purview.azure.com` | A | \<portal private endpoint IP address of Azure Purview\> |
180179
| `cdn.prod.ext.web.purview.azure.com` | A | \<portal private endpoint IP address of Azure Purview\> |
181180
| `hub.prod.ext.web.purview.azure.com` | A | \<portal private endpoint IP address of Azure Purview\> |

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/13/2022
9+
ms.date: 01/21/2022
1010
---
1111

1212
# Azure Purview network architecture and best practices
@@ -96,7 +96,7 @@ When you're scanning a data source in Azure Purview, you need to provide a crede
9696

9797
### Additional considerations
9898

99-
- If you choose to scan data sources by using public endpoints, your on-premises or VM-based data sources must have outbound connectivity to Azure endpoints.
99+
- If you choose to scan data sources using public endpoints, your self-hosted integration runtime VMs must have outbound access to data sources and Azure endpoints.
100100

101101
- Your self-hosted integration runtime VMs must have [outbound connectivity to Azure endpoints](manage-integration-runtimes.md#networking-requirements).
102102

0 commit comments

Comments
 (0)