// Infrastructure automation
Making infrastructure changes repeatable with Terraform
I use automation to make infrastructure easier to understand, safer to change and less dependent on manual effort. The goal is not automation for its own sake; it is better delivery and calmer operations.
Why this matters to me
My career began in hands-on support and systems administration, where a small inconsistency could become a difficult incident for users and engineers alike. That experience still shapes how I approach cloud automation today: the code needs to work for the delivery team, the support team and the organisation that depends on it.
At Trident Energy, I have helped establish Infrastructure as Code practices using Terraform and ARM templates to standardise cloud provisioning. I also use PowerShell to reduce repetitive operational work and create practical tooling for the people responsible for day-to-day management.
Code as a shared record of intent
Terraform gives teams a reviewable description of the infrastructure they intend to operate. Clear modules, environment boundaries, naming and variable conventions make it easier to see what exists, why it exists and what a proposed change will do before it reaches production.
I favour patterns that are understandable over patterns that are merely clever. A platform should be maintainable by the next engineer, not just by the person who first built it.
Build governance into the delivery path
Plans should be reviewed before they are applied, with access controls, policy guardrails and cost visibility built into the workflow. Pairing provisioning with Azure governance, RBAC and monitoring means a new resource starts its life with the right operational context rather than becoming a later cleanup task.
- Terraform and ARM templates for consistent Azure provisioning
- PowerShell for operational automation, monitoring and remediation tasks
- Reviewable change paths that support security, accountability and delivery pace
- Documentation and handover that help teams operate what they build
Automation should improve operations
The most valuable automation reduces drift, shortens recovery time and frees engineers to focus on the work that needs judgment. I combine platform automation with monitoring, alerting and clear ownership so that the outcome is not simply faster provisioning, but more reliable infrastructure.
Explore my experience, or start a conversation about your next infrastructure programme.
Read next: Building Azure foundations that support delivery →