Unknown error while deleting VMSS

Sergey Borovoy 521

I need to delete a VMSS but I can't because every time I get this error: "An unexpected error occured while processing the network profile of the VM. Please retry later."

I suspect that the problem is in the NIC. The Network Settings blade says that my Network interface is "qa-be-asNic" but such NIC does not exist. I tried creating and attaching a new NIC but got this error:

"Failed to attach network interface 'nic-temporary-to-be-deleted' to virtual machine 'qa-be-as'. Error: Operation 'Update Virtual Machine Scale Set' is not allowed on Virtual Machine Scale Set 'qa-be-as' since it is marked for deletion. For more information on your operations, please refer to https://aka.ms/activitylog."

So, in a nutshell: I cannot delete my VMSS because it's screwed up, but I also cannot un-screw it because it's marked for deletion.

Any ideas? Thanks.

anashetty 740 Reputation points Microsoft Vendor

2024-09-18T16:54:01.1366667+00:00

Hi Sergey Borovoy,

Welcome to the Microsoft Q&A Platform. Thank you for posting your query here. We are looking into it and will get back to you soon.

Thank you.
Sergey Borovoy 521 Reputation points

2024-09-24T14:10:41.0566667+00:00

Hello Anashetty and thank you for your continued support.

Check associated resources and delete them: az vmss show --resource-group <your-resource-group> --name <vmss-name> --query "virtualMachineProfile.networkProfile"

Unfortunately, you only provided the az command for showing the network profile (yes, I can see a profile with one Network Interface Config), but not the command for deleting the profile. I am not very familiar with az, so I used the Remove-AzVmssNetworkInterfaceConfiguration comamndlet instead. The result was interesting. Now if I print our the vmss object, the Network profile appears to be empty:

Yet if I run the az vmss show command again, the Network Profile is full of stuff:

How is this humanly possible???

Okay, on to the other advice in your message.

Run the following command to deallocate all instances in the VMSS:

My VMSS is empty, there are no instances.

Run the following command to remove any dependencies on the VMSS:

I ran the command you provided but got the error "Get-AzResource: A positional parameter cannot be found that accepts argument 'dependencies'."

Try Force delete the VMSS through Azure CLI:

I ran the command you provided, it finished without error (in fact, without any output at all), but nothing seems to have changed, the VMSS is still there.

Update the VMSS State**:** Try updating the VMSS configuration via PowerShell or CLI to force it to recognize the correct state and NIC configuration.

I ran the command you provided, it gave me this error: "Update-AzVmss: 'Location' cannot be null."

I thought that "Location" was a parameter so I added "-Location northeurope" to the command line, but this time I got the error "Update-AzVmss: A parameter cannot be found that matches parameter name 'Location'."

This is confusing. What kind of "location" does this commandlet require? My VMSS shows its location as North Europe. Thank you for your observation that the VMSS is in an inconsistent state, I think by now we can safely conclude that this is indeed the case. Question is, what do I do now?

I very much appreciate your continued assistance.

Accepted answer

anashetty 740 Reputation points Microsoft Vendor

2024-09-19T11:48:19.9233333+00:00
Hi Sergey Borovoy,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

We understand from your query that you are experiencing an issue while trying to delete VMSS. Here are few suggestions to help you.

You may need to stop any pending or ongoing operations through the Activity Log: Navigate to the Azure portal and open the VMSS resource. Go to the "Activity log" tab, and filter by "Operation name" to find any operations related to the VMSS. Review the status of each operation, and check if any operations are in pending or running state, you can attempt to cancel them. After that try cancelling VMSS again.

You can force delete VMSS through Azure CLI or PowerShell

PowerShell**:** You can use the Remove-AzVmss cmdlet to force the deletion of the VMSS

Remove-AzVmss -ResourceGroupName <resource-group-name> -VMScaleSetName <vmss-name> -Force

For more information, please refer to https://learn.microsoft.com/en-us/powershell/module/az.compute/remove-azvmss?view=azps-12.3.0&viewFallbackFrom=azps-5.9.0

Azure CLI**:** You can use the az vmss delete command to force the deletion of the VMSS

az vmss delete --resource-group <resource-group-name> --name <vmss-name> --force

For more information, please refer to https://learn.microsoft.com/en-us/cli/azure/vmss?view=azure-cli-latest#az-vmss-delete

Detach NIC from the VMSS Instance: If the NIC issue is blocking the deletion, you can do this through the Azure CLI or PowerShell

To list all NIC in Resource group via Azure CLI:

az network nic list --resource-group <resource-group-name>

For more information, please refer to https://learn.microsoft.com/en-us/cli/azure/network/nic?view=azure-cli-latest#az-network-nic-list

To list all NIC in Resource group via PowerShell:

Get-AzNetworkInterface -ResourceGroupName <resource-group-name>

For more information, please refer to https://learn.microsoft.com/en-us/powershell/module/az.network/get-aznetworkinterface?view=azps-12.3.0&viewFallbackFrom=azps-5.9.0

Try to detach NIC manually through Azure CLI or PowerShell:

az vmss update --resource-group <resource-group-name> --name <vmss-name> --remove virtualMachines 0 networkProfile.networkInterfaces

$vmss = Get-AzVmss -ResourceGroupName <resource-group-name> -VMScaleSetName <vmss-name> $vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaces.Remove($vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaces[0]) Update-AzVmss -ResourceGroupName <resource-group-name> -VMScaleSetName <vmss-name> -VirtualMachineScaleSet $vmss

If this doesn't work, please provide more details regarding this issue. If you have any further queries, please do let us know.

If the answer is helpful, please click "Accept Answer" and "Upvote it."
Please sign in to rate this answer.
Sergey Borovoy 521 Reputation points

2024-09-19T19:46:52.13+00:00

Hi Anashetty,

thank you for your effort. Unfortunately, I must say that none of your suggestions worked.

