An AI agent can create a billable Azure resource in one line. The only brake most setups have is you, reading every command before it runs, every time, forever.
I stopped trusting that brake the day it worked exactly as designed.
The approval was a conversation, not a control
I was measuring the small file problem on disk and in Azure . The Azure half needed a storage account, so Claude Code and I talked through a cost plan first. I said yes in chat. Then it created a resource group and a storage account.
Nothing went wrong. That's the uncomfortable part. My "yes" was a sentence in a conversation. Nothing in the tooling connected that sentence to the commands that followed. If the plan had drifted, a bigger SKU, a second account, a cluster instead of a bucket, the same sentence would have covered it.
Photo by fsefefs sefesfesfesf on Unsplash
The bill arrives after the damage
The usual answer is "set a budget alert." A budget alert is an email.…