Virtual network not showing up in drop-down menu when creating a VM in Azure Portal

Question

Virtual network not showing up in drop-down menu when creating a VM in Azure Portal

Asad 16

Hello, I'm currently working through Learn Azure in a Month of Lunches and am on section 8.2 where I have to create and configure VMs with a load balancer that was created earlier in the chapter. The section provides some Azure CLI commands to use to make the VMs, but due to the current issue regarding that command I'm not able to run them. I was using the Cloud Shell to run the commands, so I decided to just make the VMs in the portal instead.

However, when I try to make the VMs in the portal, the virtual network that I created isn't showing up in the Networking tab. I'm creating the VM in the same region as my virtual network, and am also making it in the same resource group. Interestingly, when I make a virtual network through the portal in a different region, and then create a VM and set it to that same region, it then shows up in the drop-down menu. I made the virtual network that I need to use with Azure CLI commands that were given in the book, but I'm not understanding why that would make it so that it wouldn't show up when making a VM in the portal.

I know I could just get the Azure CLI on my local machine and then run the commands from there due to the hotfix that was released, but I want to understand why this isn't working from the portal.

Can anyone help me with this? Thanks.

Andreas Baumgarten 123.4K Reputation points MVP Volunteer Moderator

2022-02-15T19:04:56.087+00:00

Hi @Asad ,

without seeing the details it's hard to help.

Maybe you can post some screenshots of the vNet/subnet configuration in the portal and also the details of the VM configuration during creation.

----------

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten
Ravi Kanth Koppala 3,391 Reputation points Microsoft Employee Moderator

2022-02-21T17:38:37.093+00:00

@Asad ,
Just checking in to see if you got a chance to see the suggested response below. If the suggested response helped you, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Thanks.
Harshvardhan Saini 36 Reputation points

2022-04-07T12:09:05.077+00:00

Hi.. This is April 22 but this issue still haunting many users including me. The same issue occurs (VNet not visible in the dropdown) when I try to create the application gateway. Please fix this issue.

Thanks & Regards,
Harsh
KrishnanduB 1 Reputation point

2022-04-08T18:41:26.193+00:00

I am facing similar issue, I have created Virtual Networks and afterwards I am trying to deploy a VM in the same Resource Group as the VNets, those existing VNets are not showing down in the drop-down list.
Both VMs and VNets belongs to the same region i.e., East-US 2
Ahamed N 16 Reputation points

2022-04-14T08:11:06.46+00:00

Hi..

Adding this update on 14th Apr'22.

Still the problem is not resolved and its not showing any of my subnets from my VNet. Will someone from Microsoft can fix it ASAP?
Bryan Ohana 1 Reputation point

2022-05-26T08:49:21.507+00:00

Hi Everyone, I experience the same issue, does anyone has a solution ?
Ryan Eschete 6 Reputation points

2022-05-27T16:21:53.9+00:00

II've been toying with this for a few days now. I figured out the issue. Your browser is caching possibly old info. Open a new browser or delete cache/internet history and look for your new vm
Ryan Eschete 6 Reputation points

2022-05-27T16:22:15.72+00:00

virtual nework
Eddie 16 Reputation points

2022-10-28T22:24:25.677+00:00

This may be caused by accidentally creating a Virtual Network (Classic). It seems that classic virtual networks cannot be managed the same way as Virtual Networks and don't appear in resource groups*.

To allow it to appear you need convert the Virtual Network (Classic) by viewing the resource and choosing the "Migration to ARM" option on the left side of the page - if you've got nothing using that network just follow the prompts and it should be converted in no time.

I think the cause of this confusion is that the Create a Resource > Virtual Network screen defaults (or it did for me) to "Deploy with Classic" rather then "Deploy with Resource Manager" (which seems like a better default)

*Some detail of the differences between Virtual Network Classic and Virtual Network in Azure - https://stackoverflow.com/questions/58756340/what-is-the-difference-between-virtual-network-classic-and-virtual-network-in

Hopefully this help fix the issue for you? It came up for me when working through the Learn Azure in a Month of Lunches book, in chapter 5.
Michael Zendan 0 Reputation points

