From Azure Administrator to Architect: What Changes

Moving from Azure administration to solution architecture is not simply a matter of sitting a more difficult exam. The administrator is responsible for making resources behave correctly today. The architect must justify why those resources, dependencies, security boundaries and recovery options are appropriate before and after they are deployed. That change in accountability explains the difference between AZ-104 administration and AZ-305 architecture design.

The credential relationship is specific: Microsoft Certified: Azure Solutions Architect Expert requires an active Azure Administrator Associate certification plus passing AZ-305. An AZ-305 exam pass alone does not issue the Expert credential. Candidates should check the current Microsoft Learn certification page before scheduling or claiming the designation. This guide addresses the professional transition: how to turn administrator experience into architecture evidence over roughly three stages, not another side-by-side exam-domain table.

First, choose one system whose operations you already understand

Start with an application you have supported, ideally one with a real user journey, stored data, identity restrictions, external dependencies and a meaningful recovery requirement. A useful training substitute is a small internal request-tracking application. It accepts requests, stores them in a database, sends notifications, and serves staff in more than one office. Its owner cannot tolerate lost requests, wants predictable operating cost, and expects administrators to recover from routine faults without emergency redesign.

As an administrator, write down how the environment works: subscriptions and resource groups, identities and permissions, virtual networks and name resolution, compute and storage choices, monitoring, backups, deployment method and current support responsibilities. Include the most recent incident and what evidence resolved it. This inventory is your operational baseline—not an architecture proposal yet.

Then ask for the requirements that were missing from the runbook. What recovery time is actually acceptable? Must information remain in one region? Which users can see which requests? What is the expected growth pattern? What is the budget tolerance during a regional failure? An architect cannot choose redundancy, a service tier or a network topology responsibly without knowing those constraints.

Stage one: translate operational tickets into design questions

Take three recurring incidents and write the design question behind each. Suppose an application once lost access to storage after a role assignment changed. The administrator’s task was to restore permission. The architect’s question is whether the identity model prevents accidental privilege growth while still allowing necessary work. Separate role assignments, management-plane actions and data-plane access, and document which principals are authorized at each layer.

In Azure, Azure Policy and Azure RBAC serve different purposes. Policy evaluates or enforces resource conditions; RBAC governs which identities may perform actions. Resource locks protect against certain management operations but are not equivalent to authorization or data protection. Build a simple table: requirement, control, owner, evidence of enforcement, and failure that would invalidate the design.

Now repeat the exercise for networking. A support ticket might say that a private service is unreachable. The administrator checks DNS, route tables and network security rules. The architect needs to decide whether direct connectivity, VNet peering, a hub-spoke topology, managed ingress, or another pattern best fits segmentation and operational responsibility. Peering does not automatically provide transit routing, and a drawn connection does not demonstrate that clients can resolve or reach a private endpoint. Map the entire traffic path, including return traffic and identity where applicable.

Finish stage one with a traceable requirement-to-control map for the chosen application. Each design assumption needs an owner and an observable validation method. An attractive diagram with no measurable acceptance condition is not yet a proposal.

Stage two: compare alternatives instead of configuring the first familiar product

Choose three major decisions and write two defensible architectures for each. Start with compute: a virtual machine provides familiar operating-system control but creates patching, image and scaling obligations. A managed application service can reduce routine infrastructure duties but may constrain runtime behavior or networking choices. Container orchestration can meet complex scheduling requirements while adding cluster operations, identity, upgrades and cost. The right choice depends on the workload’s actual constraints, not which product is fashionable.

Use Azure VMs and managed web applications to test the trade-off on a workload you know. Ask whether the application needs OS-level customization, predictable scale, low cold-start latency, specialized connectivity or features that a managed platform cannot supply. Include ownership of operating-system updates and runtime security in the comparison.

Storage is a second decision. Do not treat “choose geo-redundant storage” as a complete recovery design. Azure storage redundancy affects durability and geographic placement, but it does not substitute for application-consistent backups, authorization, data retention or a plan for accidental deletion. Specify recovery-point and recovery-time objectives, then test whether the chosen architecture can meet them. Also check that the correct storage type, account features and regional availability support the proposed redundancy option.

For networking, compare a straightforward application ingress design with one that needs centralized inspection, regional failover or private access. Document where TLS terminates, how name resolution works, who owns certificate rotation, what telemetry is available and which failure domain becomes shared. The cheapest topology on a diagram may be expensive to operate or troubleshoot. The most redundant design may introduce complexity that the organization is not staffed to maintain.

Deliver a short architecture decision record for each choice: context, alternatives considered, decision, rejected trade-offs, assumptions, approximate cost drivers, operational owner and one test that could prove the choice wrong. This is stronger AZ-305 preparation than listing Azure services with one-line descriptions.

Stage three: design a failure before a real incident designs it for you

Pick a user journey such as submitting a request and receiving confirmation. Simulate the loss of one dependency in a safe environment: identity token issuance, private DNS resolution, database connectivity, a compute instance or the notification service. Record the visible symptom, the detection signal, the containment action, and whether the system can continue with degraded functionality. Not every dependency needs multi-region active-active deployment; the design must justify the chosen failure response against the business requirement.

Use Azure backup and recovery as the implementation side of the exercise, but do not stop at “backup job succeeded.” Perform a test restore, confirm application data and permissions, and compare actual elapsed recovery time with the stated objective. If restoration relies on undocumented operator knowledge or unavailable credentials, the architecture is not yet resilient.

Observability is equally architectural. Azure Monitor alerting can notify staff that a metric or log condition crossed a threshold, but a successful alert rule does not tell the team whether customers completed their work. Add a user-relevant transaction and a named response owner to the monitoring design. Link the alert to a runbook that states the permitted next action and the evidence required before closing the incident.

Finally, decide what a design change would do during routine maintenance. A deployment, certificate renewal or security-policy change should not accidentally invalidate the recovery path. Trace the dependencies through the maintenance workflow and make rollback part of the design before the change reaches production.

Build an evidence portfolio, not a screenshot portfolio

After the three stages, present a small portfolio that a second engineer can inspect independently. Include a requirements document, one current-state diagram, two alternative designs, a decision record, an access-control matrix, a failure-test report and an operating-cost sensitivity check. Every artifact should answer a question. If the diagram uses a service that was not included in the cost estimate or recovery test, explain why it was excluded and who owns the resulting risk.

Ask a reviewer to challenge the proposal. What happens if the data cannot leave its region? What if the business doubles peak traffic? What if the team loses the ability to use a particular managed service? What if a security policy forbids public endpoints? A promising architect can adjust a design without losing track of its safety and operational assumptions. An administrator who has already managed incidents often brings valuable realism to those conversations; the transition is learning to make the trade-offs explicit before a production incident occurs.

Use the exam relationship to structure final preparation

AZ-104 experience is an advantage because you know how Azure behaves when things go wrong. AZ-305 asks you to turn that experience into decisions about identity, governance, storage, continuity and infrastructure. Review the current Microsoft AZ-305 skills guide, practice explaining alternatives under a stated constraint, and mark any topic where you can configure a service but cannot justify when not to use it.

Do not treat an exam pass, an architectural diagram or a running lab as sufficient evidence on its own. The credible progression is from known operational behavior, through explicit requirements, to a design that another engineer can evaluate, implement, observe and recover. The Azure Solutions Architect Expert designation recognizes the credential requirements; the professional shift is demonstrated in the reasoning behind the system.

img