Skip to content

Commit 2fc2417

Browse files
authored
pencil edits
Line 215: adimistrative > administrative Line 248: Microsoft Purview portal > Microsoft Purview governance portal
1 parent af18944 commit 2fc2417

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
@@ -212,7 +212,7 @@ For performance and cost optimization, we highly recommended deploying one or mo
212212

213213
You can use Managed VNet Runtime to scan data sources in a private network, if your Microsoft Purview account is deployed in any of the [supported regions](catalog-managed-vnet.md#supported-regions) and you are planning to scan Any of the supported [Azure data sources](catalog-managed-vnet.md#supported-data-sources).
214214

215-
Using Managed VNet Runtime helps to minimize the adimistrative overhead of managing the runtime and reduce overall scan duration.
215+
Using Managed VNet Runtime helps to minimize the administrative overhead of managing the runtime and reduce overall scan duration.
216216

217217
To scan any Azure data sources using Managed VNet Runtime, a managed private endpoint must be deployed within Microsoft Purview Managed Virtual Network, even if the data source already has a private network in your Azure subscription.
218218

@@ -245,7 +245,7 @@ For this scenario:
245245

246246
- This option is recommended if you have data sources in both primary and secondary regions and users are connected through the primary region.
247247
- Deploy a Microsoft Purview account in your secondary region (for example, Australia East).
248-
- Deploy Microsoft Purview portal private endpoint in the primary region (for example, Australia Southeast) for user access to Microsoft Purview governance portal.
248+
- Deploy Microsoft Purview governance portal private endpoint in the primary region (for example, Australia Southeast) for user access to Microsoft Purview governance portal.
249249
- Deploy Microsoft Purview account and ingestion private endpoints in your primary region (for example, Australia southeast) to scan data sources locally in the primary region.
250250
- Deploy Microsoft Purview account and ingestion private endpoints in your secondary region (for example, Australia East) to scan data sources locally in the secondary region.
251251
- Deploy [Microsoft Purview self-hosted integration runtime]( manage-integration-runtimes.md) VMs in both primary and secondary regions. This will help to keep data Map scan traffic in the local region and send only metadata to Microsoft Purview Data Map where is configured in your secondary region (for example, Australia East).

0 commit comments

Comments
 (0)