Azure Virtual WAN
An Azure virtual networking service that provides optimized and automated branch-to-branch connectivity.
225 questions
Unable to delete an Azure Virtual WAN, after NVA has been deleted in the Hub
Jesper Hald
0
Reputation points
I have testet Azure Virtual WAN, deploying the following resources:
- Azure Virtual WAN
- West Europe Hub
- Fortigate NVA inside the Hub
When I tried to delete the Azure Virtual WAN resource, the NVA was removed completely - as far as I can see - but Azure Virtual WAN fails on Hub deletion with a reference to the NVA resource that no longer exists.
I have tried to:
- Reset the hub
- Redeploy the NVA (this fails, with reference to the non existing NVA)
Also, I have made sure that the Routing Intent was deleted first.
The Support + Troubleshooting insists that I have no errors.
I am not really sure where to go from here - I am using my Visual Studio Subscription, so I am running out of credits fast, which kind of limits what I am able to do.
Any help will be appriciated.
Azure Virtual WAN
Azure
Azure
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
1,014 questions
{count} votes
-
William Nieto 535 Reputation points2024-06-03T12:05:07.5933333+00:00 It sounds like you're encountering a common issue with resource dependencies and deletion in Azure Virtual WAN. Here are some steps and tips that might help you resolve this problem:
Network virtual appliance issues in Azure
Step-by-Step Troubleshooting:
Check Resource Locks:
- Ensure there are no resource locks on the Azure Virtual WAN or associated resources. Resource locks can prevent deletion.
Review Dependencies:
- Double-check if there are any lingering dependencies or references to the NVA (Network Virtual Appliance). Sometimes, even if the NVA appears deleted, there might be hidden dependencies. **Use Azure Resource Graph**: - Use Azure Resource Graph to query resources and identify any lingering references to the NVA. - Example Query: ```sql kustoCopy code Resources| where type == 'Microsoft.Network/virtualWANs' | project id, name, properties ```
**Manually Remove Resource References**: - Try to manually edit and remove any lingering references to the NVA in the Virtual WAN settings via the Azure portal or Azure CLI. **Force Deletion via Azure CLI**: - Use Azure CLI to force delete the Azure Virtual WAN and its resources. - Example command: ```yaml bashCopy code az network vwan delete --name <YourVirtualWANName> --resource-group <YourResourceGroupName> -- ``` **Check for Pending Operations**: - Ensure there are no pending operations on the Azure Virtual WAN or Hub. You can check this in the Activity Log in the Azure portal. **Redeploy with Correct Configuration**: - If deletion fails due to a configuration issue, redeploy the NVA with the exact previous configuration, and then try deleting the Virtual WAN and Hub again.Advanced Steps:
Azure Support Ticket:
- If you haven't already, consider raising a support ticket with Azure Support. Provide them with detailed logs and the steps you've taken. Sometimes, support can perform backend operations to resolve such issues.
Resource Group Deletion:
- As a last resort, if you don't have any other critical resources in the same resource group, you can try deleting the entire resource group. This will force the deletion of all resources within it. - Example command: ```yaml bashCopy code az group delete --name <YourResourceGroupName> -- ```Monitoring and Cost Management:
Given that you're running out of credits, it’s crucial to monitor and manage your Azure spending:
- Set Up Budgets and Alerts:
- Use Azure Cost Management + Billing to set up budgets and alerts to avoid unexpected charges.
- Optimize Resource Usage:
- Ensure that you only deploy necessary resources and deallocate any that are not in use.
Additional Tips:
- Azure Documentation and Community Forums:
- Refer to the Azure documentation for Virtual WAN and related resources for any specific guidance on deletion issues.
- Explore community forums like Microsoft Q&A and Stack Overflow for similar issues faced by others and potential solutions.
- Refer to the Azure documentation for Virtual WAN and related resources for any specific guidance on deletion issues.
By following these steps, you should be able to identify and resolve the issue preventing the deletion of your Azure Virtual WAN and associated resources. If the problem persists, reaching out to Azure Support with detailed information is the best course of action.It sounds like you're encountering a common issue with resource dependencies and deletion in Azure Virtual WAN. Here are some steps and tips that might help you resolve this problem:
Step-by-Step Troubleshooting:
Check Resource Locks:
- Ensure there are no resource locks on the Azure Virtual WAN or associated resources. Resource locks can prevent deletion.
Review Dependencies:
- Double-check if there are any lingering dependencies or references to the NVA (Network Virtual Appliance). Sometimes, even if the NVA appears deleted, there might be hidden dependencies. **Use Azure Resource Graph**: - Use Azure Resource Graph to query resources and identify any lingering references to the NVA. - Example Query: ```sql kustoCopy code Resources| where type == 'Microsoft.Network/virtualWANs' | project id, name, properties ```
**Manually Remove Resource References**: - Try to manually edit and remove any lingering references to the NVA in the Virtual WAN settings via the Azure portal or Azure CLI. **Force Deletion via Azure CLI**: - Use Azure CLI to force delete the Azure Virtual WAN and its resources. - Example command: ```yaml bashCopy code az network vwan delete --name <YourVirtualWANName> --resource-group <YourResourceGroupName> -- ``` **Check for Pending Operations**: - Ensure there are no pending operations on the Azure Virtual WAN or Hub. You can check this in the Activity Log in the Azure portal. **Redeploy with Correct Configuration**: - If deletion fails due to a configuration issue, redeploy the NVA with the exact previous configuration, and then try deleting the Virtual WAN and Hub again.Advanced Steps:
Azure Support Ticket:
- If you haven't already, consider raising a support ticket with Azure Support. Provide them with detailed logs and the steps you've taken. Sometimes, support can perform backend operations to resolve such issues.
Resource Group Deletion:
- As a last resort, if you don't have any other critical resources in the same resource group, you can try deleting the entire resource group. This will force the deletion of all resources within it. - Example command: ```yaml bashCopy code az group delete --name <YourResourceGroupName> -- ```Monitoring and Cost Management:
Given that you're running out of credits, it’s crucial to monitor and manage your Azure spending:
- Set Up Budgets and Alerts:
- Use Azure Cost Management + Billing to set up budgets and alerts to avoid unexpected charges.
- Optimize Resource Usage:
- Ensure that you only deploy necessary resources and deallocate any that are not in use.
By following these steps, you should be able to identify and resolve the issue preventing the deletion of your Azure Virtual WAN and associated resources.
-
KapilAnanth-MSFT 46,776 Reputation points Microsoft Employee2024-06-04T05:30:05.84+00:00 Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you are unable to delete a virtual WAN.
- Can you please share the exact error message you are receiving?
- Did you try the Azure CLI Command : az resource delete
- Or Powershell : Remove-AzResource
Cheers,
Kapil
Sign in to comment
Sign in to answer