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

Orion Edwards 81

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:

 {
     &#34;error&#34;: {
         &#34;code&#34;: &#34;InvalidGatewayHost&#34;,
         &#34;message&#34;: &#34;Host name resolution failed for &#39;Microsoft.Network&#39;; cannot fulfill the request.&#34;
     }
 }

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

Hans Bakker 107 Reputation points

2020-06-04T11:21:23.503+00:00

I am experiencing the same
Graham Cross 11 Reputation points

2020-06-04T11:23:03.997+00:00

I am experiencing the exact same issue as you, I have never experienced this problem before. It could be a problem with Azure right now.
Ajay Kumar Jha 1 Reputation point

2020-06-04T11:23:54.807+00:00

We are also facing the same issue here.
Mike Martin 1 Reputation point

2020-06-04T11:24:03.377+00:00

^ Same here, getting this error when trying to create VM's in the UK South region via Azure Databricks.

As is often the case "Service Health" in Azure portal shows no issues
Nagamunindra Nelapati 6 Reputation points

2020-06-04T11:30:21.733+00:00

Facing the same issue
Chris M 6 Reputation points

2020-06-04T11:33:04.79+00:00

It's now appearing in the portal listed as an "emerging issue under investigation".

Not only is it affecting resource creation, but also appears to affect changes to vnets... Some of the changes are going through even though errors are shown, some aren't.
Killer 1 Reputation point

2020-06-04T11:38:42.45+00:00

EXPERIENCING same issue
SmokeyTheBear 1 Reputation point

2020-06-04T11:39:25.417+00:00

Dunno what you guys are talking about ... Works fine for me on Amazon AWS ¯_(ツ)_/¯.
Microsoft_Azure_userSW 1 Reputation point

2020-06-04T11:58:11.15+00:00

Hi, also experiencing this, do we know when this is likely to be resolved please?
Abin [MSFT] 1 Reputation point

2020-06-04T12:10:39.43+00:00

Facing this issue.
Elijah B 1 Reputation point

2020-06-04T12:57:44.89+00:00

Had the same issue, although i seemed to be able to get past it in the East US by using an old NSG that already existed but wasnt being used. Not the ideal soloution, but im at least past that point in the deployment.
Cedersved 16 Reputation points

2020-06-04T13:13:58.567+00:00

It also seems to affect data flow execution in azure data factory v2, as they fail with error code 4501 unable to fetch execution state since a few hours back
Cedersved 16 Reputation points

2020-06-04T13:34:57.55+00:00

Your comment is here. You have to click 'show more'
Matt Cummings 1 Reputation point

2020-06-04T15:16:13.54+00:00

Has this resolved for anyone yet? As of 11:15, US East Coast time, I'm still having the issue.

Accepted answer

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
Please sign in to rate this answer.

5 people found this answer helpful.
Orion Edwards 81 Reputation points

2020-06-04T11:50:56.677+00:00

Thanks! I had checked the status page earlier and it was showing all green. Looks like I was just one of the unlucky early-adopters of this bug

Orion Edwards 81 Reputation points

2020-06-04T21:27:27.35+00:00

Confirm everything is all working now
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

20 additional answers

_Admin Azure 11 Reputation points

2020-06-04T14:07:04.777+00:00

I have been lossing much time during the morning trying to deploy new virtual machines... Now I see that is a global issue....
Azure should comunicated this things to all their users inmediatlly....
Please sign in to rate this answer.

2 people found this answer helpful.
Hitesh Kacholiya 11 Reputation points

2020-06-04T14:41:50.937+00:00

Totally Agreed. There was no notification from Azure and we ended up wasting lot of time trying to figure out the issue.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Graham Cross 11 Reputation points

2020-06-04T11:52:32.417+00:00

It's definitely a service issue, as someone else has already posted:
Azure Resource Manager (ARM) - Multiple regions - Investigating
Starting at 08:45 UTC on 04 Jun 2020, some customers may experience issues with resource creation for services that depend on the Azure Resource Manager (ARM) platform. We are aware of this issue and are actively investigating. The next update will be provided in 60 minutes, or as events warrant.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Lloyd Smart 1 Reputation point

2020-06-04T12:18:56.327+00:00

Having the same issue. Can't create peerings between vnets. Seeing it on North EU and West EU.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Mohan Perera 1 Reputation point

2020-06-04T12:24:39.657+00:00

I was trying to create windows VM and not able to create and getting the error as
{
"error": {
"code": "InvalidGatewayHost",
"message": "Host name resolution failed for 'Microsoft.Network'; cannot fulfill the request."
}
}

Tried in Central and East Australia, both the regions having issues.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

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

20 additional answers

Your answer