You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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:
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:
The text was updated successfully, but these errors were encountered: