Azure Virtual Machine Scale Sets
Azure compute resources that are used to create and manage groups of heterogeneous load-balanced virtual machines.
343 questions
Duplicate Resource groups with differing capitilisation results in inaccessible resources
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 17%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
BF
0
Reputation points
Recently found out that when scaling out our agent pool, we get the following error:
Failed to increase capacity with error: Resource /subscriptions/13d2c765-693d-4278-91be-769abbce15cb/resourceGroups/DEVOPS-AGENTS/providers/Microsoft.Network/virtualNetworks/DEVOPS-AGENTS-VNET referenced by resource /subscriptions/13d2c765-693d-4278-91be-769abbce15cb/resourceGroups/DEVOPS-TEMPLATE/providers/Microsoft.Compute/virtualMachineScaleSets/DevOps-VMSS-Spot was not found. Please make sure that the referenced resource exists, and that both resources are in the same region.
It seems we have two resource groups, one called DEVOPS-TEMPLATE, and one called DevOps-Template which up until 16-Feb had not caused any issues, but now every scale event has this error.
Annoying thing is I can't move the capitalised group into the other one, as in the move resource drop down it is not listed, I suspect because it is the 'current' resource group that it is in, and as such you can't move from resource group A into resource group A sort of thing.
has anyone run into this before or have any ideas?
{count} votes
-
Prrudram-MSFT 21,786 Reputation points2023-03-10T11:49:09.31+00:00 Hello @BF
You are encountering an issue with the virtual network referenced by the virtual machine scale set. The error message indicates that the virtual network resource is not found in the same region as the virtual machine scale set.
To resolve this issue, you can try the following steps:
- Verify that the virtual network resource exists in the same region as the virtual machine scale set.
- If the virtual network resource exists, verify that the virtual network resource is correctly referenced by the virtual machine scale set.
- If the virtual network resource is not correctly referenced, update the virtual machine scale set to reference the correct virtual network resource.
If you are still encountering issues, you can try the following steps:
- Create a new virtual network resource in the same region as the virtual machine scale set.
- Update the virtual machine scale set to reference the new virtual network resource.
-
Prrudram-MSFT 21,786 Reputation points
2023-03-13T18:37:11.7333333+00:00 @BF Do you have any update?
Sign in to comment