Azure architecture and cost review
Find out whether your Azure environment is built to run, and what it should cost.
Azure environments built quickly during a migration tend to drift: spend grows, exceptions pile up and nobody is sure the design still holds. In two to three weeks we review the architecture and the bill together, because most cost problems start as design problems.
Who it is for
Organisations already running production workloads in Azure whose spend or structure has drifted, who have inherited an environment built by someone else, or who are about to put more on it and want the foundations checked first.
What we examine
- Landing zone: management groups, subscriptions, Azure Policy and the exceptions to it
- Network: hub and spoke design, hybrid connectivity, DNS, private endpoints and outbound paths
- Identity for the platform and for workloads: privileged roles, service principals and managed identities
- Operations: logging, monitoring, backup coverage and how changes are made
- Cost: allocation and tagging, idle and over-sized resources, storage tiers, licensing benefits and commitment coverage
What you receive
- Architecture findings, ranked by risk, with the evidence for each
- Cost opportunities, each with the effort, the risk and what it depends on
- A remediation backlog your team or ours can work through
- Recommendations for reservations and savings plans, sized to what you will keep running
What we need from you
- Reader and Cost Management Reader access to the subscriptions in scope
- About two hours of your team's time across a kick-off and the readout
- An introduction to whoever approves Azure spend
How it runs
- Scoping: subscriptions in scope and the questions the review has to answer.
- Review: configuration, cost data and operational process examined against how the environment is used.
- Readout: findings and the backlog walked through with your team, then finalised.
What happens next
Quick savings can often be made straight away. Design fixes are delivered as Transformation Engineering, and ongoing governance and cost work can move into Managed Engineering so the environment stays in shape.
Questions buyers ask
Will you make changes during the review?
No. The review uses read-only access. Changes are made afterwards, through your change process, once you have agreed the backlog.
Do you take a share of the savings?
No. The review is a fixed fee agreed after scoping, so the recommendations are not shaped by how we are paid.
We use a cost management tool already. Is this still useful?
Yes. Tools show where money goes. The review explains why, which fixes are safe, and which spend follows from design decisions that need changing.
Do you review GCP or AWS?
Our focus is Azure and hybrid estates. We can review GCP alongside Azure where both are in use.
Can we use the results with another provider?
Yes. Findings and the backlog are yours to use with anyone.
Start a conversation
Get the Azure bill and the architecture telling the same story.
Tell us what you would like the review to answer.
Talk to an Engineer