2023-01-20T15:58:45.1233333+00:00

THIS IS STILL HAPPENING
Emre Ates 0 Reputation points

2023-01-20T15:59:29.58+00:00

Hello,

I am also facing the same problem on multiple services. The latest case was the creation of an application gateway. The virtual networks are not being listed. Hope to get a fix soon.

Cheers
nakul 15 Reputation points

2023-01-23T02:23:24.53+00:00

Hi..

Adding this update on 23rd Jan 23.

Still the problem is not resolved and VNet is not showing. while Vnet got created with 1st vm but for 2nd vm it is not showing when clicked same region and resource group. when trying to create new Vnet with same name it says the vnet is already present. Will someone from Microsoft can fix it ASAP?
nakul 15 Reputation points

2023-01-23T02:24:50.5033333+00:00

Hi..

Adding this update on 23rd Jan 23.

Still the problem is not resolved and VNet is not showing. while Vnet got created with 1st vm but for 2nd vm it is not showing when clicked same region and resource group. when trying to create new Vnet with same name it says the vnet is already present. Will someone from Microsoft can fix it ASAP?
TSTR_JRNL 0 Reputation points

2023-02-07T09:17:49.4133333+00:00

Same issue creating Virtual Network Gateway?!

When checking VNet Topology, an error showed up that there's No network watcher present in region: northeurope...

Creating one (successfully deployed) does not solve this issue.

I ended up creating a VNet in another region, that seems to work for me.

Cheers.
nba 0 Reputation points

2023-02-09T09:08:16.7833333+00:00

Anyone get a solution to this yet? I'm having the same issues.
IrreLevant 0 Reputation points

2023-02-15T07:50:22.23+00:00

At the moment when a vnet is created by cli its not usable for new VMs at portal. Its not showing up in the dropdown list at vm creation.

If the same vnet is created at portal with same configuration its usable without any problems.

(only tested westeurope)
Mohamed Saadeldin 0 Reputation points

2023-02-20T11:51:06.54+00:00

Still the problem is not resolved and not showing any Vnet in my subscription when trying to create VM.
Christian Laughton 0 Reputation points

2023-02-22T16:09:31.45+00:00

This is still a problem for me also. Vnet's not showing when creating VM's.
David Hanson 0 Reputation points

2023-04-02T20:34:09.2266667+00:00

The VNet shows up from the drop down list for me if I create a new subnet in the portal (GUI) in that same VNet. I was not able to reproduce this unfortunately.
Petri Oikarainen 25 Reputation points

2023-04-15T09:30:27.3566667+00:00

This is issue still persist as of 15-04-2023, but I found a quick workaround. When you create vnets with cli and into specific regions and attempt to create vnet peering, vnets do not show up. If you want vnets created with CLI to show, you need to create a dummy VNET into the same region where your vnets that you want to use, are. This for some reason refreshes the vnet list and VNETs appear in dropdown. Please Microsoft, fix this.
MURGU, DAN 0 Reputation points

2023-08-02T12:29:42.8266667+00:00

If using the portal, you also need to log-off and and log back on after creating the dummy VNET mentioned above.
GitaraniSharma-MSFT 50,021 Reputation points Microsoft Employee Moderator

2023-08-08T14:14:28.3466667+00:00

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<UPDATE>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Hello All,

This Vnet selection issue has re-appeared after a recent code change made in the VM image dropdown portal experience on 21st July, 2023.

Azure Portal Product Group team is aware of this issue and is working on a hotfix.

In the meantime, anyone facing this issue can use the below Azure portal link to get around the issue:

http://portal.azure.com/?feature.canmodifystamps=true&Microsoft_Azure_Compute=flight1

Regards,

Gita
Joe Fulford 101 Reputation points Microsoft Employee

2023-08-08T14:27:02.1833333+00:00

Are you using any global subscription or directory filters which would be hiding the virtual networks?
Tharjalan Jeyaradnam 0 Reputation points

2023-12-16T14:32:22.2566667+00:00

got it
Tomasz Krawczyk 5 Reputation points

