Hello @Neeraj ,
same address space for 2 Vnets that are not peered shouldn't be an issue,
unless you have plans to peer these 2 virtual networks.
It'll be great if you can elaborate more on what is the issue and what are you trying to achieve.
Hi @Neeraj ,
you created the new VM in the same Azure Subscription in the same Azure region?
If so you should be able to select the existing Virtual Network and subnet in the "Create a virtual machine" wizard.
---------
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten
Hi @Andreas Baumgarten ,
Exactly. That is the expected behavior as you have mentioned, but this did not happen. The resources are not just in the same subscription, but also in the same Resource Group and region. I am experiencing this since last couple of weeks for other resources as well.
Regards,
Neeraj
Hi @Neeraj ,
are you deploying the VMs using Availability Zones?
It should not matter and should not cause any issues because virtual networks are spanning all Availability Zones in a region by default.
----------
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten
Hi @Andreas Baumgarten ,
No, I am not deploying the VM using Availability Zone.
Regards,
Neeraj
Sign in to comment