Can't create Azure virtual machines: Network deployment stuck with BadGateway status

Question

I've tried about half a dozen times so far to create a windows server virtual machine across multiple different regions (US East 2, Australia East, Australia SouthEast) using multiple different instance types (DS2_v2, DS3_v2).

All appear to be stuck deploying network related resources.

Example:

Resource            Type                                  Status   
ccdev840vnet209     Microsoft.Network/virtualNetworks     BadGateway 

Operation ID: /subscriptions/e55d8cbb-12c6-4ac2-ae7d-241a20dc3931/resourceGroups/cc-dev-840/providers/Microsoft.Resources/deployments/CreateVm-MicrosoftWindowsServer.WindowsServer-201-20200604222821/operations/98463F00074BA2CE

Operation name: 98463F00074BA2CE

Provisioning operation: Create

Provisioning state: Running

Timestamp: 6/4/2020, 10:59:52 PM

Duration: 30 minutes 21 seconds

Tracking ID: 7921864c-492d-412b-9dcf-3ce65e76781d

Status: BadGateway

Status message:

 {
     "error": {
         "code": "InvalidGatewayHost",
         "message": "Host name resolution failed for 'Microsoft.Network'; cannot fulfill the request."
     }
 }

Type: Microsoft.Network/virtualNetworks

Resource ID: /subscriptions/e55d8cbb-12c6-4ac2-ae7d-241a20dc3931/resourceGroups/cc-dev-840/providers/Microsoft.Network/virtualNetworks/ccdev840vnet209

Resource: ccdev840vnet209

Is Azure broken? How can I resolve this? I've just followed the standard VM creation wizard using default options

Answer 1

Azure Status (https://status.azure.com/en-us/status) says:

Multiple regions - Investigating

Starting at 08:45 UTC on 04 Jun 2020, customers may experience issues with resource creation. We are aware of this issue and are actively investigating. The next update will be provided in 60 minutes, or as events warrant.

This message was last updated at 11:09 UTC on 04 June 2020

Answer 2

Same here in France Central, trying to update a Web Application Firewall :

Failed to save application gateway changes
Failed to save configuration changes to application gateway 'xxxxxxxx'. Error: Host name resolution failed for 'Microsoft.Network'; cannot fulfill the request.

Regards

Answer 3

I have the same issue when trying to add application rule in appgatewayV2

Answer 4

same issue configuring cosmos db networking

Answer 5

I 1st wrote this as a comment, but i dont see it anywhere, i was able to move past this and deploy a VM by using a Network Security group that existed already but was not in use. this may work for some in a situation like mine where i am testing deployments, and not others who need a new group. But i was able to get my VM Deployed and running by using an existing group.