2024-04-03T12:26:43.5433333+00:00

Try creating another dummy VNET. After I did that, suddenly the one created in the first place showed up in the dropdown (of course, the dummy VNET was still not visible).

Maybe Azure is only showing the (i-1) oldest elements of the list in the dropdown ;)

5 answers

Your answer

Andreas Baumgarten 123.4K Reputation points MVP Volunteer Moderator

2022-02-15T19:04:56.087+00:00

Hi @Asad ,

without seeing the details it's hard to help.

Maybe you can post some screenshots of the vNet/subnet configuration in the portal and also the details of the VM configuration during creation.

----------

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten
Ravi Kanth Koppala 3,391 Reputation points Microsoft Employee Moderator

2022-02-21T17:38:37.093+00:00

@Asad ,
Just checking in to see if you got a chance to see the suggested response below. If the suggested response helped you, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Thanks.
Harshvardhan Saini 36 Reputation points

2022-04-07T12:09:05.077+00:00

Hi.. This is April 22 but this issue still haunting many users including me. The same issue occurs (VNet not visible in the dropdown) when I try to create the application gateway. Please fix this issue.

Thanks & Regards,
Harsh
KrishnanduB 1 Reputation point

2022-04-08T18:41:26.193+00:00

I am facing similar issue, I have created Virtual Networks and afterwards I am trying to deploy a VM in the same Resource Group as the VNets, those existing VNets are not showing down in the drop-down list.
Both VMs and VNets belongs to the same region i.e., East-US 2
Ahamed N 16 Reputation points

2022-04-14T08:11:06.46+00:00

Hi..

Adding this update on 14th Apr'22.

Still the problem is not resolved and its not showing any of my subnets from my VNet. Will someone from Microsoft can fix it ASAP?
Bryan Ohana 1 Reputation point

2022-05-26T08:49:21.507+00:00

Hi Everyone, I experience the same issue, does anyone has a solution ?
Ryan Eschete 6 Reputation points

2022-05-27T16:21:53.9+00:00

II've been toying with this for a few days now. I figured out the issue. Your browser is caching possibly old info. Open a new browser or delete cache/internet history and look for your new vm
Ryan Eschete 6 Reputation points

2022-05-27T16:22:15.72+00:00

virtual nework
Eddie 16 Reputation points

2022-10-28T22:24:25.677+00:00

This may be caused by accidentally creating a Virtual Network (Classic). It seems that classic virtual networks cannot be managed the same way as Virtual Networks and don't appear in resource groups*.

To allow it to appear you need convert the Virtual Network (Classic) by viewing the resource and choosing the "Migration to ARM" option on the left side of the page - if you've got nothing using that network just follow the prompts and it should be converted in no time.

I think the cause of this confusion is that the Create a Resource > Virtual Network screen defaults (or it did for me) to "Deploy with Classic" rather then "Deploy with Resource Manager" (which seems like a better default)

*Some detail of the differences between Virtual Network Classic and Virtual Network in Azure - https://stackoverflow.com/questions/58756340/what-is-the-difference-between-virtual-network-classic-and-virtual-network-in

Hopefully this help fix the issue for you? It came up for me when working through the Learn Azure in a Month of Lunches book, in chapter 5.
Michael Zendan 0 Reputation points

2023-01-20T15:58:45.1233333+00:00

THIS IS STILL HAPPENING
Emre Ates 0 Reputation points

2023-01-20T15:59:29.58+00:00

Hello,

I am also facing the same problem on multiple services. The latest case was the creation of an application gateway. The virtual networks are not being listed. Hope to get a fix soon.

Cheers
nakul 15 Reputation points

2023-01-23T02:23:24.53+00:00

Hi..

Adding this update on 23rd Jan 23.

Still the problem is not resolved and VNet is not showing. while Vnet got created with 1st vm but for 2nd vm it is not showing when clicked same region and resource group. when trying to create new Vnet with same name it says the vnet is already present. Will someone from Microsoft can fix it ASAP?
nakul 15 Reputation points

2023-01-23T02:24:50.5033333+00:00

