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

The companion code for this blog can be found here . One thing you may have noticed is that I have been in PowerShell a bit more frequently as of late. The back story is I had a machine that all of a sudden didn't respond well with PowerShell and I spent quite a bit of time cleaning everything up. Whenever plagued with PowerShell issues, I run through an extensive list of troubleshooting every time a machine doesn't play nice and figured it might be a good time to share some

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

I know a lot of us are using more command line based tools these days. Azure PowerShell is one of the tools I tend to use often if I need...