As for "stoping any pending or ongoing operations through the Activity Log": I can see multiple "Delete Virtual Machine Scale Set" operations with the status of "Failed" but no pending / ongoing operations. Consequently, there is nothing to stop.

Trying to delete the VMSS via PowerShell leads to the same error as through the Portal:

Trying to remove the network interface leads to this error: InvalidOperation: Cannot index into a null array. The null array in this case is $vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaces[0]. Indeed, when I look at $vmss.VirtualMachineProfile.NetworkProfile, I see one NetworkInterfaceConfiguration element, but no NetworkInterface elements:

I also tried removing the NetworkInterfaceConfigurations using:

$vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaces.Remove($vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaceConfigurations[0])

but got the error InvalidOperation: You cannot call a method on a null-valued expression.
I do not understand this error. $vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaceConfigurations[0] is NOT null, I can print it out.

I would very much appreciate further advice from you. Thank you.

anashetty 740 Reputation points Microsoft Vendor

2024-09-20T17:25:55.8333333+00:00

Hi Sergey Borovoy,

Thank you for the detailed explanation, and based on the information provided, here are some additional suggestions to help resolve the issue.

Check associated resources and delete them:
az vmss show --resource-group <your-resource-group> --name <vmss-name> --query "virtualMachineProfile.networkProfile"

Run the following command to deallocate all instances in the VMSS:
Stop-AzVmss -ResourceGroupName $resourceGroupName -VMScaleSetName $vmssName -Force

Run the following command to remove any dependencies on the VMSS:
Get-AzResource -ResourceGroupName $resourceGroupName -ResourceType Microsoft.Compute/virtualMachineScaleSets -Name $vmssName -ExpandProperties dependencies | ForEach-Object { Remove-AzResource -ResourceId $_.Id -Force }

Try Force delete the VMSS through Azure CLI:
az vmss delete --resource-group <your-resource-group> --name <vmss-name> --no-wait --force-deletion

If the above approach doesn't work, you can try below steps.

The error you're facing — InvalidOperation: Cannot index into a null array — suggests that the NetworkInterfaces array is either empty or not properly initialized. This situation may arise when the VM Scale Set (VMSS) is in an inconsistent state, such as being marked for deletion but failing to complete the process.

Update the VMSS State**:** Try updating the VMSS configuration via PowerShell or CLI to force it to recognize the correct state and NIC configuration.

Update-AzVmss -ResourceGroupName "YourResourceGroup" -VMScaleSetName "YourVmssName"

Please try above steps, if you have any further queries, please do let us know.

If the answer is helpful, please click "Accept Answer" and "Upvote it."

anashetty 740 Reputation points Microsoft Vendor

2024-09-23T08:55:30.2233333+00:00

Hi Sergey Borovoy,

Just checking in to see if you had a chance to see my response to your question. Please tell us if it was helpful and feel free to reach out to us if you have any queries.

If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.

anashetty 740 Reputation points Microsoft Vendor

2024-09-24T10:05:59.7966667+00:00

Hi Sergey Borovoy,

Just checking in to see if you had a chance to see my response to your question. Please tell us if it was helpful and feel free to reach out to us if you have any queries.

If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.

Sergey Borovoy 521 Reputation points

2024-09-24T14:04:50.2866667+00:00

Hello Anashetty and thank you for your continued support.

Check associated resources and delete them: az vmss show --resource-group <your-resource-group> --name <vmss-name> --query "virtualMachineProfile.networkProfile"

Unfortunately, you only provided the az command for showing the network profile (yes, I can see a profile with one Network Interface Config), but not the command for deleting the profile. I am not very familiar with az, so I used the Remove-AzVmssNetworkInterfaceConfiguration comamndlet instead. The result was interesting. Now if I print our the vmss object, the Network profile appears to be empty:

Yes if I run the az vmss show command again, the Network Profile is full of stuff:

How is this humanly possible???

Okay, on to the other advice in your message.

Run the following command to deallocate all instances in the VMSS:

My VMSS is empty, there are no instances.

Run the following command to remove any dependencies on the VMSS:

I ran the command you provided but got the error "Get-AzResource: A positional parameter cannot be found that accepts argument 'dependencies'."

Try Force delete the VMSS through Azure CLI:

I ran the command you provided, it finished without error (in fact, without any output at all), but nothing seems to have changed, the VMSS is still there.

Update the VMSS State**:** Try updating the VMSS configuration via PowerShell or CLI to force it to recognize the correct state and NIC configuration.

I ran the command you provided, it gave me this error: "Update-AzVmss: 'Location' cannot be null."

I thought that "Location" was a parameter so I added "-Location northeurope" to the command line, but this time I got the error "Update-AzVmss: A parameter cannot be found that matches parameter name 'Location'."

This is confusing. What kind of "location" does this commandlet require? My VMSS shows its location as North Europe.

Thank you for your observation that the VMSS is in an inconsistent state, I think by now we can safely conclude that this is indeed the case. Question is, what do I do now?

I very much appreciate your continued assistance.

Sergey Borovoy 521 Reputation points

2024-09-24T14:07:04.3333333+00:00

Hello Anashetty and thank you for your continued support.

Check associated resources and delete them: az vmss show --resource-group <your-resource-group> --name <vmss-name> --query "virtualMachineProfile.networkProfile"

Unfortunately, you only provided the az command for showing the network profile (yes, I can see a profile with one Network Interface Config), but not the command for deleting the profile. I am not very familiar with az, so I used the Remove-AzVmssNetworkInterfaceConfiguration comamndlet instead. The result was interesting. Now if I print our the vmss object, the Network profile appears to be empty:

Yet if I run the az vmss show command again, the Network Profile is full of stuff:

How is this humanly possible???

Okay, on to the other advice in your message.

Run the following command to deallocate all instances in the VMSS:

My VMSS is empty, there are no instances.

Run the following command to remove any dependencies on the VMSS:

I ran the command you provided but got the error "Get-AzResource: A positional parameter cannot be found that accepts argument 'dependencies'."

