Is it possible to create many VMs in a DevTest lab in the same Resource group? How can I do this?
A new resource group is created for each new VM ( with a random name) in the lab
Currently, there is no way to gather all DevTest Lab VMs into a single Resource Group.
This is the feedback, Azure DevTest Labs Team has replied the issue, you could refer to it.
We’ve planned the work to create minimum number of resource groups for lab VMs (starting from a single resource group for multiple lab VMs, and expand to another resource group if the resource quota is hit). Does it solve your problem? Providing naming convention for the lab-generated resource group and other resources is also planned.
Related
While creating aks cluster by using terraform and using existing values like resource group, vnet, subnet, network security group,
Deployment creating additional resource group, network security group, dns zone.
Do you have any idea how to stop that or disable?
Creating new RG with name MC_RG_XXXXXXXX
Good things:
Cluster getting created by using existing Vnet, subnet, cluster linked with existing RG but its creating network security Group and DNS Zones with new RG.
Any idea?
This is an automatic resource group created to house the cluster https://learn.microsoft.com/en-us/azure/aks/faq#why-are-two-resource-groups-created-with-aks , there is an option in preview to specify the name of this resource group using Azure CLI and within an ARM template https://learn.microsoft.com/en-us/azure/aks/faq#can-i-provide-my-own-name-for-the-aks-node-resource-group.
I'm not sure how this will map in Terraform though.
I am a novice in Azure and currently learning about resource groups. According to their documentation, it says "a resource can only be a member of a single resource group", but I just created 2 different resource groups and named them 'msftlearn-core-infrastructure-rg' and 'msftlearn-core-infrastructure-rg2' under Free Subscription and I added Virtual Network as a resource in both of them.
I have named the network separately as well. The tutorial says to add vitual network resource in just 'msftlearn-core-infrastructure-rg', I created another resource group just to see what error I get if I add same resource in another resource group.
The virtual network resource was added successfully in both the resource groups. So doesn't it contradict the statement: "a resource can only be a member of a single resource group"?
A bit confused here. Please help.
What you did is create 2 virtual networks, both of which are in a single resource group.
A single virtual network can only be in a single resource group.
You can create more of similar resources in different resource groups.
I have an Azure pipeline that creates a new DevTest Lab VM from an Azure Resource Manager (ARM) template. That works great but a new resource group is created for the VM. I would like to specify an existing resource group the VM should belong to but I can't figure out how to configure this in the Azure DevTest Labs Create VM task or in the ARM template JSON file.
I found one example that provided a resourceGroup parameter as part of the resources object in the JSON but that that gives me an invalid template error:
...
"resources": [
{
...
"type": "Microsoft.DevTestLab/labs/virtualmachines",
"name": "[variables('vmName')]",
"resourceGroup": "[parameters('cdResourceGroup')]",
...
}
]
...
This seems like something that should be fairly straightforward but I haven't been able to find this documented.
What I am trying to do is not supported. Looking for other solutions.
Azure DevTest Lab VMs cannot belong to existing resource groups (besides the lab's common resource group). The lab can be configured so that all VMs in the lab belong to a single common resource group or each VM will belong to it's own resource group that is created with the VM (the default). See this Azure DevTest Labs FAQ.
To configure via the Azure portal: Select the lab > "Configuration and policies" > "Lab settings"
Today I tried to add new VM into an Azure Resource Group that already has VMs and other resources and it was successful. I removed it and after a while, when a new VM was being added into the same Resource Group, it prompts a new Resource Group would be needed to store the new VM.
I was wondering when a new VM could and could not be added into a Resource Group taken by other resources.
Thanks.
No, this is not the case, you can put almost any resources together in a resource group. there are some weird exception like: windows and linux app service plans cant exist in the same resource group.
you can add resources to different regions in the same resource group as well
you cannot add resources with the same name and type to the resource group, because name + type combination has to be the same
so you can add VM called new and VM called new1, but not VM called new and another VM called new; but you can add VM called new and Azure SQL called new into the same resource group (give that Azure SQL instance called new is available, but this has nothing to do with the resource group)
This can now be done from the portal. In your portal at the Home page click Virtual Machines, then Add. You can then choose the current resource group and add the machine in to it. May be of use to someone else coming along later like I did.
I'm unable to associate the existing virtual network after moved from one resource group to the required resource group in which I am trying to create new virtual machine in the required resource group through ARM azure portal.
According to the error log, please ensure your VNet is in the Southeast Asia and in the same subscription.
Note: When you move VNet from one resource group to another resource group with new different location, the location of VNet does not change.