Automated vs Manual vs Consultant: Three Ways to Run an Azure Architecture Assessment
Automated, manual self-assessment, and consultant-led: three ways to run an Azure architecture assessment compared on time, cost, depth, and currency. For CTOs and VPs of Engineering.
Marc Dekeyser |
Automated vs Manual vs Consultant: Three Ways to Run an Azure Architecture Assessment
Three honest ways to run an Azure architecture assessment. One spits out findings in hours. One is a free questionnaire you fill in yourself, the Microsoft Azure Well-Architected Review. One is a consultant you pay to come in and look.
They mostly differ on speed, cost, and how long the answer stays true. And on judgment: a senior consultant reads business context that no tool can.
People frame this as automation versus humans. Wrong question. The one that matters is which method fits the decision in front of you, the budget you actually have, and how often the answer needs to be refreshed. Each of the three is genuinely the best at one thing.
The three methods
Automated assessment points tooling at the environment (or its definition) and generates findings against the Microsoft Azure Well-Architected Framework. Manual self-assessment is your own team working through a structured questionnaire, usually the free Well-Architected Review: roughly 60 questions across the five pillars. Consultant-led is a human, or a team of them, poking at the architecture, interviewing your people, and writing it up.
Different outputs, not different grades of the same output. Automation gives you consistent, repeatable findings. The questionnaire gives you a self-scored snapshot. A consultant gives you interpreted recommendations shaped by your context. None wins outright. They answer different questions.
How the three compare
Read the table, then read the paragraph under it. The paragraph is the part people skip and shouldn’t.
| Dimension | Automated assessment (e.g. PAA) | Manual self-assessment (Well-Architected Review) | Consultant-led engagement |
|---|---|---|---|
| Time to first output | Hours | Days (a workshop) | Weeks |
| Typical cost | Low, transparent (EUR 99–799/mo) | Free | High, contact-us (often five figures) |
| Currency over time | Continuous; re-runs cheaply | Stale once architecture changes | Point-in-time snapshot |
| Depth of judgment | Bounded by what tooling observes | Bounded by the team’s own knowledge | Deepest; contextual and strategic |
| Consistency | Deterministic, repeatable | Varies with who answers | Varies with the consultant |
| Compliance mapping | Per-finding to NIS2/DORA/ISO/SOC 2 | Not built in | Yes, if scoped (and priced) |
| Remediation output | Generated Terraform / Bicep | Guidance only | Tailored recommendations |
| Best at | Breadth, currency, drift detection | Free structured starting point | Context, strategy, hard trade-offs |
Here is the part the table can’t hold. A senior consultant is the only one of the three who can weigh business context (a planned acquisition, a regulatory deadline, how operationally mature your team really is) and tell you which of ten findings actually matters this quarter. Automation can’t do that. It never will. What automation does that no consultant will is run again next week, and the week after, at the same low cost, catching the drift that quietly makes every point-in-time assessment a lie.
Picking one
Match the method to how often the answer has to be right, not just how deep you want it once. Three patterns cover most of what I see.
Automated assessment when you need findings fast, repeatedly, and mapped to compliance frameworks. Before a board update. During due diligence. On a platform that changes every sprint. It is quick and it stays current. It also only surfaces what tooling can observe, and it will never infer the strategy you never wrote down.
The manual Well-Architected Review when you want a free, structured way to start the conversation inside the team. Zero cost, first-party framing, good for getting everyone speaking the same language. The catch is that it is self-reported. A team that doesn’t know what it doesn’t know scores itself generously, and the score is stale by the next deploy.
A consultant when the decision is big and context-heavy: a re-platforming, a major architectural bet, a fight between cost and resilience where someone has to actually call it. You are buying judgment. You pay for it in money, in lead time, and in the fact that the report describes the architecture as it stood on the day, not as it stands six months later.
For a structured framing of what an assessment should cover, see our Azure architecture governance checklist, and for one pillar in depth, the Well-Architected security pillar walkthrough.
Compete or complement?
They complement each other far more than they compete, because each one covers where the others are weakest. The pattern that works: run automated assessment continuously to hold the line on breadth and drift, use the free Well-Architected Review to get the team aligned on language and priorities, and bring in a senior consultant for the handful of decisions where judgment changes the outcome. Automation makes that consultant worth more. They spend their hours on interpretation and trade-offs instead of on inventory and box-ticking the tooling already finished.
That is where PAA sits, and I’ll say it plainly. It’s the automated, continuous option: all-five-pillar Azure and Microsoft 365 review, deterministic compliance mapping, generated Terraform or Bicep remediation you apply yourself, drift detection between runs. It does not replace a senior architect’s judgment. It’s read-only. It proposes changes; it does not make them. It’s the layer that keeps the assessment true in the long stretches between the moments a human looks closely.
FAQ
Is an automated Azure architecture assessment as good as a consultant? No, and it is not trying to be. Automation is faster, cheaper, and stays current, but a senior consultant brings contextual judgment and strategic interpretation that tooling cannot. They answer different questions. The strongest approach uses automation for breadth and currency and a consultant for high-stakes, context-heavy decisions.
Is the Microsoft Azure Well-Architected Review free? Yes. The Well-Architected Review is a free, first-party self-assessment of roughly 60 questions across the five pillars. Its weakness is not cost but reliability: it is self-reported, so its accuracy depends on the knowledge and honesty of the people answering, and it goes stale as the architecture changes.
How often should an architecture assessment be refreshed? As often as the architecture changes materially, which for an active platform is continuously. This is the core weakness of manual and consultant assessments: they are point-in-time. Automated assessment with drift detection is the only method that refreshes cheaply enough to stay current between major reviews.
Can automated assessment map findings to NIS2 and DORA? Yes. Automated assessment tools can map each finding to control frameworks deterministically — the same input yields the same mapping every time. Manual self-assessment does not include this, and consultant engagements include it only when scoped and priced for it. Deterministic mapping is what makes findings auditable.
Does automation produce remediation, not just findings? Some automated tools generate remediation as infrastructure-as-code — Terraform or Bicep you review and apply. This is a meaningful difference from the manual review, which gives guidance only. The code still needs human review before it is applied; automation proposes, it does not silently change your environment.
The short version
- Automated assessment produces findings in hours and stays current with continuous re-runs. Depth is capped by what tooling can observe.
- The Microsoft Azure Well-Architected Review is free and structured, but manual and self-reported. Its accuracy is only as good as the honesty and knowledge of whoever fills it in.
- A consultant brings the deepest contextual judgment and strategic interpretation, at the highest cost, as a point-in-time snapshot.
- Currency is where they split hardest. Automation re-runs cheaply; manual and consultant assessments go stale the moment the architecture moves.
- They complement each other. Automation holds breadth and drift, a senior architect holds judgment.
The right answer is rarely one method. It’s automation holding the line on breadth and currency, a free questionnaire aligning the team, and a senior architect spending scarce judgment where it actually moves the decision.