Try Force delete the VMSS through Azure CLI:

I ran the command you provided, it finished without error (in fact, without any output at all), but nothing seems to have changed, the VMSS is still there.

Update the VMSS State**:** Try updating the VMSS configuration via PowerShell or CLI to force it to recognize the correct state and NIC configuration.

I ran the command you provided, it gave me this error: "Update-AzVmss: 'Location' cannot be null."

I thought that "Location" was a parameter so I added "-Location northeurope" to the command line, but this time I got the error "Update-AzVmss: A parameter cannot be found that matches parameter name 'Location'."

This is confusing. What kind of "location" does this commandlet require? My VMSS shows its location as North Europe. Thank you for your observation that the VMSS is in an inconsistent state, I think by now we can safely conclude that this is indeed the case. Question is, what do I do now?

I very much appreciate your continued assistance.

Sergey Borovoy 521 Reputation points

2024-09-24T14:09:22.3666667+00:00

Hello Anashetty and thank you for your continued support.

Check associated resources and delete them: az vmss show --resource-group <your-resource-group> --name <vmss-name> --query "virtualMachineProfile.networkProfile"

Unfortunately, you only provided the az command for showing the network profile (yes, I can see a profile with one Network Interface Config), but not the command for deleting the profile. I am not very familiar with az, so I used the Remove-AzVmssNetworkInterfaceConfiguration comamndlet instead. The result was interesting. Now if I print out the PowerShell vmss object, the Network profile appears to be empty:

Yet if I run the az vmss show command again, the Network Profile is full of stuff:

How is this humanly possible???

Okay, on to the other advice in your message.

Run the following command to deallocate all instances in the VMSS:

My VMSS is empty, there are no instances.

Run the following command to remove any dependencies on the VMSS:

I ran the command you provided but got the error "Get-AzResource: A positional parameter cannot be found that accepts argument 'dependencies'."

Try Force delete the VMSS through Azure CLI:

I ran the command you provided, it finished without error (in fact, without any output at all), but nothing seems to have changed, the VMSS is still there.

Update the VMSS State**:** Try updating the VMSS configuration via PowerShell or CLI to force it to recognize the correct state and NIC configuration.

I ran the command you provided, it gave me this error: "Update-AzVmss: 'Location' cannot be null."

I thought that "Location" was a parameter so I added "-Location northeurope" to the command line, but this time I got the error "Update-AzVmss: A parameter cannot be found that matches parameter name 'Location'."

This is confusing. What kind of "location" does this commandlet require? My VMSS shows its location as North Europe. Thank you for your observation that the VMSS is in an inconsistent state, I think by now we can safely conclude that this is indeed the case. Question is, what do I do now?

I very much appreciate your continued assistance.

Sergey Borovoy 521 Reputation points

2024-09-24T14:11:58.1766667+00:00

Hello Anashetty and thank you for your continued support.

Check associated resources and delete them: az vmss show --resource-group <your-resource-group> --name <vmss-name> --query "virtualMachineProfile.networkProfile"

Unfortunately, you only provided the az command for showing the network profile (yes, I can see a profile with one Network Interface Config), but not the command for deleting the profile. I am not very familiar with az, so I used the Remove-AzVmssNetworkInterfaceConfiguration comamndlet instead. The result was interesting. Now if I print our the vmss object, the Network profile appears to be empty:

Yet if I run the az vmss show command again, the Network Profile is full of stuff:

How is this humanly possible???

Okay, on to the other advice in your message.

Run the following command to deallocate all instances in the VMSS:

My VMSS is empty, there are no instances.

Run the following command to remove any dependencies on the VMSS:

I ran the command you provided but got the error "Get-AzResource: A positional parameter cannot be found that accepts argument 'dependencies'."

Try Force delete the VMSS through Azure CLI:

I ran the command you provided, it finished without error (in fact, without any output at all), but nothing seems to have changed, the VMSS is still there.

Update the VMSS State**:** Try updating the VMSS configuration via PowerShell or CLI to force it to recognize the correct state and NIC configuration.

I ran the command you provided, it gave me this error: "Update-AzVmss: 'Location' cannot be null."

I thought that "Location" was a parameter so I added "-Location northeurope" to the command line, but this time I got the error "Update-AzVmss: A parameter cannot be found that matches parameter name 'Location'."

This is confusing. What kind of "location" does this commandlet require? My VMSS shows its location as North Europe. Thank you for your observation that the VMSS is in an inconsistent state, I think by now we can safely conclude that this is indeed the case. Question is, what do I do now?

I very much appreciate your continued assistance.

Sergey Borovoy 521 Reputation points

2024-09-24T14:13:43.1566667+00:00

I wrote a long reply to your comments but when I click "Add comment", nothing happens. Fortunately, I saved it in the clipboard so I could try again, and then again, but still it does not appear on the page.

Yet this shorter comment went through.

I don't know what's going on, must be some bug on the learn website. Please advice.

Sergey Borovoy 521 Reputation points

2024-09-24T14:18:00.1333333+00:00

Okay now I see that my comment was "deleted due to a violation of our Code of Conduct." I read the Code but I absolutely fail to see what part of my comment went against any policies. It would be helpful if the person who deleted it could be a bit more specific!..

Sergey Borovoy 521 Reputation points

2024-09-24T14:22:19.97+00:00

Okay, will try to post again, this time without the screenshots. They are helpful but not indispensable.

Hello Anashetty and thank you for your continued support.

Check associated resources and delete them: az vmss show --resource-group <your-resource-group> --name <vmss-name> --query "virtualMachineProfile.networkProfile"

Unfortunately, you only provided the az command for showing the network profile (yes, I can see a profile with one Network Interface Config), but not the command for deleting the profile. I am not very familiar with az, so I used the Remove-AzVmssNetworkInterfaceConfiguration comamndlet instead. The result was interesting. Now if I print our the vmss object, the Network profile appears to be empty:

........................

ManagedDisk : StorageAccountType : Premium_LRS

