Unable to select Virtual Network/Subnet when creating VM in Azure Portal

Question

Unable to select Virtual Network/Subnet when creating VM in Azure Portal

Nasser Al-Hadhrami 25

Screenshot 2025-09-10 at 3.40.51 PM copy

Description: When attempting to create virtual machines through the Azure Portal, the Virtual Network and Subnet dropdown menus are not functioning properly. This issue occurs:

Across all Azure regions
For all VM types and sizes
With both existing VNets and when trying to create new ones
The Subnet field shows "The value must not be empty" error
Virtual Network dropdown appears empty or unresponsive

Steps attempted:

Cleared browser cache and cookies
Tried multiple browsers and incognito mode
Verified user permissions (Owner)
Attempted in multiple regions
Refreshed portal multiple times

Expected behavior: Virtual Network dropdown should display existing VNets, and Subnet dropdown should populate after VNet selection.

Impact: Unable to provision new VMs through Azure Portal, blocking deployment workflows.

Alan Kinane 17,356 Reputation points MVP Volunteer Moderator

2025-09-10T12:35:10.65+00:00

Hi, have you given the VM a name on the 'Basics' tab before proceeding to Networking? I've seen this happen if you don't complete the mandatory fields on the first tab 'Basics'. Complete this tab fully and then move on to Disks and then Networking. I suspect it's the Virtual Machine Name that's missing.
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T13:43:35.84+00:00

Yes, I completed all mandatory fields on the Basics tab including VM name. However, I discovered this is a subscription-specific issue.

When I tried the same process in my test lab subscription, it works perfectly fine - all VNet/Subnet dropdowns load normally. The issue only occurs in my production subscription.

Additionally, normally Azure shows field validation errors when you try to proceed to Review + create - but in my case, the process just gets stuck without any error messages, which indicates this isn't a typical field completion issue.

I tried both chrome & firefox latest versions.

I tried to clean all browser history with all caches.

It was working before few weeks, but today we not able to create machines.

we tried from different regions.

we tried from different devices and IP addresses.

This appears to be a subscription-level service problem rather than a user error.
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T14:01:35.0633333+00:00

The issue isn't limited to VM creation - it also occurs when trying to create a standalone NIC card. I can't see existing VNets and cannot create new ones in any networking scenario within this subscription.

This appears to be a subscription-level service problem affecting all networking components.
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T21:52:53.7433333+00:00

Hello Ankit Yadav,

Thank you for reply.

Yes, Azure CLI works perfectly. I successfully created two VMs in East US and North UAE using the same subscription via CLI commands.

We also use Azure Java SDK for automation to create VMs and VNets, which works fine as well.

The issue is portal-specific: when creating VMs, the portal gets stuck at the networking section - can't see existing VNets and no option to create new ones. Even if we manually create a VNet through the portal, it doesn't appear in the VM creation dropdown.

The same issue occurs when creating Network Interface Cards (NICs) - existing VNets are not visible.

This suggests the problem is specifically with the portal during the creation process of NICs and machines.

in the below image, you may notice, i cant see my vnets and no option to create a new one.

but actually, i have many vents in same region.

normally, the portal show button to create a new vnets below virtual network field.

Thank you in advance, and hope to solve this strange issue soon.
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T22:00:33.3+00:00

Hello,

Thank you for reply.

Yes, Azure CLI works perfectly. I successfully created two VMs in East US and North UAE using the same subscription via CLI commands.

We also use Azure Java SDK for automation to create VMs and VNets, which works fine as well.

The issue is portal-specific: when creating VMs, the portal gets stuck at the networking section - can't see existing VNets and no option to create new ones. Even if we manually create a VNet through the portal, it doesn't appear in the VM creation dropdown.

The same issue occurs when creating Network Interface Cards (NICs) - existing VNets are not visible.

This suggests the problem is specifically with the portal during the process of vm or network interface creation.

In below image, it shows that i successfully created machines in two regions.

but when try to create machine or nic using portal, i cant see the list of my existing vnets and no option button to create new one. the issue same when create machine (in network tab)
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T22:04:04.3+00:00

Hello Ankit Yadav,

Thank you for reply.

Yes, Azure CLI works perfectly. I successfully created two VMs in East US and North UAE using the same subscription via CLI commands.

