Skip to content

Update Key Vault to Support RBAC Permissions and Delete Protection #1067

Description

@AErmie

⚠️ Problem

For organizations that utilize the Enterprise Scale in association with the Cloud Adoption Framework (CAF), there are various Azure Policies and Initiatives that are deployed.

One of those Initiatives is the Enforce recommended guardrails for Azure Key Vault. This initiative contains several policies, including:

  • Azure Key Vault should use RBAC permission model
  • Key vaults should have deletion protection enabled

The current deployment of the FinOps Toolkit (Hub architecture), violates those 2 policies and prevents its deployment. We have to add/create an exception in the target Subscription / Resource Group, for the deployment to complete successfully.

🛠️ Solution

Update the FinOps Toolkit's Key Vault implementation to support the RBAC permissions model, and also enable delete protection.

ℹ️ Additional context

The client I am currently assisting, is in a regulated industry, and uses the CAF / Enterprise Scale Terraform modules.

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.

Activity

  1. flanakin commented on Oct 23, 2024

    @flanakin
    Collaborator

    Makes sense. I'm not familiar with these options, but we can probably look at this in December. If you're familiar with bicep and would like to see this sooner, we'd welcome a PR to add this. Or if you know the settings that need to be applied, you could share them here, which might speed things up. Just let us know.

    Either way, thanks for the feedback!

  2. flanakin commented on Oct 23, 2024

    @flanakin
    Collaborator

    allcontributors[bot] (@allcontributors) please add AErmie for feature

  3. allcontributors commented on Oct 23, 2024

    @allcontributors
    Contributor

    Michael Flanakin (@flanakin)

    I couldn't determine any contributions to add, did you specify any contributions?
    Please make sure to use valid contribution names.

  4. AErmie commented on Oct 29, 2024

    @AErmie
    CollaboratorAuthor
  5. ankurshukla03 commented on Feb 28, 2025

    @ankurshukla03

    #1349 - Added the PR request to enable purge protection for the keyvault as per this issue

  6. 2 remaining items

  7. added 3 commits that reference this issue on Oct 23, 2026
    562429c
    f95f3b2
    4a074e7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions