Skip to content

Commit 7b3b180

Browse files
Merge pull request #229313 from vimalsmsft/master
Fixed the typo and corrected the information
2 parents 33ac3e6 + ea72416 commit 7b3b180

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/purview/catalog-firewall.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ To configure Microsoft Purview firewall follow these steps:
4646
- Public network access is set to _All networks_ on your Microsoft Purview account's Managed Event Hubs, if it's used.
4747

4848
> [!NOTE]
49-
> Even though the network access is enaled through public internet, to gain access to Microsoft Purview governance portal, users must be first authenticated and authorized.
49+
> Even though the network access is enabled through public internet, to gain access to Microsoft Purview governance portal, users must be first authenticated and authorized.
5050
5151
- **Disabled for ingestion only (Preview)**
5252

articles/purview/catalog-private-link-end-to-end.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ In this guide, you will learn how to deploy _account_, _portal_ and _ingestion_
1616

1717
The Microsoft Purview _account_ private endpoint is used to add another layer of security by enabling scenarios where only client calls that originate from within the virtual network are allowed to access the Microsoft Purview account. This private endpoint is also a prerequisite for the portal private endpoint.
1818

19-
The Microsoft Purview _compliance portal_ private endpoint is required to enable connectivity to [Microsoft Purview governance portal](https://web.purview.azure.com/resource/) using a private network.
19+
The Microsoft Purview _portal_ private endpoint is required to enable connectivity to [Microsoft Purview governance portal](https://web.purview.azure.com/resource/) using a private network.
2020

2121
Microsoft Purview can scan data sources in Azure or an on-premises environment by using _ingestion_ private endpoints. Three private endpoint resources are required to be deployed and linked to Microsoft Purview managed or configured resources when ingestion private endpoint is deployed:
2222

0 commit comments

Comments
 (0)