Skip to content

Commit afee01c

Browse files
authored
Update catalog-private-link-faqs.md
1 parent 1ac919a commit afee01c

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/purview/catalog-private-link-faqs.md

Lines changed: 3 additions & 1 deletion
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: how-to
9-
ms.date: 05/05/2022
9+
ms.date: 05/06/2022
1010
# Customer intent: As a Microsoft Purview admin, I want to set up private endpoints and managed vnets for my Microsoft Purview account for secure access or ingestion.
1111
---
1212
# FAQ about Microsoft Purview private endpoints and Managed VNets
@@ -139,8 +139,10 @@ At least one account and portal private endpoints are required, if public access
139139
At least one account, portal and ingestion private endpoint are required, if public access in Microsoft Purview account is set to **deny** and you are planning to scan additional data sources using a self-hosted integration runtime.
140140

141141
### What inbound and outbound communications are allowed through public endpoint for Microsoft Purview Managed VNets?
142+
142143
No inbound communication is allowed into a Managed VNet from public network.
143144
All ports are opened for outbound communications.
145+
In Microsoft Purview, a Managed VNet can be used to privately connect to Azure data sources to extract metadata during scan.
144146

145147
### Why do I receive the following error message when I try to launch Microsoft Purview governance portal from my machine?
146148

0 commit comments

Comments
 (0)