[CLI/PS] KeyVault API versions before 2026-02-01 will be retired- Reference doc reminder message

[Alex-AZPS]

Warning: Azure Key Vault API versions earlier than 2026-02-01 are being retired.

 

Azure CLI Reference Documentation Warning
Proposed Warning Message

Warning

Azure Key Vault API versions earlier than 2026-02-01 are scheduled for retirement and may stop working after the retirement date.

Support for Key Vault API version 2026-02-01 was introduced in Azure CLI 2.90.0. We strongly recommend upgrading to Azure CLI 2.90.0 or later and migrating to API version 2026-02-01 or later as soon as possible.

For supported versions and migration guidance, see:

Supported API versions: https://review.learn.microsoft.com/en-us/azure/key-vault/general/access-control-default?branch=main&branchFallbackFrom=pr-en-us-2074&tabs=azure-cli

Azure PowerShell Reference Documentation Warning
Proposed Warning Message

Warning

Azure Key Vault API versions earlier than 2026-02-01 are scheduled for retirement and may stop working after the retirement date.

Support for Key Vault API version 2026-02-01 was introduced in Azure PowerShell 16.3.0. We strongly recommend upgrading to Azure PowerShell 16.3.0 or later and migrating to API version 2026-02-01 or later as soon as possible.

For supported versions and migration guidance, see:

Supported API versions: https://review.learn.microsoft.com/en-us/azure/key-vault/general/access-control-default?branch=main&branchFallbackFrom=pr-en-us-2074&tabs=azure-cli

[yonzhan]

Thank you for opening this issue, we will look into it.

[isra-fel]

General mindset:

1. add a clips section to https://review.learn.microsoft.com/en-us/azure/key-vault/general/access-control-default?branch=main&branchFallbackFrom=pr-en-us-2074&tabs=azure-cli and use it as source of truth. Link it (shortlink) from everywhere else.

Notes:

1. Use clips version instead of api version in our cx facing messages

[isra-fel]

Need to work with Q squad to put the universal banner message in ref docs

[microsoft-github-policy-service]

🔔 Routing this issue to @Azure/act-identity-squad.

[x-engineering-agent]

Hi — before we can implement a fix in the azure-cli codebase, we need a bit more clarity on what code change is expected. The issue body describes a warning message for the reference documentation on learn.microsoft.com, but that content lives outside this repo. Could you clarify:

1. Runtime warning: Should az keyvault (or sub-commands like az keyvault key, az keyvault secret, az keyvault certificate, etc.) emit a runtime deprecation warning to users running CLI versions older than 2.90.0 or using an older API version? If so, which commands and what exact message text?
2. CLI help text: Should a deprecation notice be added to the command help strings (e.g., az keyvault --help)? Which commands?
3. Minimum version gate: Is the CLI expected to block calls that would hit pre-2026-02-01 API versions, or only warn?
4. Already addressed: Since CLI 2.90.0 already supports API version 2026-02-01, is there a remaining code gap, or is this purely a documentation/reference-doc task handled by the Q squad outside this repo?

We'll pick this up automatically once the scope is clarified.