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

I am experiencing the exact same issue

Resource Type Status Operation details
VirtNet2 Microsoft.Network/VirtualNetworks BadGateway Operation details
{
"error": {
"code": "InvalidGatewayHost",
"message": "Host name resolution failed for 'Microsoft.Network'; cannot fulfill the request."
}
}

Answer 3

Same issue in West and North Europe.

Original Error: Code="InvalidGatewayHost" Message="Host name resolution failed for 'Microsoft.Network'; cannot fulfill the request.

Answer 4

Facing a similar issue, is there any further update on this(any idea if there is a tracker where we can monitor this update so that we can get to know if the issue is resolved)

cheers

Answer 5

Hi,

You can also follow along on the official Azure Support twitter account:
https://twitter.com/AzureSupport/status/1268504676489666560

and over at the Azure Portal:
https://portal.azure.com/#blade/Microsoft_Azure_Health/AzureHealthBrowseBlade/serviceIssues

Best regards,
Leon