Remove -TenantLevel parameter used for on the Get-AzResourceLock cmdlet

[brucelin-511]

Description

Remove -TenantLevel parameter used for on the Get-AzResourceLock cmdlet to fix the issue of
What is the -TenantLevel parameter used for on the Get-AzResourceLock cmdlet? #11335

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
  • the markdown help files have been regenerated using the commands listed here

[adxsdkps]

Can one of the admins verify this patch?

[isra-fel]

Hi @brucelin-511 , what would happen if the user used -TenantLevel before? The cmdlet returned nothing, or threw an error?

I ask because we cannot check in breaking changes without notifying our customers in advance, unless the function is already broken.

[brucelin-511]

@isra-fel Previously, adding -TenantLevel, it don't throw the error. Actually, the effect of adding it or not, the result is the same. Resource (management) locks are only valid at the Subscription, Resource Group, Resource scopes. TenantLevel should not be a parameter for the command.

[isra-fel]

LGTM