AzureTracks is a practical technical blog for people building, securing, and operating Microsoft cloud environments. I focus on real-world Azure and Microsoft 365 security work: the decisions that need to be made, the controls that need to be tested, and the evidence that shows a deployment is working as intended.
About me
I’m Andrew. I’ve worked in information technology since 2001 and have focused on Azure, cloud migrations, and Microsoft infrastructure since 2015. My background spans software development, network and ATM systems, public-safety technology, infrastructure administration, troubleshooting, and automation for organizations across government, finance, retail, construction, energy, and other industries.
Today, I enjoy helping teams make Azure and Microsoft 365 environments more secure, manageable, and repeatable. PowerShell and automation are a major part of that work, especially when a process needs to be documented, validated, and performed consistently across environments.
What you’ll find on AzureTracks
- Step-by-step Azure and Microsoft 365 security walkthroughs
- Microsoft Sentinel, Defender, Entra ID, governance, and monitoring guidance
- PowerShell, Azure CLI, KQL, and infrastructure automation examples
- Production-minded deployment, validation, troubleshooting, and rollback notes
- Summaries of important Azure and Microsoft security updates
The goal is not simply to show where to click in a portal. I want each walkthrough to explain why a control matters, what should be captured before making a change, how to test the finished state, and what operational teams need after deployment.
How I approach technical guidance
Cloud services change quickly, and every organization has different requirements. I build articles around a lab-first, verify-before-expanding approach. Where it matters, I include prerequisites, permissions, cost or licensing considerations, known limitations, production hardening, and rollback guidance.
Examples on this site are starting points, not substitutes for your organization’s architecture review, security policies, change-management process, or testing. Always validate commands and configuration changes in a non-production environment and confirm the current Microsoft documentation before deploying them broadly.
Why I share
I enjoy sharing knowledge with the technical community and turning complex cloud-security work into something another engineer can understand, test, and improve. If an article helps someone avoid an architectural shortcut, solve a difficult problem, or give their security operations team a better day, AzureTracks is doing its job.
Outside of technology, I enjoy hiking, mountain biking, camping, and spending time with my wife and family near the Rockies. Work keeps us connected, but getting outdoors keeps everything in perspective.
AzureTracks is an independent site. The views and examples published here are my own and are not official guidance from Microsoft or any current or former employer.