Introduction
I’ve always believed that to truly master the cloud, one must understand the "why" behind the services, not just the "how" of a single provider.
Currently, I am privileged to be interning with an AWS Partner company, where I’m diving deep into AWS projects and solving real-world challenges weekly. It’s been an incredible journey earning my AWS CCP and SAA, but I’ve decided that 2026 is the year I become a multi-cloud professional.
I’ve officially begun my journey toward the Microsoft AZ-104 (Azure Administrator) certification! 🎓
Why add Azure to my AWS background?
Cloud Agnostic Mindset: Understanding how different providers handle Identity (Entra ID vs. IAM) or Networking (VNets vs. VPCs) sharpens my architectural decision-making.
Best-of-Breed Solutions: Every cloud has its "superpower". By learning Azure, I can better advise on hybrid environments and Microsoft ecosystem integrations.
Continuous Growth: The cloud doesn't stand still, and neither should we.
I’m currently following a modular path through Udemy and Microsoft Learn, mapping my AWS knowledge to Azure services as I go.
To my fellow cloud engineers: What was the biggest "lightbulb moment" you had when learning your second cloud provider? 💡
Follow me on my socials:
LinkedIn:
YouTube:
Top comments (0)