Hi..

Adding this update on 23rd Jan 23.

Still the problem is not resolved and VNet is not showing. while Vnet got created with 1st vm but for 2nd vm it is not showing when clicked same region and resource group. when trying to create new Vnet with same name it says the vnet is already present. Will someone from Microsoft can fix it ASAP?
TSTR_JRNL 0 Reputation points

2023-02-07T09:17:49.4133333+00:00

Same issue creating Virtual Network Gateway?!

When checking VNet Topology, an error showed up that there's No network watcher present in region: northeurope...

Creating one (successfully deployed) does not solve this issue.

I ended up creating a VNet in another region, that seems to work for me.

Cheers.
nba 0 Reputation points

2023-02-09T09:08:16.7833333+00:00

Anyone get a solution to this yet? I'm having the same issues.
IrreLevant 0 Reputation points

2023-02-15T07:50:22.23+00:00

At the moment when a vnet is created by cli its not usable for new VMs at portal. Its not showing up in the dropdown list at vm creation.

If the same vnet is created at portal with same configuration its usable without any problems.

(only tested westeurope)
Mohamed Saadeldin 0 Reputation points

2023-02-20T11:51:06.54+00:00

Still the problem is not resolved and not showing any Vnet in my subscription when trying to create VM.
Christian Laughton 0 Reputation points

2023-02-22T16:09:31.45+00:00

This is still a problem for me also. Vnet's not showing when creating VM's.
David Hanson 0 Reputation points

2023-04-02T20:34:09.2266667+00:00

The VNet shows up from the drop down list for me if I create a new subnet in the portal (GUI) in that same VNet. I was not able to reproduce this unfortunately.
Petri Oikarainen 25 Reputation points

2023-04-15T09:30:27.3566667+00:00

This is issue still persist as of 15-04-2023, but I found a quick workaround. When you create vnets with cli and into specific regions and attempt to create vnet peering, vnets do not show up. If you want vnets created with CLI to show, you need to create a dummy VNET into the same region where your vnets that you want to use, are. This for some reason refreshes the vnet list and VNETs appear in dropdown. Please Microsoft, fix this.
MURGU, DAN 0 Reputation points

2023-08-02T12:29:42.8266667+00:00

If using the portal, you also need to log-off and and log back on after creating the dummy VNET mentioned above.
GitaraniSharma-MSFT 50,021 Reputation points Microsoft Employee Moderator

2023-08-08T14:14:28.3466667+00:00

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<UPDATE>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Hello All,

This Vnet selection issue has re-appeared after a recent code change made in the VM image dropdown portal experience on 21st July, 2023.

Azure Portal Product Group team is aware of this issue and is working on a hotfix.

In the meantime, anyone facing this issue can use the below Azure portal link to get around the issue:

http://portal.azure.com/?feature.canmodifystamps=true&Microsoft_Azure_Compute=flight1

Regards,

Gita
Joe Fulford 101 Reputation points Microsoft Employee

2023-08-08T14:27:02.1833333+00:00

Are you using any global subscription or directory filters which would be hiding the virtual networks?
Tharjalan Jeyaradnam 0 Reputation points

2023-12-16T14:32:22.2566667+00:00

got it
Tomasz Krawczyk 5 Reputation points

2024-04-03T12:26:43.5433333+00:00

Try creating another dummy VNET. After I did that, suddenly the one created in the first place showed up in the dropdown (of course, the dummy VNET was still not visible).

Maybe Azure is only showing the (i-1) oldest elements of the list in the dropdown ;)

Answer 1

bvn prasad 5

I faced same issue yesterday while creating a Global Network peering.

Steps done: -

Configured VM with East US. Did not faced any issue.

Configured VM in West US, where i am unable to find the Virtual Network in West US.

Tried two to three times, but still faced same issue.

I am able to find a workaround for this issue.

Go to Network Interfaces section.
Create a Network interface with the respective Resource Group and Respective Virtual Network which we are facing issue in.
Create a Network Interface.
Now try creating the Virtual Machine, you will get the VNet in the dropdown which was not available before.

