How do you manage Azure Resource Graph queries once they stop being ad hoc?
I use Azure Resource Graph when I need a quick view across Azure resources. Writing the first query is usually straightforward. The awkward part starts when that query becomes something a team depends on.
Where do you keep those queries? Saved in Resource Graph Explorer, stored in Git, embedded in PowerShell or CLI scripts, or presented through Workbooks?
And once they are running regularly, how do you handle scheduling, history, exceptions, and making sure somebody acts on the results?
I have seen useful queries gradually turn into scripts that only one person understands. I am curious what has held up well for other teams, especially when more than one person is responsible for Azure governance.
u/abd0hanafy — 6 days ago