To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
4 thoughts on “Azure Automation Hybrid Worker with Azure Arc Enabled Servers”
Hi Travis,
thanks for the content. One question: how many workers can exist in a single workers group? I mean, we can run one script to multiple servers at a time?
The doc is not that clear about that:
“Each user Hybrid Runbook Worker is a member of a Hybrid Runbook Worker group that you specify when you install the worker. A group can include a single worker, but you can include multiple workers in a group for high availability.”
Multiple works provide high availability. The script will only run on one of the workers and it’s not possible to select the one it runs on.
Hi Travis!,
Thanks for the reply! So basically, if I need to run the script on every single machine, I should create a separate workgroup for each one, right?
You could, but that won’t scale well. This question has come up a coupled of times since I posted the video. I’m working on a follow up that goes over PowerShell remoting with Hybrid Workers that may address this scenario. It will be available in a week. The short version is use invoke-command with credential resources to run the commands remotely.