More robust viewing and management of Hybrid Runbook Workers
Hybrid runbook workers should have management offered through the Azure Portal and via PowerShell cmdlets.
User story 1: As a user I should be able to see which hybrid runbook worker a particular job ran on, not just the hybrid worker group (which I should see as well). The Azure Portal UI should show me the specific hybrid worker and I should also see the specific hybrid worker as output when executing Get-AzureRmAutomationJob (again, in addition to the Hybrid Worker Group).
User story 2: As a user I should be able to configure individual hybrid workers to be available/unavailable to accept new jobs. This is necessary so that a hybrid worker can be configured not to accept new jobs without impacting the jobs that it is currently working on. This would facilitate processes such as patching hybrid worker computers without impacting jobs they are working on. The hybrid worker can be configured not to accept any new jobs and then jobs can be queried (see user story 1) to confirm that no jobs are running on that hybrid worker and patching could then proceed. The ability to mark a hybrid worker as available/unavailable (or in and out of maintenance mode perhaps?) should be offered via the Azure Portal UI as well as via PowerShell. PowerShell cmdlets should be created for managing a specific hybrid worker such as Get-AzureRmAutomationHybridWorker and Update-AzureRmAutomationHybridWorker or perhaps Set-AzureRmAutomationHybridWorker.
Thank you for the feedback. We have plans around improving hybrid worker management & we will prioritize it as resourcing allows.
Pieter van Wijngaarden commented
I have an additional user story: As a user I should be able to remove hybrid runbook workers from the portal (i.e. not on the hybrid worker itself). Sometimes, the (virtual) machine that the hybrid runbook worker was running on was terminated or deleted entirely before removing the Hybrid Runbook Worker. I have quite a few stale entries in my Automation Account(s) now pointing to systems that do not exist anymore, and I can't remove the Hybrid Runbook Worker, nor the group they belong to.