When you work with Azure Automation — and especially if you use Hybrid Worker machines — sometimes you need to use the certificates that are part of the connections created by the automation account on a local VM or server.
Runbooks that use these kinds of certificates work fine in the Azure environment, but if you need to run it in your local environment, using Hybrid Worker machines, this represents a challenge. Here's how to get those connection certificates on your Hybrid Worker.
Azure Automation is a cloud-based configuration service that automatically manages your Azure and non-Azure environments based on your runbooks, update management features, and shared capabilities like access controls, global storage of credentials/certificates/etc, tags, and more.
Included in Azure Automation is the option to extend your libraries. You can import a set of libraries called Modules to your automation account from a preexisting list that can be found in the Gallery or by uploading script files of your own.
Below you’ll see where to upload or choose these Modules.
When you work with Azure Automation, you might find yourself coding locally, putting all the initial logic into the script, copying and pasting the code to the web to run it, and then testing the code from the portal.
Usually this practice takes longer to execute and will require a printout of variables or comments to follow the code execution, as you are not debugging your script.
There is another, possibly better, way to get your PowerShell code into Azure.
As part of any monitoring strategy, we might need to automate some tasks to provide key information to evaluate the state of our infrastructure or apply a repetitive action to resolve specific issues.
We have several ways to implement this. One option is to use Microsoft’s Azure Automation toolset. Let’s explore what you can control with Azure Automation and how to get started using it for cloud server update management, configuration, and more.