We also use Azure Java SDK for automation to create VMs and VNets, which works fine as well.

The issue is portal-specific: when creating VMs, the portal gets stuck at the networking section - can't see existing VNets and no option to create new ones. Even if we manually create a VNet through the portal, it doesn't appear in the VM creation dropdown.

The same issue occurs when creating Network Interface Cards (NICs) - existing VNets are not visible.

This suggests the problem is specifically with the portal during the process of vm or network interface creation.
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T22:06:41.6333333+00:00

Hello Ankit Yadav,

Thank you for reply.

Yes, Azure CLI works perfectly. I successfully created two VMs in East US and North UAE using the same subscription via CLI commands.

We also use Azure Java SDK for automation to create VMs and VNets, which works fine as well.

The issue is portal-specific: when creating VMs, the portal gets stuck at the networking section - can't see existing VNets and no option to create new ones. Even if we manually create a VNet through the portal, it doesn't appear in the VM creation dropdown.

The same issue occurs when creating Network Interface Cards (NICs) - existing VNets are not visible.

This suggests the problem is specifically with the portal during the process of vm or network interface creation.

In below image, it shows that i successfully created machines in two regions.

but when try to create machine or nic using portal, i cant see the list of my existing vnets and no option button to create new one. the issue same when create machine (in network tab)
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T22:07:27.8733333+00:00

Hello Ankit Yadav,

Thank you for reply.

Yes, Azure CLI works perfectly. I successfully created two VMs in East US and North UAE using the same subscription via CLI commands.

We also use Azure Java SDK for automation to create VMs and VNets, which works fine as well.

The issue is portal-specific: when creating VMs, the portal gets stuck at the networking section - can't see existing VNets and no option to create new ones. Even if we manually create a VNet through the portal, it doesn't appear in the VM creation dropdown.

The same issue occurs when creating Network Interface Cards (NICs) - existing VNets are not visible.

This suggests the problem is specifically with the portal during the process of vm or network interface creation.

In below image, it shows that i successfully created machines in two regions.

but when try to create machine or nic using portal, i cant see the list of my existing vnets and no option button to create new one. the issue same when create machine (in network tab)
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T23:10:04.48+00:00

I believe the issue is from azure portal itself in my subscription. maybe we need azure technical team to check our subscriptions and troubleshoot the issue from their side.
Priya ranjan Jena 2,295 Reputation points Microsoft External Staff Moderator

2025-09-11T09:51:10.93+00:00

Hi Nasser Al-Hadhrami,

Could you please try to access the portal from the below link? see if that works, please let us know.

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

If you find this comment helpful, please “up-vote” for the information provided , this can be beneficial to community members.

Kindly let us know if you have any additional questions.

Thanks
Nasser Al-Hadhrami 25 Reputation points

2025-09-11T14:52:05.5933333+00:00

Hi @Priya ranjan Jena

Thank you for reply.

still same issue. i cant see vnet list when create machine or network interfaces.

and as i mention before, it works with commands and with azure java api, the issue only with azure portal and only for prod subscription. it works fine for testlab subscription.

Microsoft before few days, they announced they have issue in azure because of fibre cuts in Red Sea. is there any relation? don't know just asking, but the test testlab subscription works fine. i also tried many diff regions and still not wok

because the account was working fine before 2 weeks.
Nasser Al-Hadhrami 25 Reputation points

2025-09-11T22:34:23.59+00:00

Hi @Ravi Varma Mudduluru

Thank you for reply.

I sent you reply on private

Thank you

Answer accepted by question author

1 additional answer

Your answer

Alan Kinane 17,356 Reputation points MVP Volunteer Moderator

2025-09-10T12:35:10.65+00:00

Hi, have you given the VM a name on the 'Basics' tab before proceeding to Networking? I've seen this happen if you don't complete the mandatory fields on the first tab 'Basics'. Complete this tab fully and then move on to Disks and then Networking. I suspect it's the Virtual Machine Name that's missing.
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T13:43:35.84+00:00

Yes, I completed all mandatory fields on the Basics tab including VM name. However, I discovered this is a subscription-specific issue.

When I tried the same process in my test lab subscription, it works perfectly fine - all VNet/Subnet dropdowns load normally. The issue only occurs in my production subscription.

