microsoft / microsoft/finops-toolkit

Evaluate FinOps hubs alignment with CAF/WAF guardrails

Open
#2,313 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Tool: FinOps hubs
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

🤖 [AI] Filed from findings raised in discussion #2283.

⚠️ Problem

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with discussion #2283 and the FinOps hub templates, then review the policy-conflict examples in #1067, #2249, and the companion storage-key issue. Compare the templates with common CAF landing-zone policies and WAF pillars. Done means documenting each additional gap and filing targeted follow-up issues rather than changing one isolated policy conflict.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
cloud, infrastructure, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.