Remove-AzResourceLock not working: Error: could not be found.

[Raag007]

Description

Hi, team - starting from today, Remove-AzResourceLock command is not working, we have been using this same command for the last couple of years.

Below is the command and exception:

Remove-AzResourceLock -LockName "NoDelete" -ResourceGroupName d1a -Force

Remove-AzResourceLock : The resource lock 'd1a/providers/Microsoft.Authorization/locks/NoDelete' could not be found.

Issue script & Debug output

n/a

Environment data

PSVersion                      5.1.22621.4391
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.4391
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Module versions

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     4.0.2      Az.Accounts                         {Add-AzEnvironment, Clear-AzConfig, Clear-AzContext, Clear-AzDefault...}
Script     7.9.0      Az.Resources                        {Export-AzResourceGroup, Export-AzTemplateSpec, Get-AzDenyAssignment, Get-AzDeployment...}
Script     4.1.1      Az.ServiceBus                       {New-AzServiceBusAuthorizationRuleSASToken, Test-AzServiceBusNameAvailability, Approve-AzServiceBusPrivateEndpointConnection, Complete-AzServiceBusMigration...}

Error output

Remove-AzResourceLock : The resource lock 'd1a/providers/Microsoft.Authorization/locks/NoDelete' could not be found.
At line:1 char:1
+ Remove-AzResourceLock -LockName "NoDelete" -ResourceGroupName ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Remove-AzResourceLock], PSInvalidOperationException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.RemoveAzureResourceLockCmdlet

[isra-fel]

Hi, as you said, "we have been using this same command for the last couple of years", what could have changed? Did you updat ethe version of azure powershell?

Also, sharing the debug log can help up diagnose the issue