Additionally, normally Azure shows field validation errors when you try to proceed to Review + create - but in my case, the process just gets stuck without any error messages, which indicates this isn't a typical field completion issue.

I tried both chrome & firefox latest versions.

I tried to clean all browser history with all caches.

It was working before few weeks, but today we not able to create machines.

we tried from different regions.

we tried from different devices and IP addresses.

This appears to be a subscription-level service problem rather than a user error.
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T14:01:35.0633333+00:00

The issue isn't limited to VM creation - it also occurs when trying to create a standalone NIC card. I can't see existing VNets and cannot create new ones in any networking scenario within this subscription.

This appears to be a subscription-level service problem affecting all networking components.
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T21:52:53.7433333+00:00

Hello Ankit Yadav,

Thank you for reply.

Yes, Azure CLI works perfectly. I successfully created two VMs in East US and North UAE using the same subscription via CLI commands.

We also use Azure Java SDK for automation to create VMs and VNets, which works fine as well.

The issue is portal-specific: when creating VMs, the portal gets stuck at the networking section - can't see existing VNets and no option to create new ones. Even if we manually create a VNet through the portal, it doesn't appear in the VM creation dropdown.

The same issue occurs when creating Network Interface Cards (NICs) - existing VNets are not visible.

This suggests the problem is specifically with the portal during the creation process of NICs and machines.

in the below image, you may notice, i cant see my vnets and no option to create a new one.

but actually, i have many vents in same region.

normally, the portal show button to create a new vnets below virtual network field.

Thank you in advance, and hope to solve this strange issue soon.
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T22:00:33.3+00:00

Hello,

Thank you for reply.

Yes, Azure CLI works perfectly. I successfully created two VMs in East US and North UAE using the same subscription via CLI commands.

We also use Azure Java SDK for automation to create VMs and VNets, which works fine as well.

The issue is portal-specific: when creating VMs, the portal gets stuck at the networking section - can't see existing VNets and no option to create new ones. Even if we manually create a VNet through the portal, it doesn't appear in the VM creation dropdown.

The same issue occurs when creating Network Interface Cards (NICs) - existing VNets are not visible.

This suggests the problem is specifically with the portal during the process of vm or network interface creation.

In below image, it shows that i successfully created machines in two regions.

but when try to create machine or nic using portal, i cant see the list of my existing vnets and no option button to create new one. the issue same when create machine (in network tab)
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T22:04:04.3+00:00

Hello Ankit Yadav,

Thank you for reply.

Yes, Azure CLI works perfectly. I successfully created two VMs in East US and North UAE using the same subscription via CLI commands.

We also use Azure Java SDK for automation to create VMs and VNets, which works fine as well.

The issue is portal-specific: when creating VMs, the portal gets stuck at the networking section - can't see existing VNets and no option to create new ones. Even if we manually create a VNet through the portal, it doesn't appear in the VM creation dropdown.

The same issue occurs when creating Network Interface Cards (NICs) - existing VNets are not visible.

This suggests the problem is specifically with the portal during the process of vm or network interface creation.
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T22:06:41.6333333+00:00

Hello Ankit Yadav,

Thank you for reply.

Yes, Azure CLI works perfectly. I successfully created two VMs in East US and North UAE using the same subscription via CLI commands.

We also use Azure Java SDK for automation to create VMs and VNets, which works fine as well.

The issue is portal-specific: when creating VMs, the portal gets stuck at the networking section - can't see existing VNets and no option to create new ones. Even if we manually create a VNet through the portal, it doesn't appear in the VM creation dropdown.

The same issue occurs when creating Network Interface Cards (NICs) - existing VNets are not visible.

This suggests the problem is specifically with the portal during the process of vm or network interface creation.

In below image, it shows that i successfully created machines in two regions.

but when try to create machine or nic using portal, i cant see the list of my existing vnets and no option button to create new one. the issue same when create machine (in network tab)
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T22:07:27.8733333+00:00

Hello Ankit Yadav,

Thank you for reply.

Yes, Azure CLI works perfectly. I successfully created two VMs in East US and North UAE using the same subscription via CLI commands.

We also use Azure Java SDK for automation to create VMs and VNets, which works fine as well.

