Utilize the same Automation hybrid runbook workers across multiple Automation accounts under the same subscription.
Utilize the same Automation hybrid runbook workers across multiple Automation accounts under the same subscription. Currently its a 1to1 link between an automation account and a runbook worker. This means I have to create a new runbook worker for each automation account.
Cole Gonzales commented
When there are separate automation accounts for several different use cases it is not reasonable to install as many local servers to do the job. It's a big waste of resources and creates unnecessary maintenance needs.
Because of the varying complexity and connections to Logic App, Event Grid etc. and also different permissions per account, all the runbooks cannot be located in one Automation Account. Microsoft also recommends using separate Resource Groups for different applications.
In my case Automation is used in many (sensitive) data transfers and other integrations between on-prem and/or cloud applications. Often the flow is made with Logic App and the on-prem actions are done with Runbooks.
JB Lewis commented
What if the HRW could be run in a container? Then you could service multiple automation accounts with a modicum of separation between the instances.
YES! Trying to be more "Serverless" by moving on-prem scripts to Runbooks but when one server is required per automation account it starts to seem pointless
Ola Hagbohm commented
Yes but please don't limit it to a subscription or tenant.
Yes but not limited to a subscription or tenant
John S commented
Yes, but please don't limit this to a subscription.