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
{{ message }}
Repository navigation
Evaluate FinOps hubs alignment with CAF/WAF guardrails #2313
We've fixed individual CAF/landing-zone policy conflicts reactively as they're reported (Key Vault RBAC — #1067/#2249; storage shared-key access — see companion issue filed alongside this one). There's likely a broader set of CAF/WAF (Cloud Adoption Framework / Well-Architected Framework) guardrails and built-in Azure Policies the hub templates don't yet account for.
🛠️ Solution
Do a systematic pass evaluating FinOps hub templates against common CAF landing-zone policies and WAF pillars, and file targeted issues for any additional gaps found, rather than continuing to fix these one at a time as customers hit them.
ℹ️ Additional context
Prompted by discussion #2283 and the pattern seen across #1067 and the storage-key issue — both are "policy X blocks deployment" reports.
Activity