resource provider note and acrolinx updates

Author: madsd

articles/app-service/configure-vnet-integration-enable.md

@@ -5,27 +5,24 @@ keywords: vnet integration
 author: madsd
 ms.author: madsd
 ms.topic: how-to
-ms.date: 10/20/2021
+ms.date: 02/13/2023
 ms.tool: azure-cli, azure-powershell
 ---
 
 # Enable virtual network integration in Azure App Service
 
-Through integrating with an Azure virtual network (VNet) from your [Azure App Service app](./overview.md), you can reach private resources from your app within the virtual network. The VNet integration feature has two variations:
-
-* **Regional virtual network integration**: Connect to Azure virtual networks in the same region. You must have a dedicated subnet in the virtual network you're integrating with.
-* **Gateway-required virtual network integration**: When you connect directly to a virtual network in other regions or to a classic virtual network in the same region, you must use gateway-required virtual network integration.
-
-This article describes how to set up regional virtual network integration.
+Through integrating with an Azure virtual network from your [Azure App Service app](./overview.md), you can reach private resources from your app within the virtual network.
 
 ## Prerequisites
 
-The VNet integration feature requires:
+The virtual network integration feature requires:
 
 - An App Service pricing tier [that supports virtual network integration](./overview-vnet-integration.md).
 - A virtual network in the same region with an empty subnet.
 
-The subnet must be delegated to Microsoft.Web/serverFarms. If the delegation isn't done before integration, the provisioning process will configure this delegation. The subnet must be allocated an IPv4 `/28` block (16 addresses). We recommend that you have a minimum of 64 addresses (IPv4 `/26` block) to allow for maximum horizontal scale.
+The subnet must be delegated to Microsoft.Web/serverFarms. If the delegation isn't done before integration, the provisioning process configures this delegation. The subnet must be allocated an IPv4 `/28` block (16 addresses). We recommend that you have a minimum of 64 addresses (IPv4 `/26` block) to allow for maximum horizontal scale.
+
+If the virtual network is in a different subscription than the app, you must ensure that the subscription with the virtual network is registered for the `Microsoft.Web` resource provider. You can explicitly register the provider [by following this documentation](../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider), but it is automatically registered when creating the first web app in a subscription.
 
 ## Configure in the Azure portal
 
@@ -39,7 +36,7 @@ The subnet must be delegated to Microsoft.Web/serverFarms. If the delegation isn
 
     :::image type="content" source="./media/configure-vnet-integration-enable/vnetint-add-vnet.png" alt-text="Screenshot that shows selecting the virtual network.":::
 
-During the integration, your app is restarted. When integration is finished, you'll see details on the virtual network you're integrated with.
+During the integration, your app is restarted. When integration is finished, you see details on the virtual network you're integrated with.
 
 ## Configure with the Azure CLI
 
@@ -50,7 +47,7 @@ az webapp vnet-integration add --resource-group <group-name> --name <app-name> -
 ```
 
 > [!NOTE]
-> The command checks if the subnet is delegated to Microsoft.Web/serverFarms and applies the necessary delegation if it isn't configured. If the subnet was configured, and you don't have permissions to check it, or if the virtual network is in another subscription, you can use the *--skip-delegation-check* parameter to bypass the validation.
+> The command checks if the subnet is delegated to Microsoft.Web/serverFarms and applies the necessary delegation if it isn't configured. If the subnet was configured, and you don't have permissions to check it, or if the virtual network is in another subscription, you can use the `--skip-delegation-check` parameter to bypass the validation.
 
 ## Configure with Azure PowerShell
 
@@ -83,7 +80,7 @@ $subnet = Add-AzDelegation -Name "myDelegation" -ServiceName "Microsoft.Web/serv
 Set-AzVirtualNetwork -VirtualNetwork $vnet
 ```
 
-Configure VNet Integration.
+Configure virtual network integration.
 
 > [!NOTE]
 > If the webapp is in another subscription than virtual network, you can use the *Set-AzContext -Subscription "xxxx-xxxx-xxxx-xxxx"* command to set the current subscription context. Set the current subscription context to the subscription where the web app was deployed.