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

Orion Edwards 81 Reputation points
2020-06-04T11:09:56.58+00:00

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

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,139 questions
{count} votes

Accepted answer
  1. Hans Bakker 107 Reputation points
    2020-06-04T11:22:52.217+00:00

    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

    5 people found this answer helpful.

20 additional answers

Sort by: Most helpful
  1. Tapan Barman 1 Reputation point
    2020-06-04T12:26:28.033+00:00

    9131-screenshot-from-2020-06-04-16-20-00.png

    Also happening in South Asia

    0 comments No comments

  2. Hitesh Kacholiya 11 Reputation points
    2020-06-04T12:28:23.733+00:00

    We are also facing similar issues while trying to create NSGs or trying to update existing rules in NSGs.

    Below is the error that we get: Error: Host name resolution failed for 'Microsoft.Network'; cannot fulfill the request.

    We are trying this in West Europe Region.

    Thanks
    Hitesh Kacholiya

    0 comments No comments

  3. Anonymous
    2020-06-04T12:41:05.78+00:00

    having same issue while creating the NSG rules in West Europe region

    "
    Error waiting for completion of Network Security Rule "xxxxx" (NSG "xxx-nsg" / Resource Group "xx-xx-rg"): Future#WaitForCompletion: the number of retries has been exceeded: StatusCode=502 -- Original Error: Code="InvalidGatewayHost" Message="Host name resolution failed for 'Microsoft.Network'; cannot fulfill the request."

    "

    0 comments No comments

  4. Pablo Abbate 6 Reputation points
    2020-06-04T12:43:01.447+00:00

    Same issue creating a aks cluster:

    Deployment failed. Correlation ID: 90938824-e055-489c-b6ee-6cc8a4f4322c. Reconcile standard load balancer failed. Details: standardLoadBalancerReconciler retry failed: Future#WaitForCompletion: the number of retries has been exceeded: StatusCode=502 -- Original Error: Code="InvalidGatewayHost" Message="Host name resolution failed for 'Microsoft.Network'; cannot fulfill the request.".

    0 comments No comments