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.
Virtual network not showing up in drop-down menu when creating a VM in Azure Portal
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.
4 answers
Sort by: Most helpful
-
-
Ravi Kanth Koppala 3,231 Reputation points Microsoft Employee
2022-02-18T12:39:00.35+00:00 @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.
-
GitaraniSharma-MSFT 49,591 Reputation points Microsoft Employee
2023-08-08T14:12:34.7333333+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
-
bvn prasad 0 Reputation points
2024-09-27T00:57:06.2233333+00:00 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.