I can't attach my new VM to my already created Vnet

Hudson Bento 16 Reputation points
2021-08-25T21:00:13.407+00:00

I have a Vnet created (vnet001) in a resource group (resourses-rg), I try to create a new VM in the same resource group (resourses-rg) in the Vnet already created (vnet001). But, when show to me the configuration of network, Azure don't show me the Vnet (vnet001), instead Azure force to me a create a new vnet. The vnet and vm are in the same location, but in the moment of creation of vm, the vnet don't show, neither of option. Do I need to create another resource, or make a specific configuration in the vnet, to make it visible when creating the vm's?

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,202 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,180 questions

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Andreas Baumgarten 97,731 Reputation points MVP
    2021-08-25T21:32:12.587+00:00

    Hi @Hudson Bento ,

    I've seen this issue because of 2 reasons so far:

    • The VM and the selected Azure region doesn't fit with the Azure region of the vNet (this happens to me most of the time ;-) ) VM and vNet must be in the same region.
    • Permission to read the vNet information are missing.

    Which permission/role does the user have in the subscription (contributor/owner or something special?)

    ----------

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

    Regards
    Andreas Baumgarten

    2 people found this answer helpful.
    0 comments
  2. Hudson Bento 16 Reputation points
    2021-09-01T22:34:35.897+00:00

    Hi! Sorry for the delay!
    These 2 reasons don't match

    1 - I'm trying to create the VM in exactly the same region as Vnet.
    2 - I'm owner of subscription.

    I've already created another management group and a new subscription and I still can't put a VM on the subnet I created... Regardless of how many subnets I create, they are never available when I go to create a VM.

    2 people found this answer helpful.
  3. Aakash 1 Reputation point
    2022-10-10T17:44:51.743+00:00

    This could be because you are trying to launch the VM in an Availability zone where there are no subnets in your Vnet. Try selecting a different zone option where you have your subnet.

    0 comments
  4. Safa Tamer CEVIK 1 Reputation point
    2023-06-20T17:44:47.82+00:00

    Ok, I think I found a solution for this. If you want to attach an existing virtual network to a vm that you are creating, the virtual network must have a network interface first. First, you need to create a network interface in that virtual network and than you can select this virtual network when creating a new virtual machine.