Open
Conversation
|
@Chakradhar886 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
jayesh-tanna
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR explicitly sets:
enable_rbac_authorization=False
while creating the Azure Key Vault.
Why this change is needed:
Recent failures were observed after upgrading the Azure Management Key Vault SDK from v13 to v14.
Although public documentation suggests that RBAC authorization defaults remain unchanged when the value is not specified, actual behavior changed in v14.
As confirmed during discussion and a local PoC:
In SDK v13, Key Vault creation worked without explicitly setting enable_rbac_authorization
In SDK v14, when this value is not explicitly set, Key Vault access fails during runtime
Explicitly setting enable_rbac_authorization=False restores the earlier, working behavior
Jayesh validated this by running a local PoC comparing SDK v13 vs v14 behavior, and confirmed that explicitly disabling RBAC authorization is the correct and minimal fix.
Checklist