How to run an Azure architecture review

Start with scope, not tooling

The quality of an Azure architecture review is shaped early by the scope. Decide which subscriptions, landing zone structures, and shared services are genuinely in play before trying to score or report anything.

Review structure matters

A good review maps resource evidence to the five Azure Well-Architected pillars in one coherent model. Otherwise the output becomes a bundle of disconnected observations.

The output has to stand up in a meeting

The report is not just a delivery artifact. It is the thing that carries the review into stakeholder discussion. That means it needs evidence, architecture context, and readable prioritisation.