Skip to content

"az keyvault update" not working in Azure China after upgrading to 2.40.0 #23888

@jonathanzhang02

Description

@jonathanzhang02

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

% az keyvault update  --resource-group "xxxxxxx"  --name "xxxxxx"  --default-action Deny
(NoRegisteredProviderFound) No registered resource provider found for location 'chinaeast2' and API version '2022-07-01' for type 'vaults'. The supported api-versions are '2015-06-01, 2016-10-01, 2018-02-14-preview, 2018-02-14, 2019-09-01, 2021-04-01-preview, 2021-06-01-preview, 2021-10-01, 2021-11-01-preview'. The supported locations are 'chinanorth, chinaeast, chinanorth2, chinaeast2, chinanorth3, chinaeast3'.
Code: NoRegisteredProviderFound
Message: No registered resource provider found for location 'chinaeast2' and API version '2022-07-01' for type 'vaults'. The supported api-versions are '2015-06-01, 2016-10-01, 2018-02-14-preview, 2018-02-14, 2019-09-01, 2021-04-01-preview, 2021-06-01-preview, 2021-10-01, 2021-11-01-preview'. The supported locations are 'chinanorth, chinaeast, chinanorth2, chinaeast2, chinanorth3, chinaeast3'.

Describe the bug
The command az keyvault update --resource-group "xxxxxxx" --name "xxxxxx" --default-action Deny display error message like above after upgrade az to version 2.40.0

To Reproduce
az version 2.40.0 and az keyvault update --resource-group "xxxxxxx" --name "xxxxxx" --default-action Deny

Expected behavior
The command should work on that az version

Environment summary
az command from containerized debian system

Additional context
Please at least give suggestion similar to what was provided in #22735

Metadata

Metadata

Assignees

Labels

Auto-AssignAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamKeyVaultaz keyvaultact-identity-squadcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions