Merge pull request #194312 from Clare-Zheng82/0401-Modify_managed_VNET_case

Update the case of managed VNET in Managed virtual network doc

Author: Maggiemouse1

articles/data-factory/managed-virtual-network-private-endpoint.md

@@ -7,48 +7,48 @@ ms.service: data-factory
 ms.subservice: integration-runtime
 ms.topic: conceptual
 ms.custom: seo-lt-2019, references_regions, devx-track-azurepowershell
-ms.date: 09/28/2021
+ms.date: 04/01/2022
 ---
 
 # Azure Data Factory Managed Virtual Network
 
 [!INCLUDE[appliesto-adf-xxx-md](includes/appliesto-adf-xxx-md.md)]
 
-This article will explain Managed Virtual Network and Managed Private endpoints in Azure Data Factory.
+This article will explain managed virtual network and Managed Private endpoints in Azure Data Factory.
 
 
 ## Managed virtual network
 
-When you create an Azure Integration Runtime (IR) within Azure Data Factory Managed Virtual Network (VNET), the integration runtime will be provisioned with the managed Virtual Network and will leverage private endpoints to securely connect to supported data stores. 
+When you create an Azure Integration Runtime (IR) within Azure Data Factory managed virtual network (VNET), the integration runtime will be provisioned with the managed virtual network and will leverage private endpoints to securely connect to supported data stores. 
 
-Creating an Azure IR within managed Virtual Network ensures that data integration process is isolated and secure. 
+Creating an Azure IR within managed virtual network ensures that data integration process is isolated and secure. 
 
-Benefits of using Managed Virtual Network:
+Benefits of using managed virtual network:
 
-- With a Managed Virtual Network, you can offload the burden of managing the Virtual Network to Azure Data Factory. You don't need to create a subnet for Azure Integration Runtime that could eventually use many private IPs from your Virtual Network and would require prior network infrastructure planning. 
+- With a managed virtual network, you can offload the burden of managing the virtual network to Azure Data Factory. You don't need to create a subnet for Azure Integration Runtime that could eventually use many private IPs from your virtual network and would require prior network infrastructure planning. 
 - It does not require deep Azure networking knowledge to do data integrations securely. Instead getting started with secure ETL is much simplified for data engineers. 
-- Managed Virtual Network along with Managed private endpoints protects against data exfiltration. 
+- Managed virtual network along with Managed private endpoints protects against data exfiltration. 
 
 > [!IMPORTANT]
->Currently, the managed Virtual Network is only supported in the same region as Azure Data Factory region.
+>Currently, the managed virtual network is only supported in the same region as Azure Data Factory region.
 
 > [!Note]
 >Existing global Azure integration runtime can't switch to Azure integration runtime in Azure Data Factory managed virtual network and vice versa.
  
 
-:::image type="content" source="./media/managed-vnet/managed-vnet-architecture-diagram.png" alt-text="ADF Managed Virtual Network architecture":::
+:::image type="content" source="./media/managed-vnet/managed-vnet-architecture-diagram.png" alt-text="ADF managed virtual network architecture":::
 
 ## Managed private endpoints
 
-Managed private endpoints are private endpoints created in the Azure Data Factory Managed Virtual Network establishing a private link to Azure resources. Azure Data Factory manages these private endpoints on your behalf. 
+Managed private endpoints are private endpoints created in the Azure Data Factory managed virtual network establishing a private link to Azure resources. Azure Data Factory manages these private endpoints on your behalf. 
 
 :::image type="content" source="./media/tutorial-copy-data-portal-private/new-managed-private-endpoint.png" alt-text="New Managed private endpoint":::
 
 Azure Data Factory supports private links. Private link enables you to access Azure (PaaS) services (such as Azure Storage, Azure Cosmos DB, Azure Synapse Analytics).
 
-When you use a private link, traffic between your data stores and managed Virtual Network traverses entirely over the Microsoft backbone network. Private Link protects against data exfiltration risks. You establish a private link to a resource by creating a private endpoint.
+When you use a private link, traffic between your data stores and managed virtual network traverses entirely over the Microsoft backbone network. Private Link protects against data exfiltration risks. You establish a private link to a resource by creating a private endpoint.
 