NetworkProfile :

ExtensionProfile :

Extensions[0] :

........................

Yet if I run the az vmss show command again, the Network Profile is still full of stuff, including one Network Interface Config.

How is this humanly possible?

Okay, on to the other advice in your message.

Run the following command to deallocate all instances in the VMSS:

My VMSS is empty, there are no instances.

Run the following command to remove any dependencies on the VMSS:

I ran the command you provided but got the error "Get-AzResource: A positional parameter cannot be found that accepts argument 'dependencies'."

Try Force delete the VMSS through Azure CLI:

I ran the command you provided, it finished without error (in fact, without any output at all), but nothing seems to have changed, the VMSS is still there.

Update the VMSS State**:** Try updating the VMSS configuration via PowerShell or CLI to force it to recognize the correct state and NIC configuration.

I ran the command you provided, it gave me this error: "Update-AzVmss: 'Location' cannot be null."

I thought that "Location" was a parameter so I added "-Location northeurope" to the command line, but this time I got the error "Update-AzVmss: A parameter cannot be found that matches parameter name 'Location'."

This is confusing. What kind of "location" does this commandlet require? My VMSS shows its location as North Europe.

Thank you for your observation that the VMSS is in an inconsistent state, I think by now we can safely conclude that this is indeed the case. Question is, what do I do now?

I very much appreciate your continued assistance.

anashetty 740 Reputation points Microsoft Vendor

2024-09-25T13:13:26.46+00:00

Hi Sergey Borovoy,

Thank you for getting back with us and based on the information provided, here are some additional suggestions to help resolve the issue.

Can you please try this below command to list dependencies:
Get-AzResource -ResourceGroupName $resourceGroupName | Where-Object {$_.ResourceId -like "*$vmssName*"}

If the dependencies are listed, try removing them by using this command:
Get-AzResource -ResourceGroupName $resourceGroupName | Where-Object {$_.ResourceId -like "*$vmssName*"} | ForEach-Object { Remove-AzResource -ResourceId $_.ResourceId -Force }

After removing dependencies, Force delete VMSS by using command:
az vmss delete --resource-group <your-resource-group> --name <vmss-name> --force-deletion

If the above steps don't help, please try this:

Retrieve the Current VMSS Configuration:
$vmss = Get-AzVmss -ResourceGroupName "YourResourceGroup" -VMScaleSetName "YourVmssName"

After retrieving the configuration, check the Location property of the VMSS object:

$vmss.Location

You can update the VMSS without the -Location parameter by specifying the existing configuration:

Update-AzVmss -ResourceGroupName "YourResourceGroup" -VMScaleSetName "YourVmssName" -VirtualMachineScaleSet $vmss

Make sure to replace "YourResourceGroup" and "YourVmssName" with your actual resource group name and VMSS name.

Please follow the steps above and if you still need assistance, please reach out to us if you have further queries.

If the answer is helpful, please click "Accept Answer" and "Upvote it."

anashetty 740 Reputation points Microsoft Vendor

2024-09-26T12:03:30.2266667+00:00

Hi Sergey Borovoy,

Just checking to see if the modified answer helped for you...! Please tell us if it was helpful and feel free to reach out to us if you have any queries.

If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.

Sergey Borovoy 521 Reputation points

2024-09-26T15:35:05.3933333+00:00

Hello Anashetty and thank you for your continued support.

Can you please try this below command to list dependencies:

The command showed 2 dependencies, an NSG and a load balancer. The subsequent deletion command deleted the NSG but gave out this error for the LB: "Cannot delete load balancer qa-be-aslb since its child resources qa-be-aslb/inboundNatPools/natpool,bepool are in use by virtual machine scale set"

Next you suggested that I try deleting the VMSS again but the result was the same as before.

Next you suggested that I retrieve the location of the VMSS. I am not sure why, since right afterwards you said "You can update the VMSS without the -Location parameter". But I retrieved it anyway, which, as I mentioned earlier, was northeurope.

You can update the VMSS without the -Location parameter by specifying the existing configuration: Update-AzVmss -ResourceGroupName "YourResourceGroup" -VMScaleSetName "YourVmssName" -VirtualMachineScaleSet $vmss

This command gave me the error:

Update-AzVmss: Operation 'Update Virtual Machine Scale Set' is not allowed on Virtual Machine Scale Set 'qa-be-as' since it is marked for deletion. For more information on your operations, please refer to https://aka.ms/activitylog.

ErrorCode: OperationNotAllowed

ErrorMessage: Operation 'Update Virtual Machine Scale Set' is not allowed on Virtual Machine Scale Set 'qa-be-as' since it is marked for deletion. For more information on your operations, please refer to https://aka.ms/activitylog.

ErrorTarget:

StatusCode: 409

ReasonPhrase:

OperationID : 630f2e97-94ce-41da-8944-7a689342b8cb

You may remember I reported this same error before when tryoing to attach a different NIC to the VMSS.

It seems as if we are going in circles by now and need some fresh angle although I cannot say what it might be. I very much appreciate your continued assistance.

anashetty 740 Reputation points Microsoft Vendor

2024-09-27T10:54:57.8266667+00:00

Hi Sergey Borovoy,

We understand from your query that you are experiencing an issue. Please try below steps.

Try this command to get the Load Balancer dependencies:
Get-AzLoadBalancer -ResourceGroupName $resourceGroupName -Name $loadBalancerName

check the inbound NAT pools and backend address pools:

Get-AzLoadBalancerBackendAddressPool -ResourceGroupName $resourceGroupName -LoadBalancerName $loadBalancerName

Get-AzLoadBalancerInboundNatPool -ResourceGroupName $resourceGroupName -LoadBalancerName $loadBalancerName

To remove the dependencies, you need to first disassociate the VMSS from the load balancer resources. Specifically, disassociate the backend pool and inbound NAT pool from the VMSS.

Remove the VMSS association with the Load Balancer's Backend Pool:

