A Hybrid Runbook is an Azure automation runbook that runs on a dedicated virtual machine. “Regular” automation runbooks cannot access resources in other clouds or on-premises. The Hybrid Runbook Worker feature of Azure Automation allows you to run runbooks directly on the computer hosting the role and against resources in the environment to manage those local resources.
In a client engagement, my automation runbook needed to reach out to a SQL Server datawarehouse to add Azure AD Groups as users in the database. For this, the ip address of the machine running the powershell had to be added to SQL Server firewall rule. That is where an Azure VM running as a Hybrid Worker became useful. Since the powershell script files ran on the Hybrid Worker machine, it was simple to add the Hybrid Worker machine’s ip to the SQL Server firewal rule using the powershell: New-AzureRmSqlServerFirewallRule.
Once you properly set up a Hybrid Worker machine, following the steps listed below, you get the option to run your runbooks on the Hybrid Worker machine. When you choose this option, your scripts will run on this designated machine.
A thing to watch out is when using custom modules. Normally, when using “regular” runbooks, you import your custom modules as zip files in the modules section of the automation account. When you use the Hybrid Worker option however, your custom modules do not get copied over to the Hybrid Worker machine. Instead you have to copy the modules file over to the machine and put it in the path that powershell can find it. The folder structure that encloses the module needs to be as prescribed in the docs. I have dealt with this in the section “Installing custom modules on the Hybrid Machine”
Setting up a Hybrid Runbook Worker
- In the Azure Portal, create an Azure Automation account, note its Resource Group Name & Automation Account Name. Currently the only Automation regions supported for integration with OMS are – Australia Southeast, East US 2, Southeast Asia, and West Europe, so location has to be one of these.Example:
- Automation Account Name: abcautomation
- Resource Group : rg-hb-util
- Location : East Us 2 *
- Create a OMS account there is a free trial available. You should create it in the same region as your automation account.
- Sign up url: OMS Trial Sign Up Link
- There will be a prompt to “Select Azure Subscription”, with prompts “Link”, “Create New”. Select Link
- Create a Windows 10 RS2 Pro (x64) vm from the marketplace
- Name : HW1
- Give it a public IP : HW1-IP
- Remote into the machine.
- If you try to launch browsers Microsoft Edge & you get “Windows 10 Edge can’t be opened using the built-in administrator account”, follow these steps to allow browser to open on Windows 10.Under Local Policies/Security Options navigate to “User Account Control Admin Approval Mode for the Built-in Administrator account And Enable it. Restart of VM is required. Refer to:https://www.virtualizationhowto.com/2015/07/windows-10-edge-opened-builtin-administrator-account/
- Download powershell script called New-OnPremiseHybridWorker.ps1 from the Powershell Gallery
- The following parameters should be provided to this script
$ResourceGroupName ="the rg of the automation account" $SubscriptionID = "your-sub-id" $WorkspaceName ="a new oms workspace will be created with the name you provide here. It should be unique to your account i.e. a workspace with this name should not already exist." $AutomationAccountName ="name of your automation account" $HybridGroupName ="A named group will be created with the name you provide i.g. Tenant-Provisioning"
- On the box, run the following powershell commands (to enable running scripts) : Set-ExecutionPolicy RemoteSigned
- Run the powershell called New-OnPremiseHybridWorker.ps1 (from the PowerShell Gallery on new vm, providing the parameters specified in 5. Important: run the powershell as Administrator or install of MS Monitoring Agent will fail. The script will download nuget packages, ask you to log into Azure with your credentials, then set up a OMS workspace and register the vm as a Hybrid Worker.
- If you go to the automation account in the Azure portal and look under the tab: “Hybrid worker groups”, you will see the group you specified in $HybridGroupName (Point #7) with Number of Workers = 1.
(Optional) Install Required software on the Hybrid Machine
- MSOnline (if you want to work with Azure Active Directory) Download Link
- Microsoft Active Directory Authentication Library for Microsoft SQL Server (If you want to work with SQL Server)Download link
If you get : Unable to load adalsql.dll then refer to : https://stackoverflow.com/questions/45578395/unable-to-load-adalsql-dll-error-when-calling-invoke-sqlcmd. You basically need to uninstall & reinstall Microsoft Active Directory Authentication Library for Microsoft SQL Server
Installing Custom Modules on the Hybrid Machine
- If you have a custom module called ” XYZ.Tenant.Management.psm1″ that you want to use in your Runbooks, then…
- This should be put into a folder called “XYZ.Tenant.Management” Refer to Rules For Installing Modules Docs: https://msdn.microsoft.com/en-us/library/dd878350
- This folder should be copied to the powershell path on the Hybrid worker vm
- This path is usually : C:\Program Files\WindowsPowerShell\Modules
- To find the path you can run this: