CLOUDY MUSINGS

Let me tell you about a moment that happens to almost everyone working with Azure networking. You're designing a network, you discover service endpoints, and you think "Great! This keeps my traffic on Microsoft's backbone instead of the public internet." You enable them for Storage, SQL, maybe Key Vault. Everything makes sense. Then you stumble across service endpoint policies and think "Oh cool, I can add more control to all these services!" You start setting them up for SQ

Cloud engineering looks complicated from the outside. But when you peel back some layers, it doesn't seem so daunting. I believe in breaking down tricky concepts so that even a six-year-old could understand. We don’t need to make everything so complicated that no one gets it. To me, that's the quickest way to lose the hearts and minds of your esteemed colleagues, customers, and peers. The Complexity of Cloud Engineering What I've found is that folks often imagine giant Terraf

All code for this blog post can be found here . By now you’ve probably figured out I like to make things harder on myself before I make...

Shannon's Disclaimer: All code for this blog can be found here . I'm going to start putting together code based blogs with their own repo and will clean up older blog posts as time allows. If you spend enough time working in the cloud, you get used to things breaking in ways that make no sense. Case in point: the other day my Azure CLI on Windows decided it was going to stop working. I started in WSL because that is usually where things behave the best. I ran az login and ins

Over the course of my career, I've picked up various Visual Studio Subscriptions that enable me to build and maintain a small Azure...