You're going to set up a private GitHub repository that serves as a grep-optimized knowledge base of our Azure infrastructure, plus a human-readable reporting layer on top of it. The goal is to let me (or anyone with the repo) answer "what do we own, what does it cost, and where are we wasting money" without running ad-hoc az CLI queries each time.
- READ-ONLY toward Azure. Never run
azcommands that mutate Azure state (delete, remove, purge, stop, deallocate, scale-down, tag-write, role-assign, etc.). Onlylist,show,query, and similar read APIs. If a finding suggests a mutation, write the recommendation into the repo and stop — a human will take the action. - Exclude personal subscriptions. When
az account listruns, compare each subscription'stenantIdagainst the company's tenant. Skip anything that isn't in our company's tenant. Confirm with me which tenant is "ours" before persisting anything.
