I am failing to deploy the VPN Gateway Globally showing error Persistent Global AnotherOperationInProgress Lock preventing the creation of a Virtual Network Gateway

The error message "Persistent Global AnotherOperationInProgress Lock preventing the creation of a Virtual Network Gateway" typically indicates that there is an ongoing operation in the Azure environment that is preventing the deployment of the VPN Gateway. Here are some steps you can take to troubleshoot and resolve this issue:

1. Check for Ongoing Operations: Go to the Azure portal and check if there are any ongoing operations related to the resource group or the specific region where you are trying to deploy the VPN Gateway. Sometimes, other deployments or operations can cause this lock.
2. Wait for Previous Operations to Complete: If there are ongoing operations, you may need to wait for them to complete. This can take some time, depending on what is being deployed or modified.
3. Resource Locks: Ensure that there are no resource locks applied to the resource group or the specific resources that might be causing the lock. You can check this in the Azure portal under the resource group's settings.
4. Retry Deployment: After confirming that there are no ongoing operations or locks, try to redeploy the VPN Gateway. Sometimes, a simple retry can resolve transient issues.
5. Contact Support: If the issue persists after trying the above steps, consider reaching out to Azure support for further assistance. They can provide more detailed insights into the specific operations that are causing the lock.

By following these steps, you should be able to resolve the issue and successfully deploy your VPN Gateway.

Hi @ GCI Admin-Hasan

It sounds like you're having a frustrating time trying to deploy the Virtual Network Gateway (VNG) and encountering the error regarding the "AnotherOperationInProgress Lock." This typically means there's an ongoing operation on the resource that is preventing further modifications.

Here are some steps you can try to resolve this issue:

1. Check Existing Operations: First, ensure there are no ongoing or hung operations for the Virtual Network Gateway. You can do this by reviewing the activity logs in the Azure Portal for the particular resource.
2. Retry Deployment: After confirming there are no active operations, try to redeploy the VNG again. Sometimes, simply retrying the deployment can resolve transient issues.
3. Verify Resource Group and Region: Double-check that your selected Resource Group and the Azure Region support the features you are trying to deploy. Even though you've already changed these, it's important to ensure they meet the requirements.
4. Remove Conflicts: If you have other resources (like existing gateways) in the same resource group or region, make sure they aren't conflicting with your current setup. You may consider deleting any resources that are no longer needed and then trying the deployment again.
5. Use Azure CLI or PowerShell: If the Azure Portal is giving you issues, try using Azure CLI or PowerShell to create the Virtual Network Gateway, which sometimes bypasses issues seen in the GUI.
6. Increasing Timeouts: If the operations take longer than expected, consider increasing the timeout duration in your deployment settings.
7. Azure Support: If you've tried the above and the issue persists, it might be worth opening an Azure support ticket for further assistance.

Hope this helps you get the VPN Gateway deployed! If you have any more questions or need further assistance, feel free to ask.

References:

• Create a VPN gateway
• VPN Gateway FAQ
• Azure Activity Logs

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.