Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[VM] How to specify virtual network from another resource group?
See original GitHub issueHi, I have an issue with azure-cli (0.1.1b3).
I have a virtual network “vn1” in a resource group “rg-network”. I have a resource group “rg-machine” in which I want to create a new VM.
When using az vm create --resource-group "rg-machine" --vnet-name "vn1" [...], a new virtual network is created in “rg-machine” instead of using the existing one in “rg-network”.
Both networks have the exact same name (“vn1”). Is this the expected behavior ? How can we use networks from another resource group ?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:15 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, this is the expected behavior. If you want to use a VNET in the other resource group you should supply the fully qualified ID for the subnet in the other resource group you wish to use. If you supply the subnet ID, do not supply vnet-name (you’ll get an error). It gets automatically parsed out of the subnet ID.
Instead of using
-o json, try-o tsv. That will eliminate the quotes