Deploy a Windows Hybrid Runbook Worker
You can use the Hybrid Runbook Worker feature of Azure Automation to run runbooks directly on the computer that's hosting the role and against resources in the environment to manage those local resources. Runbooks are stored and managed in Azure Automation and then delivered to one or more designated computers. This article describes how to install the Hybrid Runbook Worker on a Windows machine.
Installing the Windows Hybrid Runbook Worker
To install and configure a Windows Hybrid Runbook Worker, you can use two methods. The recommended method is using an Automation runbook to completely automate the process of configuring a Windows computer. The second method is following a step-by-step procedure to manually install and configure the role.
To manage the configuration of your servers that support the Hybrid Runbook Worker role with Desired State Configuration (DSC), you need to add them as DSC nodes.
The minimum requirements for a Windows Hybrid Runbook Worker are:
- Windows Server 2012 or later.
- Windows PowerShell 5.1 or later (download WMF 5.1).
- .NET Framework 4.6.2 or later.
- Two cores.
- 4 GB of RAM.
- Port 443 (outbound).
To get more networking requirements for the Hybrid Runbook Worker, see Configuring your network.
For more information about onboarding servers for management with DSC, see Onboarding machines for management by Azure Automation DSC. If you enable the Update Management solution, any Windows computer that's connected to your Azure Log Analytics workspace is automatically configured as a Hybrid Runbook Worker to support runbooks included in this solution. However, it isn't registered with any Hybrid Worker groups already defined in your Automation account.
The computer can be added to a Hybrid Runbook Worker group in your Automation account to support Automation runbooks as long as you're using the same account for both the solution and the Hybrid Runbook Worker group membership. This functionality has been added to version 7.2.12024.0 of the Hybrid Runbook Worker.
After you successfully deploy a runbook worker, review Run runbooks on a Hybrid Runbook Worker to learn how to configure your runbooks to automate processes in your on-premises datacenter or other cloud environment.
Perform the following steps to automate the installation and configuration of the Windows Hybrid Worker role:
Download the New-OnPremiseHybridWorker.ps1 script from the PowerShell Gallery directly from the computer running the Hybrid Runbook Worker role or from another computer in your environment. Copy the script to the worker.
The New-OnPremiseHybridWorker.ps1 script requires the following parameters during execution:
AutomationAccountName (mandatory): The name of your Automation account.
AAResourceGroupName (mandatory): The name of the resource group that's associated with your Automation account.
OMSResourceGroupName (optional): The name of the resource group for the Log Analytics workspace. If this resource group is not specified, AAResourceGroupName is used.
HybridGroupName (mandatory): The name of a Hybrid Runbook Worker group that you specify as a target for the runbooks that support this scenario.
SubscriptionID (mandatory): The Azure subscription ID that your Automation account is in.
WorkspaceName (optional): The Log Analytics workspace name. If you don't have a Log Analytics workspace, the script creates and configures one.
Currently, the only Automation regions supported for integration with Azure Monitor logs are Australia Southeast, East US 2, Southeast Asia, and West Europe. If your Automation account is not in one of those regions, the script creates a Log Analytics workspace but warns you that it can't link them together.
On your computer, open Windows PowerShell from the Start screen in Administrator mode.
From the PowerShell command-line shell, browse to the folder that contains the script that you downloaded. Change the values for the parameters -AutomationAccountName, -AAResourceGroupName, -OMSResourceGroupName, -HybridGroupName, -SubscriptionId, and -WorkspaceName. Then run the script.
You're prompted to authenticate with Azure after you run the script. You must sign in with an account that's a member of the Subscription Admins role and co-administrator of the subscription.
.\New-OnPremiseHybridWorker.ps1 -AutomationAccountName <NameofAutomationAccount> -AAResourceGroupName <NameofResourceGroup>` -OMSResourceGroupName <NameofOResourceGroup> -HybridGroupName <NameofHRWGroup> ` -SubscriptionId <AzureSubscriptionId> -WorkspaceName <NameOfLogAnalyticsWorkspace>
You're prompted to agree to install NuGet, and you're prompted to authenticate with your Azure credentials.
After the script is finished, the Hybrid Worker Groups page shows the new group and the number of members. If it's an existing group, the number of members is incremented. You can select the group from the list on the Hybrid Worker Groups page and select the Hybrid Workers tile. On the Hybrid Workers page, you see each member of the group listed.
Perform the first two steps once for your Automation environment, and then repeat the remaining steps for each worker computer.
This article was recently updated to use the term Azure Monitor logs instead of Log Analytics. Log data is still stored in a Log Analytics workspace and is still collected and analyzed by the same Log Analytics service. We are updating the terminology to better reflect the role of logs in Azure Monitor. See Azure Monitor terminology changes for details.
1. Create a Log Analytics workspace
If you don't already have a Log Analytics workspace, create one by using the instructions at Manage your workspace. You can use an existing workspace if you already have one.
2. Add the Automation solution to the Log Analytics workspace
Solutions add functionality to Azure Monitor logs. The Automation solution adds functionality for Azure Automation, including support for Hybrid Runbook Worker. When you add the solution to your workspace, it automatically pushes worker components to the agent computer that you will install in the next step.
To add the Automation solution to your Log Analytics workspace, follow the instructions at To add a solution using the Solutions Gallery.
3. Install the Microsoft Monitoring Agent
The Microsoft Monitoring Agent connects computers to Azure Monitor logs. When you install the agent on your on-premises computer and connect it to your workspace, it automatically downloads the components that are required for Hybrid Runbook Worker.
To install the agent on the on-premises computer, follow the instructions at Connect Windows computers to Azure Monitor logs. You can repeat this process for multiple computers to add multiple workers to your environment.
When the agent has successfully connected to Azure Monitor logs, it's listed on the Connected Sources tab of the log analytics Settings page. You can verify that the agent has correctly downloaded the Automation solution when it has a folder called AzureAutomationFiles in C:\Program Files\Microsoft Monitoring Agent\Agent. To confirm the version of the Hybrid Runbook Worker, you can browse to C:\Program Files\Microsoft Monitoring Agent\Agent\AzureAutomation\ and note the \version subfolder.
4. Install the runbook environment and connect to Azure Automation
When you add an agent to Azure Monitor logs, the Automation solution pushes down the HybridRegistration PowerShell module, which contains the Add-HybridRunbookWorker cmdlet. You use this cmdlet to install the runbook environment on the computer and register it with Azure Automation.
Open a PowerShell session in Administrator mode and run the following commands to import the module:
cd "C:\Program Files\Microsoft Monitoring Agent\Agent\AzureAutomation\<version>\HybridRegistration" Import-Module .\HybridRegistration.psd1
Then run the Add-HybridRunbookWorker cmdlet by using the following syntax:
Add-HybridRunbookWorker –GroupName <String> -EndPoint <Url> -Token <String>
You can get the information required for this cmdlet from the Manage Keys page in the Azure portal. Open this page by selecting the Keys option from the Settings page in your Automation account.
- GroupName is the name of the Hybrid Runbook Worker group. If this group already exists in the Automation account, the current computer is added to it. If this group doesn't exist, it's added.
- EndPoint is the URL entry on the Manage Keys page.
- Token is the PRIMARY ACCESS KEY entry on the Manage Keys page.
To receive detailed information about the installation, use the -Verbose switch with Add-HybridRunbookWorker.
5. Install PowerShell modules
Runbooks can use any of the activities and cmdlets defined in the modules that are installed in your Azure Automation environment. These modules are not automatically deployed to on-premises computers, so you must install them manually. The exception is the Azure module, which is installed by default and provides access to cmdlets for all Azure services and activities for Azure Automation.
Because the primary purpose of the Hybrid Runbook Worker feature is to manage local resources, you most likely need to install the modules that support these resources. For information on installing Windows PowerShell modules, see Installing Modules.
Modules that are installed must be in a location referenced by the PSModulePath environment variable so that the hybrid worker can automatically import them. For more information, see Modifying the PSModulePath Installation Path.
- To learn how to configure your runbooks to automate processes in your on-premises datacenter or other cloud environment, see Run runbooks on a Hybrid Runbook Worker.
- For instructions on how to remove Hybrid Runbook Workers, see Remove Azure Automation Hybrid Runbook Workers.
- To learn how to troubleshoot your Hybrid Runbook Workers, see Troubleshooting Windows Hybrid Runbook Workers
- For additional steps on how to troubleshoot issues with Update Management, see Update Management: troubleshooting.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.