Azure / Azure/bicep-registry-modules

[AVM Question/Feedback]: KeyVault - Retirement of API version prior to 2026-02-01 by Feb 27, 2027

Open
#6,879 6 comments 0 reactions 0 assignees View on GitHub
Needs: Core Team :genie: Type: AVM :a: :v: :m: Type: Question/Feedback :raising_hand:
Dominant language
Bicep
Stars
736
Forks
564
Avg merge
3d 15h
Merged PRs (30d)
30

Description

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Description

On 9 February 2026, Microsoft announced that on 27 February 2027, all Azure Key Vault API versions prior to 2026-02-01 will be retired. Refer to [the documentation](https://learn.microsoft.com/en-us/azure/key-vault/general/access-control-default) for more information.

Is this work on AVM's radar?

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start with the linked Azure Key Vault API retirement documentation, then identify which AVM modules use the affected API versions. Done would require a defined update scope and confirmation that affected modules support API version 2026-02-01.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.