$vmss = Get-AzVmss -ResourceGroupName $resourceGroupName -VMScaleSetName $vmssName

# Clear Load Balancer Backend Address Pool association

$vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaceConfigurations[0].IpConfigurations[0].LoadBalancerBackendAddressPools = @()

# Update the VMSS to apply changes

Update-AzVmss -ResourceGroupName $resourceGroupName -VMScaleSetName $vmssName -VirtualMachineScaleSet $vmss

Remove the VMSS association with the Load Balancer's NAT Pool:

# Clear Load Balancer NAT Pool association

$vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaceConfigurations[0].IpConfigurations[0].LoadBalancerInboundNatPools = @()

# Update the VMSS to apply changes

Update-AzVmss -ResourceGroupName $resourceGroupName -VMScaleSetName $vmssName -VirtualMachineScaleSet $vmss

After you have cleared the VMSS associations with the backend pool and NAT pool, check the dependencies of the load balancer again to ensure they are removed.

Get-AzLoadBalancer -ResourceGroupName $resourceGroupName -Name $loadBalancerName

Delete the VMSS and then delete Load Balancer

Remove-AzVmss -ResourceGroupName $resourceGroupName -VMScaleSetName $vmssName

Remove-AzLoadBalancer -ResourceGroupName $resourceGroupName -Name $loadBalancerName

I have provided more information to your question. Please tell us if it was helpful and feel free to reach out to us if you have any queries.

If the answer is helpful, please click "Accept Answer" and "Upvote it."

Sergey Borovoy 521 Reputation points

2024-09-29T19:55:22.1+00:00

Hello Anashetty,

# Clear Load Balancer Backend Address Pool association $vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaceConfigurations[0].IpConfigurations[0].LoadBalancerBackendAddressPools = @()

Without even trying it I can see that this won't work because, as I already mentioned, accessing $vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaceConfigurations[0] gives me "InvalidOperation: Cannot index into a null array."

Well I tried it anyway and I sure got one:

Your next advice ("Clear Load Balancer NAT Pool association") also involves acessing ...NetworkInterfaceConfigurations[0] so it won't work as well.

My NetworkProfile is indeed empty:
This is different from what I had before (see my comment dated Sep 19) when my NetworkInterfaceConfigurations array was NOT empty, as evident from the screenshot I attached thereto.

Now my situation is like this:

Empty NetworkProfile

The only dependency is this LB named qa-be-aslb. But it's a one-way dependency: the LB thinks its pools are attached to the VMSS, but the VMSS's Network Profile is empty.

Because the Network Profile is empty, I cannot remove the association with the LB's NAT Pool.

And I also cannot remove the LB because it gives me this error:
Remove-AzLoadBalancer: Cannot delete load balancer /subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb since its child resources /subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/inboundNatPools/natpool,bepool are in use by virtual machine scale set /subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Compute/virtualMachineScaleSets/qa-be-as.

Still stuck 😥 Will appreciate your continued help.

anashetty 740 Reputation points Microsoft Vendor

2024-09-30T16:13:43.96+00:00

Hi Sergey Borovoy,

Try using both in Azure CLI and in PowerShell commands.

Retrieve the Load Balancer:

PowerShell: $lb = Get-AzLoadBalancer -ResourceGroupName <resourceGroupName> -Name <loadBalancerName>

Azure CLI: az network lb show --resource-group <resourceGroupName> --name <loadBalancerName> --output json > lb.json

Remove Backend Address Pool Association:

PowerShell: $lb.BackendAddressPools = $lb.BackendAddressPools | Where-Object { $_.Id -ne "/subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/backendAddressPools/bepool" }

Azure CLI: az network lb backend-pool delete --resource-group <resourceGroupName> --lb-name <loadBalancerName> --name <backendPoolName>

Remove NAT Pool Association (if applicable):

PowerShell: $lb.InboundNatPools = $lb.InboundNatPools | Where-Object { $_.Id -ne "/subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/inboundNatPools/natpool" }

Azure CLI: az network lb inbound-nat-pool delete --resource-group <resourceGroupName> --lb-name <loadBalancerName> --name <natPoolName>

Update the Load Balancer:

PowerShell: Set-AzLoadBalancer -LoadBalancer $lb

Delete the Load Balancer:

PowerShell: Remove-AzLoadBalancer -ResourceGroupName <resourceGroupName> -Name <loadBalancerName>

Azure CLI: az network lb delete --resource-group <resourceGroupName> --name <loadBalancerName>

To Delete the VMSS:

PowerShell: Remove-AzVmss -ResourceGroupName <resourceGroupName> -VMScaleSetName <vmssName>

Azure CLI: az vmss delete --resource-group <resourceGroupName> --name <vmssName>

I have provided more information to your question. Please tell us if it was helpful and feel free to reach out to us if you have any queries.

If the answer is helpful, please click "Accept Answer" and "Upvote it."

anashetty 740 Reputation points Microsoft Vendor

2024-10-01T06:27:47.34+00:00

Hi Sergey Borovoy,

I just wanted to follow up on our previous conversation and ask if the response I provided was helpful to you.

If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.

anashetty 740 Reputation points Microsoft Vendor

2024-10-03T09:53:54.95+00:00

Hi Sergey Borovoy,

I just wanted to follow up on our previous conversation and ask if the response I provided was helpful to you.

If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.

Sergey Borovoy 521 Reputation points

2024-10-03T12:45:19.0866667+00:00

Hi Anashetty,

apologies for the delay, I was out of office for a couple of days.

Trying to obtain the backend pool with PS commands did not quite work:

C:> $lb = Get-AzLoadBalancer -ResourceGroupName QA-BE-AS-Scale -Name qa-be-aslb C:> $lb ResourceGroupName Name Location ProvisioningState Sku Name ----------------- ---- -------- ----------------- -------- QA-BE-AS-Scale qa-be-aslb northeurope Succeeded Standard C:\> $lb.BackendAddressPools = $lb.BackendAddressPools | Where-Object { $_.Id -ne "/subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/backendAddressPools/bepool" } C:\> $lb.BackendAddressPools C:\>

