Azure Solutions Architect Study Plan

A workable AZ-305 study plan divides Microsoft's four design domains — identity, governance and monitoring; data storage; business continuity; and infrastructure — into focused blocks, and spends most of its time converting the services you already administer into design decisions you can defend. This article lays out that plan week by week: what to study, in what order, with which official resources, and the milestones that tell you whether you are on track.

Two facts shape everything that follows. First, AZ-305 (Designing Microsoft Azure Infrastructure Solutions) is a design exam, not an implementation exam — it asks which solution fits a set of requirements, not how to click through deploying it. Second, the Azure Solutions Architect Expert certification has a hard prerequisite: you must hold the Azure Administrator Associate (AZ-104) certification, because passing AZ-305 alone does not award the expert credential. Your plan has to account for both.

Before week one: confirm you're starting from the right place

AZ-305 assumes you can already operate Azure. Microsoft's expert-level positioning expects advanced experience across IT operations — networking, virtualisation, identity, security, business continuity, data platforms and governance — and the exam questions presume that vocabulary is second nature.

Run through this pre-flight checklist before committing to a start date:

1. AZ-104 status. If you don't yet hold Azure Administrator Associate, plan that first — the expert certification will not be issued without it. The AZ-104 Microsoft Azure Administrator exam page and our full Azure Administrator certification guide cover that exam in depth.
2. Hands-on baseline. You should be comfortable in the Azure portal, CLI or PowerShell, and familiar with core services (virtual networks, storage accounts, Microsoft Entra ID, Azure Monitor). AZ-305 will not reteach them.
3. Renewal awareness. Like all Microsoft role-based certifications, Azure Solutions Architect Expert is valid for one year and renews free through an online, open-book assessment on Microsoft Learn — so your plan is building for a credential you maintain annually, not a one-off sprint.
4. The current study guide. Download the official AZ-305 study guide from Microsoft Learn before anything else. The exam's English version was updated in April 2026, and the study guide is the authoritative statement of what is currently assessed.

If you're still weighing whether the expert credential justifies this effort at all, that value question has its own answer in Is the Azure Solutions Architect certification worth it?

How long should the plan run?

Microsoft publishes no official study-hours figure for AZ-305, and any blog that promises "X hours guarantees a pass" is guessing. Preparation time depends almost entirely on how much architectural decision-making you already do at work.

This article uses an eight-week frame because it maps cleanly onto the four exam domains — roughly a fortnight each, with review woven through. Adapt it honestly:

• Compress to 4–5 weeks if you already design Azure solutions daily and mostly need to align your instincts with Microsoft's recommended patterns (the Well-Architected Framework and Cloud Adoption Framework).
• Stretch to 10–12 weeks if your experience is deep in operations but thin in design — you can build anything asked of you, but rarely choose between competing options against cost, resilience and governance requirements.

The plan below assumes five to eight focused hours per week. Consistency beats volume: three ninety-minute sessions weekly will outperform one exhausted Saturday.

The eight-week AZ-305 study roadmap

Each fortnight pairs one exam domain with a repeating rhythm: learn the design options, then interrogate them. For every service you study, force yourself to answer three questions — when would I choose this over its alternatives, what requirement rules it out, and what does it cost relative to those alternatives? That interrogation, not memorisation, is what AZ-305 rewards.

Weeks 1–2: Design identity, governance and monitoring solutions

Start here because identity and governance decisions constrain every other design on the exam.

• Identity and access: Microsoft Entra ID design choices — hybrid identity and authentication approaches, B2B/B2C scenarios, conditional access strategy, managed identities versus service principals, and when each fits.
• Governance: management group and subscription hierarchy design, Azure Policy versus role-based access control (understand which problem each solves), resource tagging strategy, and landing-zone thinking from the Cloud Adoption Framework.
• Monitoring: designing a logging and monitoring strategy with Azure Monitor, Log Analytics workspaces (one or many, and why), and how monitoring requirements differ between applications, platforms and security teams.

Milestone check: given a fictional company with three subsidiaries and separate compliance regimes, sketch a management group hierarchy and justify where policies and role assignments attach. If you can narrate the trade-offs aloud, move on.

Weeks 3–4: Design data storage solutions

This domain trips up operations-focused candidates because it demands comparative knowledge of services many administrators only touch occasionally.

• Relational choices: Azure SQL Database versus SQL Managed Instance versus SQL Server on virtual machines — build a mental decision tree keyed to compatibility, management overhead and scalability requirements.
• Non-relational choices: when Azure Cosmos DB earns its place, storage account tiers and redundancy options, and matching access patterns to blob, file, table and queue storage.
• Data integration: at design level, know what the analytics and integration services are for and when an architect would recommend them, without descending into data-engineering depth.

Milestone check: write out, from memory, the storage redundancy options and the scenario that would justify each. Then pick any two database services and argue both sides of a migration decision between them.

Weeks 5–6: Design business continuity solutions

The shortest domain on paper, but it punishes vague understanding, because every question hinges on precise requirements.

• The vocabulary of resilience: recovery time objective (RTO) and recovery point objective (RPO) drive nearly every business-continuity design decision — practise reading requirements and extracting them.
• Backup design: Azure Backup capabilities across virtual machines, databases and files; retention and vault design; how backup differs from disaster recovery, and when a scenario needs one, the other or both.
• High availability: availability zones versus availability sets versus region pairs; designing for platform-level resilience in compute, database and storage tiers; Azure Site Recovery's role in disaster recovery design.

Milestone check: take three imagined workloads — a tolerant internal app, a customer-facing e-commerce platform, a regulated financial system — and assign each an availability and recovery design. If all three answers look the same, revisit the fortnight.

Weeks 7–8: Design infrastructure solutions, then integrate everything

The broadest domain, and deliberately last: it draws on everything before it.

• Compute: choosing between virtual machines, App Service, Azure Kubernetes Service, container instances and serverless options against requirements for control, scale, cost and operational maturity.
• Application architecture: messaging and eventing choices, API management, caching, and designing for automated deployment.
• Networking: hub-and-spoke topologies, hybrid connectivity options, load-balancing services and their selection criteria, and private connectivity to platform services.
• Migrations: assessing and planning moves of servers, databases and unstructured data into Azure.

Reserve the final few days of week 8 for cross-domain integration. Real AZ-305 scenarios never sit inside one domain — a single case can touch identity, storage, resilience and networking at once — so close the plan by designing complete solutions end to end, not by rereading notes.