Deciding whether an Azure workload can go live

The date usually arrives before the certainty does. A launch is booked, operational ownership passes to another team, an acquisition hands the estate over, or a second incident turns the first one into a pattern.

An engineer runs a free assessment to see where things stand and gets a score. The score travels well: it fits in a message and it sounds like an answer. Then somebody has to sign, and finds that the score does not cover the questions the signature is actually about.

• Most of the framework. At least 40 of Microsoft's 59 checklist recommendations cannot be read off a machine, leaving at most 19 that can - whether failure-mode analysis was done, whether data is classified, whether segmentation was deliberate, whether recovery targets match what the business can carry
• Whether a gap is a blocker. Severity in the abstract is not the same as must-close-before-the-date, which depends on the flows in scope and the operational requirements the workload has to meet
• Whether a tradeoff is a fault. Microsoft's framework says plainly that tightening one pillar costs another; a scan marks a deliberate decision as a failure
• Whether a recovery claim is true. From outside, an untested recovery plan and a tested one look identical
• What actually moved. Without a dated baseline, a later reading cannot show whether anything changed or only the signal did

The person who signs it - normally a head of platform or an engineering director. Whoever is accountable for the workload once it carries real traffic, and whoever will be asked afterwards what they knew at the time.

Where operational ownership is changing hands, the receiving team's owner belongs in the decision too: they inherit everything that is not fixed before the date. The engineer who ran the assessment supplies evidence and does not carry the consequence, which is the whole reason this note exists as something to forward rather than something to act on.

An Azure Well-Architected Review: one bounded workload, read-only access, and an engineering readiness recommendation for a named date. All 59 checks judged against your estate with the evidence for each, release or handover blockers separated from work that can follow the date, a prioritised backlog with owners, effort and acceptance conditions, and a dated baseline so a later review can show what moved.

You keep the launch decision; the review supplies the case for it. Remediation is quoted separately, and the backlog is yours to use with any delivery team.

Read what the review covers