Do not confuse historical Microsoft titles with the current role
Microsoft retired its MCSA, MCSD and MCSE exam families, with the remaining examinations ending by January 31, 2021. An older article’s label “MCSD Azure Solutions Architect” should not be treated as a confirmed current Microsoft certification. The modern role-based Microsoft Certified: Azure Solutions Architect Expert path has its own official requirements. For background on the historical change, see Microsoft certification transition. These are different credential eras, not an automatic one-to-one replacement.
Understand the Azure solutions architect’s work
An Azure architect translates business requirements into cloud and hybrid designs. The broader cloud architect role also requires explaining resilience, cost, security and operational trade-offs to decision-makers, not merely attaining a particular exam badge. Key decisions involve identity, governance, monitoring, storage, networking, compute, application architecture and resilience. The role is not limited to choosing the largest virtual machine or writing deployment scripts. A design must explain who will operate the result, how data is protected, the expected failure modes and the constraints on availability and cost.
An Azure solutions architect turns business constraints into an infrastructure design. Start with a fictional transaction service and document expected users, data classification, connectivity, authentication, recovery objectives and cost constraints. Identify which requirements are mandatory and which are preferences. Only then compare managed application hosting with virtual machines, the appropriate data service and the network access path. A design that lists every Azure service is not necessarily a coherent solution.
The architect should explicitly assign operating responsibilities. For example, a managed database can reduce infrastructure administration while application-level authorization, data classification, retention and backup validation still need owners. Describe which team monitors capacity and incidents, how changes are approved and which evidence would show that the proposed architecture meets its service-level requirements.
Confirm the current certification requirements
Microsoft currently requires Azure Administrator Associate certification plus exam AZ-305 to earn Azure Solutions Architect Expert. Passing AZ-305 by itself is not the entire credential path. Microsoft updated the English-language exam on April 17, 2026. Candidates should confirm prerequisites and the current measured skills on Microsoft Learn before scheduling or buying third-party material; old MCSD preparation packages do not establish current eligibility.
Microsoft identifies Azure Administrator Associate as a prerequisite certification for Azure Solutions Architect Expert, with AZ-305 as the required design examination. That is different from the older MCSA, MCSE and MCSD program, which should be treated historically. An aspirant who has architect-level design skill but lacks the required administrator credential should plan the credential sequence and verify the current Microsoft Learn requirements before registration.
Design identity and governance
Begin with tenants, subscriptions, management groups and the intended administrative boundaries. Decide how staff, applications and automation obtain identity and what permissions they need. For a shared platform team, separation of duties may matter as much as technical convenience. A useful exercise compares a broad subscription-owner grant with narrower roles and shows which business risk each option creates.
For governance, map each subscription and resource group to workload ownership, access rules, tagging and policy controls. Test a permitted developer deployment and an unauthorized change to a protected production setting. Microsoft Entra ID, Azure role assignments and Azure Policy answer related but different questions: identity, authorization and allowed resource configuration. Capture the effective denial, not merely the intended diagram.
Choose data and application architecture
An architect must match storage and data services to access patterns, durability, recovery, cost and regulatory needs. For example, a transactional system and a read-heavy analytical dataset may need different consistency and performance characteristics. An application design should identify dependencies, scale limits and operational responsibility; using a managed service does not remove every customer security or data governance task.
Build for failures and recovery
Specify recovery-point and recovery-time objectives before selecting a backup or region strategy. A multi-region design is not automatically resilient if it depends on one global identity or DNS path without a recovery plan. Document backup tests, restore permissions, data replication behavior and the business impact of failover. Check that the design meets the actual availability requirement rather than an attractive but unjustified target.
Business continuity is a design decision about acceptable data loss and restoration time. Given a hypothetical recovery point objective of fifteen minutes and a recovery time objective of two hours, explain what the backup, replication, monitoring and failover tests would need to demonstrate. The example values are design assumptions, not Azure guarantees. A useful design review states what can fail, how operations detect the event and who authorizes a recovery action.
Show cost and operational trade-offs
Compare options using a realistic usage estimate, monitoring needs, maintenance workload and support expectations. Include network egress and recovery costs when they materially affect the design. Establish who reviews policy drift, security alerts, resource saturation and budget anomalies. An architecture that cannot be maintained by the available team may not be suitable even if the technology could meet performance targets.
Architecture choices often involve conflicting requirements. A multi-region deployment may improve resilience but introduce data-residency, replication-cost and operational-complexity questions. A managed service can reduce patching work yet still impose network, identity, monitoring and recovery obligations. In a design review, quantify or qualify these trade-offs and name the team that accepts each residual risk. A cost estimate should state traffic, storage, compute utilization and region assumptions rather than claiming a fixed universal monthly price.
Demonstrate design reasoning
Create a small case study with a user-facing application, sensitive data, two failure scenarios and clear compliance constraints. Propose at least two viable architectures and compare them on security, reliability, operations and cost. State what must be tested before approval. This exercise is closer to the decisions expected of an Azure architect than a generic promise that a retired credential guarantees a cloud career.
A strong portfolio deliverable is a concise architecture decision record: context, alternative designs, chosen approach, risks, expected monthly cost drivers and a verification plan. Add one change in requirements—such as a new residency or availability constraint—and show how the design would adapt. The ability to revisit a defensible decision matters more to the architect role than reciting service names without operational consequences.