This is an automated archive made by the Lemmit Bot.
The original was posted on /r/azure by /u/TiredDadEnergy on 2023-09-20 22:20:42.
I enjoy cloud infrastructure stuff, truly. Azure Infra has always been an enjoyable thing to learn about and has come in handy during my day job when we occasionally have to do some custom work for a customer that's outside our normal service offerings. It's never anything overly complex but it's been a good time.
Right now, my business has re-organized a bit and is working to have a dedicated team of consultants to handle some of our long-term consulting work, but until that staffing is complete, I've been asked to fill it. The commitment is manageable with my normal responsibilities (I also have a good team who can cover me one day a week while I consult) so I don't mind that. What I'm finding to be a real migraine-inducing time is consulting on more complex azure infrastructure. I can't give details for NDA reasons, but holy hell is it mind-numbing to try and figure out what's going on. This isn't a greenfield project, so I've got limited time to try and figure out what's doing what, and connected to what, and providing what service, and what NSG goes to what Subnet, and what Resource Groups have what, and I just want to slam my head on my desk.
Has anyone else ever ended up here? I'm at a point where if I never have to look at another Azure Infrastructure gig again it would be too soon. I want to crawl back into my SOC hole and hunt security threats in peace....