(Yes, I remembered to use the right subscription ID of course).

So, the BackendAddressPools now shows as empty, which it really isn't.

Okay, I tried the AZ CLI:

C:> az network lb show --resource-group QA-BE-AS-Scale --name qa-be-aslb --output json { "backendAddressPools": [ { "etag": "W/\"474e1bd8-105b-4c94-ac66-6d32ec50f81e\"", "id": "/subscriptions/2c17...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/backendAddressPools/bepool", "loadBalancerBackendAddresses": [], "loadBalancingRules": [ { "id": "/subscriptions/2c17...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/loadBalancingRules/LBRule", "resourceGroup": "QA-BE-AS-Scale" } ], "name": "bepool", "provisioningState": "Succeeded", "resourceGroup": "QA-BE-AS-Scale", "type": "Microsoft.Network/loadBalancers/backendAddressPools" } ], "frontendIPConfigurations": [ ................. ], "id": "/subscriptions/2c1...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb", "inboundNatPools": [ ............... ], "inboundNatRules": [], "loadBalancingRules": [ { "backendAddressPool": { "id": "/subscriptions/2c17...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/backendAddressPools/bepool", "resourceGroup": "QA-BE-AS-Scale" }, "backendAddressPools": [ { "id": "/subscriptions/2c17...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/backendAddressPools/bepool", "resourceGroup": "QA-BE-AS-Scale" } ], "backendPort": 80, "disableOutboundSnat": false, "enableFloatingIP": false, "enableTcpReset": false, "etag": "W/\"474e1bd8-105b-4c94-ac66-6d32ec50f81e\"", "frontendIPConfiguration": { "id": "/subscriptions/2c17...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/frontendIPConfigurations/LoadBalancerFrontEnd", "resourceGroup": "QA-BE-AS-Scale" }, "frontendPort": 80, "id": "/subscriptions/2c17...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/loadBalancingRules/LBRule", "idleTimeoutInMinutes": 5, "loadDistribution": "Default", "name": "LBRule", "probe": { "id": "/subscriptions/2c17...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/probes/tcpProbe", "resourceGroup": "QA-BE-AS-Scale" }, "protocol": "Tcp", "provisioningState": "Succeeded", "resourceGroup": "QA-BE-AS-Scale", "type": "Microsoft.Network/loadBalancers/loadBalancingRules" } ], "location": "northeurope", "name": "qa-be-aslb", "outboundRules": [], "probes": [ ..........................etc }

Okay so far so good, we can see the BE pool. But when I try to delete it, I get the error:

C:\> az network lb address-pool delete --resource-group QA-BE-AS-Scale --lb-name qa-be-aslb --name bepool (InvalidResourceReference) Resource /subscriptions/2c17...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/backendAddressPools/bepool referenced by resource /subscriptions/2c17...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/loadBalancingRules/LBRule was not found. Please make sure that the referenced resource exists, and that both resources are in the same region.

You can see from the JSON above that I do indeed have LBRule. I can also get it like this:

C:\> az network lb rule list -g QA-BE-AS-Scale --lb-name qa-be-aslb -o table BackendPort DisableOutboundSnat EnableFloatingIP EnableTcpReset FrontendPort IdleTimeoutInMinutes LoadDistribution Name Protocol ProvisioningState ResourceGroup ------------- --------------------- ------------------ ---------------- -------------- ---------------------- ------------------ ------ ---------- ------------------- --------------- 80 False False False 80 5 Default LBRule Tcp Succeeded QA-BE-AS-Scale

I am not sure about the part of the error which says "both resources are in the same region". You can see that the LB itself is in "northeurope", but I do not see any property of the LB rule that indicates its location. I am not sure that LB rules are supposed to have a location at all.

Removing the inbounds NAT pool was equally unsuccessful:

C:> az network lb inbound-nat-pool delete --resource-group QA-BE-AS-Scale --lb-name qa-be-aslb --name natpool (LoadBalancerInboundNatPoolInUseByVirtualMachineScaleSet) Cannot remove inbound nat pool natpool from load balancer since it is in use by virtual machine scale set /subscriptions/2c17...d5/resourceGroups/QA-BE-AS-SCALE/providers/Microsoft.Compute/virtualMachineScaleSets/qa-be-as.

(Detaching the LB from the VMSS won't work either - remember we tried it already).

Still stuck, will appreciate your continued help.

anashetty 740 Reputation points Microsoft Vendor

2024-10-03T16:14:39.0233333+00:00

Hi Sergey Borovoy,

Please try below steps:

Delete the Load Balancer Rule First: az network lb rule delete --resource-group QA-BE-AS-Scale --lb-name qa-be-aslb --name LBRule
https://learn.microsoft.com/en-us/cli/azure/network/lb/rule?view=azure-cli-latest#az-network-lb-rule-delete
Then Delete the Backend Pool: az network lb address-pool delete --resource-group QA-BE-AS-Scale --lb-name qa-be-aslb --name bepool

https://learn.microsoft.com/en-us/cli/azure/network/lb/address-pool?view=azure-cli-latest#az-network-lb-address-pool-delete

Detach the NAT Pool from the VMSS: az vmss update --resource-group QA-BE-AS-Scale --name qa-be-as --remove virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0].loadBalancerInboundNatPools "/subscriptions/{subscription-id}/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/inboundNatPools/natpool"

Check that you specify the correct index [0] for networkInterfaceConfigurations, and replace {subscription-id} with your actual subscription ID.

Delete the NAT Pool: az network lb inbound-nat-pool delete --resource-group QA-BE-AS-Scale --lb-name qa-be-aslb --name natpool

https://learn.microsoft.com/en-us/cli/azure/network/lb/inbound-nat-pool?view=azure-cli-latest#az-network-lb-inbound-nat-pool-delete

Check that the Load Balancer, Backend Address Pool, VM Scale Set, and all associated resources are in the same region. You can verify the region of these resources by running: az network lb show --resource-group QA-BE-AS-Scale --name qa-be-aslb --query location

az vmss show --resource-group QA-BE-AS-Scale --name qa-be-as --query location

Please let us know if you have any further queries. I’m happy to assist you further.

anashetty 740 Reputation points Microsoft Vendor

2024-10-07T01:47:45.64+00:00

Hi Sergey Borovoy,

I just wanted to follow up on our previous conversation and ask if the response I provided was helpful to you.

If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.

Sergey Borovoy 521 Reputation points

2024-10-07T11:00:00.1733333+00:00

Hi Anashetty,

I was able to delete the LB rule, thank you. But I cannot delete the BE Pool, although the error is now different:

*
(LoadBalancerBackendAddressPoolInUseByVirtualMachineScaleSet) Cannot remove backend address pool bepool from load balancer since it is in use by virtual machine scale set /subscriptions/2c...d5/resourceGroups/QA-BE-AS-SCALE/providers/Microsoft.Compute/virtualMachineScaleSets/qa-be-as.*

So we're back to what I wrote earlier: "the LB thinks its pools are attached to the VMSS, but the VMSS's Network Profile is empty".

As for your next suggestion ("Delete the NAT Pool"), I tried the removal command but got this error:

Couldn't find 'loadBalancerInboundNatPools' in 'virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0]'. Available options: ['additionalProperties', 'auxiliaryMode', 'auxiliarySku', 'deleteOption', 'disableTcpStateTracking', 'dnsSettings', 'enableAcceleratedNetworking', 'enableFpga', 'enableIpForwarding', 'ipConfigurations', 'name', 'networkSecurityGroup', 'primary']

