Terraform Fundamentals: What a Beginner Actually Needs to Know
Terraform has a small number of ideas and a large number of commands. Learn the ideas first — desired state, providers, the plan, and the state file — and the commands stop being magic.
Insights
Practical write-ups on the decisions that actually shape a Microsoft cloud estate — the trade-offs, the failure modes and the things worth doing early.
Published
Browse by topic
Landing zones, infrastructure as code and the platform decisions that are expensive to reverse.
Terraform has a small number of ideas and a large number of commands. Learn the ideas first — desired state, providers, the plan, and the state file — and the commands stop being magic.
The choice between Terraform and Bicep is usually argued as a language preference. It is really a decision about state, deletion semantics and how far your infrastructure code can reach.
Identity, access and the gaps that appear in tenant after tenant.
None of these are exotic. They are defaults nobody changed, exclusions that grew, and logs that go nowhere — and the same seven appear in tenant after tenant.
Getting a Microsoft estate ready for enterprise AI, and choosing the right architecture once it is.
Most AI readiness problems are not AI problems. They are identity, data, network and governance debts the estate already carried — and the AI project is simply the first thing that cannot work around them.
RAG and agents are not competing options — one is how a model gets facts, the other is how it decides what to do. Choosing between them starts with whether the task is answered by reading or by acting.
Cost visibility and accountability for cloud and AI workloads.
Cloud FinOps assumes cost follows capacity you provisioned. Enterprise AI breaks that assumption: spend is set by application code and user behaviour, and it grows with adoption rather than shrinking.
Start with a focused assessment of your cloud, security, AI or FinOps environment.