I spent three years in a monitoring role where I watched mainframe systems and reported incidents. I now have an opportunity to move into an L2 Azure position, and I'm trying to build the knowledge I missed while working in monitoring.
My current approach is to study every Azure service in detail, including how each one works and all of its key components. This is becoming overwhelming, and I often understand a service only well enough to describe it in a couple of sentences. I'm not yet able to explain concepts with the depth and confidence of someone experienced.
What would be a more effective learning method? Which Azure topics should I prioritize for an L2 support role, and how can I develop practical troubleshooting skills instead of trying to memorize the entire platform?
4 Answers
Since your background is in monitoring, build on that strength. Learn Application Insights, Azure Monitor, logging, and KQL queries. Your role may be less about designing or developing systems and more about identifying what is failing, understanding the evidence in the logs, and reporting the issue clearly. Use approved assistance tools only as a supplement after you understand the basics.
Study how a normal multi-tier application is put together—for example, a web application connected to a database and secure storage. Focus on why services are combined, what can fail, and how you would investigate the issue. Azure Monitor, Log Analytics, and diagnostic tools will probably be more valuable for your role than knowing every configuration option.
Use the AZ-900 fundamentals topics as a starting point and work through the beginner training on Microsoft Learn. Azure is enormous, but you’ll only use a fraction of it. Take one small area at a time and tailor your learning to the systems in your workplace. For example, initially it may be enough to understand the difference between running SQL on a virtual machine and using a managed database service; you don’t need to learn every advanced data feature immediately.
Don’t try to memorize every Azure service. Start with the fundamentals: networking, compute, storage, identity, and monitoring. Build small labs around those areas so you can see how the services behave instead of only reading feature lists. Learn the services that are actually used in your new environment first.
That makes sense. I’ll focus on understanding the architecture and troubleshooting process rather than trying to cover every service at once.