Indeed, when I look at my VMSS, I see that loadBalancerInboundNatPools is a property of ipConfigurations, not a property of networkInterfaceConfigurations[0].

So I tried a modified command (added "ipConfigurations)":*
*
az vmss update --resource-group QA-BE-AS-Scale --name qa-be-as --remove virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0].ipConfigurations[0].loadBalancerInboundNatPools "/subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/inboundNatPools/natpool"

But the error was:

invalid syntax: --remove property.list <indexToRemove> OR --remove propertyToRemove

Then I also tried removing the ipConfigurations[0] and ipConfigurations[0].loadBalancerInboundNatPools without specifying the full id of the NAT pool (i.e., simply skipped this entire part at the end in quotes). Both times the error was like this:

(OperationNotAllowed) Operation 'Update Virtual Machine Scale Set' is not allowed on Virtual Machine Scale Set 'qa-be-as' since it is marked for deletion.

So this seems to be the correct syntax for what we're trying to achieve, but this marked for deletion error throws us back to my original question.

(As a reminder: there are no ongoing operation in the Activity Log; all operations are either "succeeded" or "failed". So I do not understand this "marked for deletion" thing. Marked where? How do I unmark it?)

I really appreciate your efforts and look forward to more advice. Thank you.

Sergey

Sergey Borovoy 521 Reputation points

2024-10-07T12:05:39.6066667+00:00

Hi Anashetty,

I am having this problem with Learn - Q&A again, whereby my replies just don't get posted. Had it before (Sept. 24), tried posting several times, eventually they all got posted and I ended up with a bunch of duplicates. Don't want to repeat this.

Do you know who supports the Learn - Q&A website? I don't see any kind of support link.

Sergey Borovoy 521 Reputation points

2024-10-07T12:14:38.32+00:00

Okay, now both my replies got posted. I just don't understand why this is happening sometimes with a very long delay.

anashetty 740 Reputation points Microsoft Vendor

2024-10-08T09:51:17.5566667+00:00

Hi Sergey Borovoy,

Check Backend Pool References:

az vmss show --resource-group QA-BE-AS-Scale --name qa-be-as --query "virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0].ipConfigurations"

Force Remove the Backend Pool:

az network lb address-pool update --resource-group QA-BE-AS-Scale --lb-name qa-be-aslb --name bepool --clear backendAddressPools

Check for Existing Operations:

az resource show --ids /subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Compute/virtualMachineScaleSets/qa-be-as --expand=properties

If the VMSS is still marked for deletion, you might need to check its provisioning state:

az vmss show --resource-group QA-BE-AS-Scale --name qa-be-as --query "provisioningState"

Did you try detaching the NAT pool and deleting it.

Detach the NAT Pool from the VMSS: az vmss update --resource-group QA-BE-AS-Scale --name qa-be-as --remove virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0].loadBalancerInboundNatPools "/subscriptions/{subscription-id}/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/inboundNatPools/natpool"

Check that you specify the correct index [0] for networkInterfaceConfigurations, and replace {subscription-id} with your actual subscription ID.

Delete the NAT Pool: az network lb inbound-nat-pool delete --resource-group QA-BE-AS-Scale --lb-name qa-be-aslb --name natpool

https://learn.microsoft.com/en-us/cli/azure/network/lb/inbound-nat-pool?view=azure-cli-latest#az-network-lb-inbound-nat-pool-delete

Please try above steps and if you have any queries, please let me know.

As per your issue with Learn - Q&A again, you can give feedback on it https://learn.microsoft.com/en-us/answers/support/site-feedback

Sergey Borovoy 521 Reputation points

2024-10-08T14:45:37.23+00:00

Hi Anashetty,

thank you for your continued support. The first command you suggested gave me this:

.....

"loadBalancerBackendAddressPools": [ { "id": "/subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/backendAddressPools/bepool", "resourceGroup": "QA-BE-AS-Scale" } ],

......

The second command (force-removing the BE pool) produced this error:
unrecognized arguments: --clear backendAddressPools

The third command (check for existing operations) produced a simialr error:
unrecognized arguments: --expand=properties

Yes, I already tried detaching the NAT pool (see my previous large message beginning from the words "As for your next suggestion ("Delete the NAT Pool")") Namely:

