Installation/Validation of extension-based hybrid worker

As you know, Azure Automation agent-based user Hybrid Runbook Worker (Windows and Linux) is deprecated and support has ended on August 31, 2024.

For previous instructions, please see the following article: Migrate existing agent-based hybrid workers to extension-based workers in Azure Automation | Micr…

However, users may want to ensure that their runbooks and jobs are leveraging the scale-out or agent-based system when transitioning. It is worth noting that versions V1 and V2 of the same hybrid worker machine can be registered to Azure Automation at the same time, but with different names.

If you do not uninstall the V1 agent before installing the V2 extension, Azure will detect both versions on the same computer.

“Last seen time” indicates that both V1 and V2 are communicating with Azure Automation.

It is also worth noting that some automation tasks are still being performed by the V1 worker. This explains the ongoing activity. The Runbook task can be executed on any machine within the Hybrid Worker Group. Currently, this group contains both V1 and V2 versions, so the tasks are distributed between the two versions.

Installing V2 does not mean that the Hybrid Worker Group will ignore V1 and use V2 exclusively.

Have fun learning!