Skip to content

Commit a8eaf40

Browse files
laurabrenwhhender
andauthored
Update articles/purview/catalog-managed-vnet.md
Co-authored-by: Whitney Henderson <[email protected]>
1 parent bdd4524 commit a8eaf40

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/purview/catalog-managed-vnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ When you use a private link, traffic between your data sources and Managed Virtu
8181
Private endpoint uses a private IP address in the Managed Virtual Network to effectively bring the service into it. Private endpoints are mapped to a specific resource in Azure and not the entire service. Customers can limit connectivity to a specific resource approved by their organization. Learn more about [private links and private endpoints](../private-link/index.yml).
8282

8383
> [!NOTE]
84-
> to reduce administrative overhead, it's recommended that you create Managed private endpoints to scan all supported Azure data sources.
84+
> To reduce administrative overhead, it's recommended that you create managed private endpoints to scan all supported Azure data sources.
8585
8686
> [!WARNING]
8787
> If an Azure PaaS data store (Blob, Azure Data Lake Storage Gen2, Azure Synapse Analytics) has a private endpoint already created against it, and even if it allows access from all networks, Purview would only be able to access it using a managed private endpoint. If a private endpoint does not already exist, you must create one in such scenarios.

0 commit comments

Comments
 (0)