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