I have more than 15 years of experience across AWS and Azure, primarily as a DevOps engineer. I'm Azure-certified and have around eight years of Azure experience, but I haven't personally designed and built many production environments from the ground up. I've also been on a career break for about a year and a half, so I need to refresh my knowledge.
I'm preparing for a consulting role where the client expects me to have designed one or two infrastructure architectures. I'd like a practical roadmap for moving toward Azure architecture, including which services and architecture concepts to prioritize. I also need to automate a client use case with Bicep, so hands-on labs, reference architectures, and a high-level overview of Azure architecture would be especially helpful. I understand that becoming a strong architect takes much longer than a weekend, but I have limited time and want to focus on the most valuable areas first.
5 Answers
For a structured study path, begin with AZ-104-level administration topics and then work through AZ-305 design objectives. If networking is a weak area, add AZ-700 material. The exam objectives can help organize your review, but they won’t replace hands-on experience.
Set up a small tenant or lab environment, deploy a landing-zone-style foundation, and automate it with Bicep modules. Keep the code in a repository with a README and architecture diagram so you can demonstrate both the implementation and the reasoning behind it.
Start with Microsoft’s Cloud Adoption Framework and Well-Architected Framework. They provide useful structure around landing zones, governance, security, reliability, performance, operations, and cost. The official architecture center and reference architectures are also good places to study complete designs.
Keep in mind that an architect needs more than cloud-service knowledge. You should be able to discuss business requirements, data, applications, security, compliance, regulatory concerns, and operating models. Familiarity with security guidance such as CIS and NIST is useful, and broader enterprise architecture concepts can help as well.
Be careful about presenting yourself as having years of architecture experience if your background has mostly been implementation or DevOps. That said, architecture experience can come from several paths. A developer or operations engineer who has designed, integrated, secured, and supported real systems may have stronger practical judgment than someone who only knows frameworks and terminology.
Use your existing experience honestly, identify the gaps, and prepare a few well-documented designs that show how you think. That will be more convincing than trying to memorize Azure services over a weekend.
A more realistic short-term goal is to become comfortable designing and explaining Azure solutions rather than claiming complete architect-level experience immediately. A good exercise is to take a business scenario and produce a short design covering requirements, assumptions, diagrams, identity, networking, data, availability, disaster recovery, monitoring, security, cost, and deployment through Bicep.
Your existing DevOps background is valuable, especially if you have operated systems in production. Strong architects understand how their designs behave during deployments, incidents, scaling, and maintenance. Don’t focus only on certifications; be prepared to explain why you selected each component and what alternatives you rejected.
A complete transition to Azure architect in one weekend isn’t realistic, but you can make a focused start. Review AZ-900 and AZ-104 material, then move toward AZ-305 or AZ-700 depending on whether you need broader design knowledge or deeper networking skills.
The fastest way to build confidence is to create a lab and design it yourself. Start with a landing zone, identity, governance, subscriptions, and networking. Pay particular attention to hub-and-spoke networking, Virtual WAN, firewalls, NSGs, route tables, private endpoints, and connectivity. Then build a few common workloads, such as a web application with SQL or PostgreSQL, comparing Application Gateway with WAF against Front Door.
Use Bicep to deploy each component repeatedly and document the decisions, trade-offs, security controls, resilience, cost, and operational model. Architecture is a continuous learning process, even for people who have been doing it for years.
That makes sense. I’m mainly trying to prepare quickly for a consulting engagement, so I’ll focus on reviewing one or two complete reference architectures and rebuilding simplified versions in a lab.
Is there a resource that gives a high-level view of Azure architecture before I go deep into individual services?