Brandon Gómez 0 Reputation points

2024-10-25T03:01:28.37+00:00

It didn't work for me...

Answer 2

Hey Andreas, I actually ended up getting the Azure CLI on my local machine and created the VMs fine from there (I then proceeded to run into issues SSHing into the VM I wanted to get into but that's another issue I think). I'm on the next chapter in the book now and have deleted the resource group I was using, but I may come back to the chapter later on and try it again and see if it works. I'm trying to get through the book while my free credits are still available so yeah, I didn't want to spend too much time on this. If it doesn't work after I come back to it later I might open up another question. Thanks.

Answer 3

Ravi Kanth Koppala 3,391 Microsoft Employee Moderator

@Asad ,
Thank you for reaching out to the Microsoft Q&A platform.

This has been reported by a subset of the customers and our product team identified this issue from the azure portal service side. A fix has been deployed and it should have been mitigated. Please check and let us know if you still see this issue.

----------

Please "Accept as Answer" and Upvote if any of the above helped to help others in the community looking for remediation for similar issues.

Taraka Prabhu 1 Reputation point

2022-10-11T07:44:03.827+00:00

Im still having same problem as of 11/10/2022. Is there a way to mitigate this issue?
KapilAnanth-MSFT 49,536 Reputation points Microsoft Employee Moderator

2022-10-11T17:23:38.547+00:00
Hi @@Asad ,

Currently, we are not aware of any such portal issues.

Can you please try to reproduce this from non-preview portal : https://portal.azure.com/?feature.customportal=false

If the issue persists, can you please share the region(s) in which you are facing this issue?

Can you please confirm if the issue is happening to a particular user or multiple users in your tenant are also facing this?

Cheers,
Kapil
Sam Masih 0 Reputation points

2023-04-01T09:43:54.8866667+00:00

I am also having the issue . I created resources both in India and Australia and can't create VM on the virtual network . How can I use it ?

Answer 4

GitaraniSharma-MSFT 50,021 Microsoft Employee Moderator

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<UPDATE>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Hello All,

This Vnet selection issue has re-appeared after a recent code change made in the VM image dropdown portal experience on 21st July, 2023.

Azure Portal Product Group team is aware of this issue and is working on a hotfix.

In the meantime, anyone facing this issue can use the below Azure portal link to get around the issue:

http://portal.azure.com/?feature.canmodifystamps=true&Microsoft_Azure_Compute=flight1

Regards,

Gita

POWER THOMAS D 0 Reputation points

2023-09-20T05:16:54.0966667+00:00

In my case, I got same problem. I changed the virtaul machine location same to virtaul network, then I fixed the issue.
Clay Brinlee 6 Reputation points

2023-11-01T12:51:59.6333333+00:00

Yay for links that don't work!
Joni Edu Anas 0 Reputation points

2024-02-07T02:07:33.98+00:00
Im currently experiencing this as well as of Feb 7, 2024.

Steps Done:

Created Resource Group

Created VNET

Create Azure Postgresql Flexible Server - Private Access (VNET Integration)

VNET created from step #2 did not show in the drop down.

Using the link from GitaraniSharma-MSFT's answer, the vnet shows properly.
Joni Edu Anas 0 Reputation points

2024-02-07T02:11:28.32+00:00

Hi GitaraniSharma-MSFT, I encountered this issue just recently. Using your link fixed the issue for me. Not sure if the hotfix you mentioned was deployed already, but Id just like to let you know that this is reoccurring as of Feb 7, 2024.
Jan van Zeggelaar 5 Reputation points

2024-07-23T16:33:23.22+00:00

It is now a year later and I'm still experiencing this issue.

Answer 5

CShepherd-Certifications 0

I ran into this issue when trying to create an Azure Firewall within my existing virtual network. I found that it was because the region I had selected initially when attempting to create the firewall (EastUS) was not the same region that my virtual network exists in (EastUS2). I would double check the regions on both the firewall you are trying to create and the virtual network that you have already created, are identical.

Share via

Virtual network not showing up in drop-down menu when creating a VM in Azure Portal

5 answers

Your answer