You keep suggesting that loadBalancerInboundNatPools is a property of networkInterfaceConfigurations[0], but it isn't:

However, simply adding "ipConfigurations[0]" into the path dosn't help, although the error becomes different:

invalid syntax: --remove property.list <indexToRemove> OR --remove propertyToRemove

Thank you for your advice regarding the way to provide feedback about the Learn website, and of course more generally for your relentless research into my original question, I appreciate it a lot.

anashetty 740 Reputation points Microsoft Vendor

2024-10-09T09:12:36.48+00:00

Hi Sergey Borovoy,

I understand that there is delay in resolving your issue has caused inconvenience to you.

Please try below steps

Run the below command to remove the reference to the backend pool in the VMSS configuration: az vmss update --resource-group QA-BE-AS-Scale --name qa-be-as --remove virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0].ipConfigurations[0].loadBalancerBackendAddressPools "/subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Network/loadBalancers/qa-be-aslb/backendAddressPools/bepool"

After running the above command, verify that backend pool reference is no longer there: az vmss show --resource-group QA-BE-AS-Scale --name qa-be-as --query "virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0].ipConfigurations" Ensure that the loadBalancerBackendAddressPools array is empty.

Once the backend pool reference is removed from the VMSS, you can then delete the backend pool: az network lb address-pool delete --resource-group QA-BE-AS-Scale --lb-name qa-be-aslb --name bepool

To confirm that the backend pool is deleted, run: az network lb address-pool list --resource-group QA-BE-AS-Scale --lb-name qa-be-aslb

Please try below command to check provisioning state of VMSS: az resource show --ids /subscriptions/2c...d5/resourceGroups/QA-BE-AS-Scale/providers/Microsoft.Compute/virtualMachineScaleSets/qa-be-as --query properties.provisioningState

Please try this command to remove the loadBalancerInboundNatPools reference from the VMSS’s ipConfigurations[0]:

az vmss update \ --resource-group QA-BE-AS-Scale \ --name qa-be-as \ --remove virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0].ipConfigurations[0].loadBalancerInboundNatPools

Please try above steps and if you have any queries, please let me know.

Sergey Borovoy 521 Reputation points

2024-10-09T11:34:50.77+00:00

Hi Anashetty,

as I explained in my previous message, the first command does not work:

"...simply adding "ipConfigurations[0]" into the path dosn't help, although the error becomes different:

invalid syntax: --remove property.list <indexToRemove> OR --remove propertyToRemove"

I copied your command just in case I missed something, but the error is still the same.

I also tried running your command without that long Id of the BE pool at the end, i.e. like this:

I think this is the right way to run it because there is no syntax error anymore. Yet the result is the same as we've already seen many times before: *Operation 'Update Virtual Machine Scale Set' is not allowed on Virtual Machine Scale Set 'qa-be-as' since it is marked for deletion.* This also means that the next 3 commands you suggested won't work because they're dependent on the first one. As for the fourth command ("check provisioning state of VMSS"), it shows "**Failed**". The very last command (removing the NAT pool) seems to be the same as the command I used for the BE pool right above, and it produces the same error: *Operation 'Update Virtual Machine Scale Set' is not allowed on Virtual Machine Scale Set 'qa-be-as' since it is marked for deletion.* I really appreciate your efforts and look forward to more advice. Thank you. Sergey

Sergey Borovoy 521 Reputation points

2024-10-09T11:37:15.5533333+00:00

....sorry, formatting got all screwed up in that previous comment of mine. Let me try again:

Hi Anashetty,

as I explained in my previous message, the first command does not work:

"...simply adding "ipConfigurations[0]" into the path dosn't help, although the error becomes different:

invalid syntax: --remove property.list <indexToRemove> OR --remove propertyToRemove"

I copied your command just in case I missed something, but the error is still the same.

I also tried running your command without that long Id of the BE pool at the end, i.e. like this:

az vmss update --resource-group QA-BE-AS-Scale --name qa-be-as --remove virtualMachineProfile.networkProfile.networkInterfaceConfigurations[0].ipConfigurations[0].loadBalancerBackendAddressPools

I think this is the right way to run it because there is no syntax error anymore. Yet the result is the same as we've already seen many times before:

Operation 'Update Virtual Machine Scale Set' is not allowed on Virtual Machine Scale Set 'qa-be-as' since it is marked for deletion.

This also means that the next 3 commands you suggested won't work because they're dependent on the first one.

As for the fourth command ("check provisioning state of VMSS"), it shows "Failed".

The very last command (removing the NAT pool) seems to be the same as the command I used for the BE pool right above, and it produces the same error:

Operation 'Update Virtual Machine Scale Set' is not allowed on Virtual Machine Scale Set 'qa-be-as' since it is marked for deletion.

I really appreciate your efforts and look forward to more advice. Thank you.

Sergey

anashetty 740 Reputation points Microsoft Vendor

2024-10-14T07:22:28.3766667+00:00

Hi Sergey Borovoy,

Thank you for providing information. This issue needs deeper investigation and Azure technical support team will be able to help with this. I would recommend you open an azure support case. If you don't have the ability to open a technical support ticket, please let me know and I can help you further with this.

Thank you.

Sergey Borovoy 521 Reputation points

2024-10-14T14:17:37.95+00:00

Hi Anashetty, yes, I have come to the same conclusion. I believe the resources got inconsistent and can only be removed "surgically" by directly editing the Azure DBs.

I very much appreciate the time you spent on this, and wish you all the best.

anashetty 740 Reputation points Microsoft Vendor

2024-10-15T01:20:16.16+00:00

Hi Sergey Borovoy,

Thanks for your patience, from the above conversation please tell us if anything was helpful to you, so that we can convert it to answer. Then, if you could Accept Answer and Upvote it for the benefit of community, it will be helpful to others.

Thank you
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Unknown error while deleting VMSS

0 additional answers

Your answer