You don't need to read Terraform to know whether your cloud estate is in good shape. Ask a few plain questions and listen for hesitation. Vague answers usually mark the risky areas.
Here are the five I'd start with.
| Question | A confident answer | A worrying answer |
|---|---|---|
| 1. If we lost the whole environment tonight, how long to rebuild it? | Hours, and someone can show you the repository that proves it | Weeks, because much of it is in one person's head |
| 2. Who can delete production, and what stops them doing it by accident? | A resource lock: production refuses deletion until someone removes the guard on purpose | "Nobody would" |
| 3. Can we show an auditor a rule enforcing itself? | A policy assigned in the platform, with compliance evidence as a side effect | A document saying the rule should be followed |
| 4. When spend jumps, do we hear it from an alert or from the invoice? | A budget alert at 80%, so you react this week | The invoice, after the money has gone |
| 5. If our lead cloud person left on Friday, what breaks on Monday? | Nothing much: the work is as code, reviewed in pull requests | One named person |
What the answers tell you
The gap between hours and weeks on question 1 is a big part of what "cloud maturity" means; Infrastructure as Code, explained is the fuller version.
On question 2, Stop someone deleting prod shows how cheap a lock is. On question 3, a policy that only exists in a slide deck enforces nothing.
On question 5, a single name in the answer is a single point of failure in your architecture.
None of these need a technical answer from you; your team has to give the answer. If more than one draws a pause, start the next conversation there.
Next: when Azure's fancier network option is worth paying for, and when it isn't.