Share via

Creating new VM, cannot select existing VNET

  • Article

Question

Thursday, September 28, 2017 11:54 AM

Hi,

We have couple of virtual machines all using the same virtual net / subnet. When I try to create a new VM (Windows Server 2016) the existing VNET cannot be selected (message: No virtual net could be found), the only option is to create a new. The new VM is in the same resource group. This has been working before when we've created VM's. Why isn't it possible to select an existing VNET?

All replies (5)

Thursday, September 28, 2017 12:40 PM

When you create the VM, did you select to create a new cloud service? If yes, you can select the virtual network. If you create the VM to an existing cloud service which is associated with a region/virtual network, then you cannot select the virtual network.

Refer the below thread link discussed with same issue.

https://social.msdn.microsoft.com/Forums/en-US/32f172ea-5c78-42a1-848d-5e2ec6dbc2dc/cannot-select-an-existing-virtual-network-while-creating-a-vm-using-nodejs?forum=WAVirtualMachinesforWindows

Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

Thursday, September 28, 2017 2:22 PM

Hi,

No, I selected "Virtual machines" > "Add new".

We don't have any cloud service but we've been able to select an existing VNET before when creating new VM's?

Friday, September 29, 2017 3:46 PM

I tried to check in-house and received a message as below when I selected a different region while creating a new VM other than the region in which the existing VNET has been created:

Could you check if existing VNET region and new VM are in same region.

Could you also share with the screenshot of error message.

Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

Thursday, October 12, 2017 8:57 AM

Hi,

I now realize that I need to select "Resource manager" as distribution model to be able to select the correct VNET.

When I select "Classic" the existing VNET is not found in the list of existing VNET's, so there is no error message.

Friday, October 13, 2017 2:24 PM

Yes, you are right.

Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.