Hey everyone! I'm currently working as an Azure DevOps engineer and have also had experience with various Azure services. I'm eager to move beyond my current role and step into the position of Azure Solution Architect. However, I'm feeling a little lost when it comes to gaining real hands-on experience in this new direction. I've taken several courses that cover the basics of Azure services and deployment, but I want to understand how an Azure Solution Architect approaches project requests in a practical sense. Specifically, I'm looking for guidance on how to:
1. Break down project requests into functional and non-functional requirements.
2. Navigate the Cloud Adoption Framework (CAF).
3. Create Azure landing zones using verified modules.
4. Develop application landing zones or platform landing zones.
5. Design a migration strategy.
If anyone can share tutorials or case studies that cover these areas in detail, I would greatly appreciate it!
2 Answers
I’m also curious about this! If anyone has references to GitHub repos showcasing various Azure projects, that would be super helpful for us trying to map our paths forward!
To tackle project requests, start by identifying the core functionalities your application needs—that usually falls into Must, Should, and Could categories. For non-functional requirements, think along the lines of what security measures need to be in place, network setup, and other business constraints. If you're looking for practical steps to work on the CAF, keep in mind that the focus will differ based on whether it's a migration or a new project. For Azure landing zones, consider using the Enterprise Landing Zone accelerator as a base, and make adjustments as necessary for your organization. Also, don't forget to examine Azure Architect Expert exam material if you want deeper insights into these processes!
Absolutely, that's where the complexity really starts! Once you dive into integrating third-party tools for networking, security, and logging solutions, the real challenge and fun begins!