Merge pull request #272330 from wtnlee/updateNVADelete

Update nva delete

Author: v-dirichards

includes/virtual-wan-nva-hub-faq.md

@@ -5,7 +5,7 @@
  ms.date: 04/19/2022
  ms.author: cherylmc
 ---
-### I'm a network appliance partner and want to get our NVA in the hub. Can I join this partner program?
+### I'm a network virtual appliance (NVA) partner and want to get our NVA in the hub. Can I join this partner program?
 
 Unfortunately, we don't have capacity to on-board any new partner offers at this time. Check back with us at a later date!
 
@@ -15,19 +15,19 @@ Only partners listed in the [Partners](../articles/virtual-wan/about-nva-hub.md#
 
 ### What is the cost of the NVA?
 
-You must purchase a license for the NVA from the NVA vendor. Bring-your-own license (BYOL) is the only licensing model supported today. In addition, you'll also incur charges from Microsoft for the NVA Infrastructure Units you consume, and any other resources you use. For more information, see [Pricing concepts](../articles/virtual-wan/pricing-concepts.md).
+You must purchase a license for the NVA from the NVA vendor. Bring-your-own license (BYOL) is the only licensing model supported today. In addition, Microsoft charges for the NVA Infrastructure Units you consume, and any other resources you use. For more information, see [Pricing concepts](../articles/virtual-wan/pricing-concepts.md).
 
 ### Can I deploy an NVA to a Basic hub?
 
-No. You must use a Standard hub if you want to deploy an NVA.
+No, you must use a Standard hub if you want to deploy an NVA.
 
 ### Can I deploy an NVA into a Secure hub?
 
 Yes. Partner NVAs can be deployed into a hub with Azure Firewall.
 
-### Can I connect any CPE device in my branch office to my NVA in the hub?
+### Can I connect any device in my branch office to my NVA in the hub?
 
-No. Barracuda CloudGen WAN is only compatible with Barracuda CPE devices. To learn more about CloudGen WAN requirements, see [Barracuda's CloudGen WAN page](https://www.barracuda.com/products/cloudgenwan). For Cisco, there are several SD-WAN CPE devices that are compatible. See [Cisco Cloud OnRamp for Multi-Cloud](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/ios-xe-17/cloud-onramp-book-xe/cloud-onramp-multi-cloud.html#Cisco_Concept.dita_c61e0e7a-fff8-4080-afee-47b81e8df701) documentation for compatible CPEs. Reach out to your provider with any questions.
+No,  Barracuda CloudGen WAN is only compatible with Barracuda edge devices. To learn more about CloudGen WAN requirements, see [Barracuda's CloudGen WAN page](https://www.barracuda.com/products/cloudgenwan). For Cisco, there are several SD-WAN devices that are compatible. See [Cisco Cloud OnRamp for Multi-Cloud](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/ios-xe-17/cloud-onramp-book-xe/cloud-onramp-multi-cloud.html#Cisco_Concept.dita_c61e0e7a-fff8-4080-afee-47b81e8df701) documentation for compatible devices. Reach out to your provider with any questions.
 
 ### What routing scenarios are supported with NVA in the hub?
 
@@ -39,20 +39,32 @@ For supported regions, see [NVA supported regions](../articles/virtual-wan/about
 
 ### How do I delete my NVA in the hub?
 
-If the Network Virtual Appliance resource was deployed via a Managed Application, delete the Managed Application. This will automatically delete the Managed Resource Group and associated Network Virtual Appliance resource.
+If the Network Virtual Appliance resource was deployed via a Managed Application, delete the Managed Application. Deleting the Managed Application automatically deletes the Managed Resource Group and associated Network Virtual Appliance resource.
 
-Note that you cannot delete a NVA that is the next hop resource for a Routing Policy. To delete the NVA, first delete the Routing Policy. 
+You can't delete an NVA that is the next hop resource for a Routing Policy. To delete the NVA, first delete the Routing Policy.
 
-If the Network Virtual Appliance resource was deployed via partner orchestration software, please reference partner documentation to delete the Network Virtual Appliance.
+If the Network Virtual Appliance resource was deployed via partner orchestration software, reference partner documentation to delete the Network Virtual Appliance.
 
-Alternatively, you can run the following Powershell command to delete your Network Virtual Appliance. 
+Alternatively, you can run the following PowerShell command to delete your Network Virtual Appliance.
 
+1. Find the Azure resource group of the NVA you want to delete. The Azure resource group is usually **different** than the resource group  the Virtual WAN hub is deployed in. Ensure the  Virtual Hub property of the NVA resource corresponds to the NVA you want to delete. The following example assumes that all NVAs in your subscription have distinct names. If there are multiple NVAs with the same name, make sure you collect the information associated with the NVA you want to delete.  
+
+    ```azurepowershell-interactive
+    $nva = Get-AzNetworkVirtualAppliance -Name <NVA name>
+    $nva.VirtualHub
+    ```  
+2. Delete the NVA.
    ```azurepowershell-interactive
-   Remove-AzNetworkVirtualAppliance -Name <NVA name> -ResourceGroupName <resource group name>
+   Remove-AzNetworkVirtualAppliance -Name $nva.Name -ResourceGroupName $nva.ResourceGroupName
    ```
 
-The same command can also be run from CLI. 
+The same series of steps can be executed from Azure CLI.
 
+1. Find the Azure resource group of the NVA you want to delete.  The Azure resource group is usually **different** than the resource group  the Virtual WAN hub is deployed in. Ensure the  Virtual Hub property of the NVA resource corresponds to the NVA you want to delete. 
+   ```azurecli-interactive
+    az network virtual-appliance list
+   ```
+2. Delete the NVA
    ```azurecli-interactive
-az network virtual-appliance delete --subscription <subscription name> --resource-group <resource group name> --name <Network Virtual Appliance name>
+    az network virtual-appliance delete --subscription <subscription name> --resource-group <resource group name> --name <NVA name>
    ```