This is where my last two articles, Git for System Admin Scripting and Get Started with Git Remote, come together. Microsoft’s Visual Studio Code (VS Code) is a powerful and extendable IDE. VS Code supports Git out of the box. It also supports many programming and scripting languages with Microsoft and 3rd party extensions. In this article, I walk through common tasks that we have already covered, only this time with the native Git integration within VS Code. I also review new functionality with a free 3rd party extension.
Continue reading “Git and VS Code for the Lone Scripter”
ARM Templates are written with JSON and are at the core of Azure Resource Manager deployments. I have used and developed templates for months. Although successful, I ran into issues with formatting and syntax this week and decided to take a step back and get a better understanding of the underlying JSON used in these templates. In this post, I start from the beginning, exploring JSON as it relates to ARM templates. 
Recently I ran into an issue with Authentication and Azure Automation child runbooks. The goal was to call a PowerShell child runbook following the documentation 
I see a lot of potential in Azure Log Analytics. That should go without saying considering the amount of time I have spent learning and documenting it over the past few weeks. One of the most exciting features that adds tremendous flexibility is the ability to log directly to Log Analytics with the Web API. Logging to the Web API enables anything to be written to Log Analytics without the use of the Microsoft Monitoring agent. 
Odds are, you were Googling something like ‘write event log PowerShell’ and you stumbled on this page. If that’s the case and you just want to write an event to the Event Log to test something like a monitoring or alerting app, I won’t disappoint, below is what you need to know. If you want a little more information on writing to the Event Log as part of a script, keep going.