The issue is portal-specific: when creating VMs, the portal gets stuck at the networking section - can't see existing VNets and no option to create new ones. Even if we manually create a VNet through the portal, it doesn't appear in the VM creation dropdown.

The same issue occurs when creating Network Interface Cards (NICs) - existing VNets are not visible.

This suggests the problem is specifically with the portal during the process of vm or network interface creation.

In below image, it shows that i successfully created machines in two regions.

but when try to create machine or nic using portal, i cant see the list of my existing vnets and no option button to create new one. the issue same when create machine (in network tab)
Nasser Al-Hadhrami 25 Reputation points

2025-09-10T23:10:04.48+00:00

I believe the issue is from azure portal itself in my subscription. maybe we need azure technical team to check our subscriptions and troubleshoot the issue from their side.
Priya ranjan Jena 2,295 Reputation points Microsoft External Staff Moderator

2025-09-11T09:51:10.93+00:00

Hi Nasser Al-Hadhrami,

Could you please try to access the portal from the below link? see if that works, please let us know.

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

If you find this comment helpful, please “up-vote” for the information provided , this can be beneficial to community members.

Kindly let us know if you have any additional questions.

Thanks
Nasser Al-Hadhrami 25 Reputation points

2025-09-11T14:52:05.5933333+00:00

Hi @Priya ranjan Jena

Thank you for reply.

still same issue. i cant see vnet list when create machine or network interfaces.

and as i mention before, it works with commands and with azure java api, the issue only with azure portal and only for prod subscription. it works fine for testlab subscription.

Microsoft before few days, they announced they have issue in azure because of fibre cuts in Red Sea. is there any relation? don't know just asking, but the test testlab subscription works fine. i also tried many diff regions and still not wok

because the account was working fine before 2 weeks.
Nasser Al-Hadhrami 25 Reputation points

2025-09-11T22:34:23.59+00:00

Hi @Ravi Varma Mudduluru

Thank you for reply.

I sent you reply on private

Thank you

Answer 1

Ravi Varma Mudduluru 4,250 Microsoft External Staff Moderator

Hello @Nasser Al-Hadhrami,

We have checked with the backed team, and the fix is available in this private flight: https://portal.azure.com/?Microsoft_Azure_Network=flight14. They are still working on part of the fix, but you should now be able to create a network interface without running into any issues. If you do, please don't hesitate to let me know!

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Thanks,
M Ravi Varma

Nasser Al-Hadhrami 25 Reputation points

2025-09-30T21:34:45.2666667+00:00

Hello @Ravi Varma Mudduluru ,

Thank you for the update! I can confirm that the fix is working.

However, I wanted to mention that the link needs to be copied exactly as https://portal.azure.com/?Microsoft_Azure_Network=flight14 for it to work properly.

If users click on the hyperlink directly, it redirects to an incorrect URL: https://portal.azure.com/?Microsoft_Azure_Network=flight14%22https://portal.azure.com/?microsoft_azure_network=flight14%22, which causes same issue.

Thanks again for your help in resolving this and waiting for the Azure team to roll out this fix to the public Azure portal.

Best regards, Nasser Al-Hadhrami
Ravi Varma Mudduluru 4,250 Reputation points Microsoft External Staff Moderator

2025-10-01T00:56:30.5066667+00:00

Hello @Nasser Al-Hadhrami

Thank you for the update.

Answer 2

Hello Nasser Al-Hadhrami,

Can you try to create a test VM using Azure CLI to test if that gets created successfully using that same subscription?

Sample commands:
Set subscription using below command :

az account set --subscription "Your_subscription_name"

then try to create VM using:

az vm create -n MyVm -g MyRG -l eastus --image Ubuntu2204 --size Standard_B1s --generate-ssh-keys

note: in the command
->MyVM is the VM name

->MyRG is the resource group name

->eastus is the location
->Ubuntu2204 is the VM image

->Standard_B1s is the VM size

You can change the values accordingly and test if the VM gets created successfully for you from that subscription.
For more examples/parameters, refer: https://learn.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest#az-vm-create-examples

This way it can rule out the issues with your subscription, virtual network or subnet quota or usage and confirm if there's a portal issue or if it's limited to browser cookie/session.

Share via

Unable to select Virtual Network/Subnet when creating VM in Azure Portal

1 additional answer

Your answer