Hey everyone! I recently jumped into a role as a cloud architect at a company with a massive Azure setup—about 50 subscriptions across various departments. I'm coming from a smaller environment where I had more defined processes and a team to work with, so this feels a bit overwhelming. If you were in my shoes, how would you go about getting a solid grasp on this kind of sprawling Azure landscape? I'm eager to take charge of our cloud setup, but my past experience with small to medium-sized companies hasn't quite prepped me for this chaotic mix of cloud-native applications.
2 Answers
Honestly, the number of subscriptions alone doesn't tell the full story. You need to dive into how many resource groups and specific resources are out there. Look at policies, RBAC settings, networking, and logging. All these pieces matter for a clearer picture of what you're managing.
As a Microsoft partner, I've seen many inherited environments. First, check out the Cloud Adoption Framework—it’s a solid starting point. Analyze your cloud costs and security using Azure Advisor; it’ll give you valuable recommendations. Focus on cleaning up underutilized resources and unattached disks first. When it comes to security, be wary of public IPs that aren't tied to any Network Virtual Appliances (NVAs). They're major vulnerabilities. While you're tidying up, it’s smart to check out Cloud Defender for deeper security insights. Don't forget to peek at governance policies and RBAC settings as you go—keep a backlog of what needs attention and prioritize based on company goals.
Great advice! Also, consider implementing Azure policies for basic security guardrails and make sure to tidy up your identity and permissions. You don’t want any unsecured connections lingering. Setting up logging is key too—stream it to an event hub or SIEM for better management. It’s all about creating a strong governance strategy too—tagging is a must!

Definitely agree! Setting up infrastructure as code templates early will save you a lot of headaches later on. You can try importing what's already there, but brace yourself—it might get messy!