-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).
+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).
 
 > [!NOTE]
 > It's recommended that you create Managed private endpoints to connect to all your Azure data sources. 
@@ -132,7 +132,7 @@ New-AzResource -ApiVersion "${apiVersion}" -ResourceId "${integrationRuntimeReso
 ## Limitations and known issues
 
 ### Supported data sources
-The following data sources have native Private Endpoint support and can be connected through private link from ADF Managed Virtual Network.
+The following data sources have native Private Endpoint support and can be connected through private link from ADF managed virtual network.
 - Azure Blob Storage (not including Storage account V1)
 - Azure Cognitive Search
 - Azure Cosmos DB MongoDB API
@@ -155,21 +155,21 @@ The following data sources have native Private Endpoint support and can be conne
 > You still can access all data sources that are supported by Data Factory through public network.
 
 > [!NOTE]
-> Because Azure SQL Managed Instance native Private Endpoint in public preview, you can access it from managed Virtual Network using Private Linked Service and Load Balancer. Please see [How to access SQL Managed Instance from Data Factory Managed VNET using Private Endpoint](tutorial-managed-virtual-network-sql-managed-instance.md).
+> Because Azure SQL Managed Instance native Private Endpoint in public preview, you can access it from managed virtual network using Private Linked Service and Load Balancer. Please see [How to access SQL Managed Instance from Data Factory Managed VNET using Private Endpoint](tutorial-managed-virtual-network-sql-managed-instance.md).
 
 ### On-premises data sources
-To access on-premises data sources from managed Virtual Network using Private Endpoint, please see this tutorial [How to access on-premises SQL Server from Data Factory Managed VNET using Private Endpoint](tutorial-managed-virtual-network-on-premise-sql-server.md).
+To access on-premises data sources from managed virtual network using Private Endpoint, please see this tutorial [How to access on-premises SQL Server from Data Factory Managed VNET using Private Endpoint](tutorial-managed-virtual-network-on-premise-sql-server.md).
 
-### Azure Data Factory managed Virtual Network is available in the following Azure regions
-Generally, managed Virtual network is available to all Azure Data Factory regions, except:
+### Azure Data Factory managed virtual network is available in the following Azure regions
+Generally, managed virtual network is available to all Azure Data Factory regions, except:
 - South India
 
 
-### Outbound communications through public endpoint from ADF Managed Virtual Network
+### Outbound communications through public endpoint from ADF managed virtual network
 - All ports are opened for outbound communications.
 
 ### Linked Service creation of Azure Key Vault 
-- When you create a Linked Service for Azure Key Vault, there is no Azure Integration Runtime reference. So you can't create Private Endpoint during Linked Service creation of Azure Key Vault. But when you create Linked Service for data stores which references Azure Key Vault Linked Service and this Linked Service references Azure Integration Runtime with Managed Virtual Network enabled, then you are able to create a Private Endpoint for the Azure Key Vault Linked Service during the creation. 
+- When you create a Linked Service for Azure Key Vault, there is no Azure Integration Runtime reference. So you can't create Private Endpoint during Linked Service creation of Azure Key Vault. But when you create Linked Service for data stores which references Azure Key Vault Linked Service and this Linked Service references Azure Integration Runtime with managed virtual network enabled, then you are able to create a Private Endpoint for the Azure Key Vault Linked Service during the creation. 
 - **Test connection** operation for Linked Service of Azure Key Vault only validates the URL format, but doesn't do any network operation.
 - The column **Using private endpoint** is always shown as blank even if you create Private Endpoint for Azure Key Vault.
 
@@ -180,5 +180,5 @@ Generally, managed Virtual network is available to all Azure Data Factory region
 
 ## Next steps
 
-- Tutorial: [Build a copy pipeline using managed Virtual Network and private endpoints](tutorial-copy-data-portal-private.md) 
-- Tutorial: [Build mapping dataflow pipeline using managed Virtual Network and private endpoints](tutorial-data-flow-private.md)
+- Tutorial: [Build a copy pipeline using managed virtual network and private endpoints](tutorial-copy-data-portal-private.md) 
+- Tutorial: [Build mapping dataflow pipeline using managed virtual network and private endpoints](tutorial-data-flow-private.md)