Azure & cloud
Azure infrastructure that stops making deployment an event
A lot of Azure estates grew by hand, one portal click at a time, and work perfectly well right up until somebody needs to change them. Nobody is quite sure what is deployed, releases happen on Thursday so there is a day to fix them, and one person holds the whole picture in their head.
The fix is not usually more infrastructure. It is describing what you already have as code, putting a pipeline in front of it, and making the environments identical enough that testing somewhere safe actually tells you something.
Get in touchWho this is for
- Your Azure setup was built by hand and nobody wants to touch it now.
- Deploying is a manual routine that only one person is comfortable running.
- Your test environment differs from production in ways you discover at the worst moment.
- The Azure bill has grown and nobody can point at exactly what caused it.
What you get
Infrastructure as code
Your environment described in Bicep and kept in version control, so it can be reviewed, rebuilt and reasoned about instead of remembered.
A pipeline that deploys
Build, test and release automated in GitHub Actions or Azure DevOps, with the environments separated and promotion between them boring.
An architecture you can explain
Written down, sized to what you actually run, and without the services that only exist in the reference diagram.
A look at the bill
Which resources are earning their cost, which are oversized, and which have been quietly running since a project that ended.
Related work
Common questions
We are already on Azure but it is a mess. Where do you start?
With a read-only look at what is actually deployed and what it costs, before changing anything. That produces a short list of things worth fixing in order — usually deployment first, because everything else is easier once changes are repeatable.
Do you also handle the migration itself?
For applications, yes — that is the same .NET work I do anyway. For large lift-and-shift programmes across a whole estate, an established partner with a team is a better fit than one person, and I will say so rather than take the work.
Do you work on site on Funen?
Yes. I am based in Odense, so meeting in person anywhere on Funen or in the Triangle Region is straightforward. Most of the actual work happens remotely, which keeps it cheaper for you.