Azure Automation: Setting “Run As” Account on Hybrid Worker Groups!

I just want to post a little new feature I found a couple of days ago as a small NYE treat!

It is now possible to set a “global” Run As account on a hybrid worker group!

This feature removes any difference between SMA and AA Hybrid Workers, meaning that you can transfer any runbooks directly! (Contact me if you need help)

By Default the Hybrid Workers run as “LocalSystem”, while SMA runbook workers run as a specified service account.

It is possible to change the service account for the Microsoft Monitoring Agent, but that is not best practice and could impact other services than the Hybrid Worker.

Now with the new setting we can define a service account, selected from the asset, for each of the Hybrid Worker groups! Great Stuff!

To Setup a run as account for a Hybrid worker group:


  • Select a Hybrid Worker groups
  • Click “All Settings”


  • Select “Hybrid Worker Group Settings”


  • Change the Default to Custom
  • then select a credential from the assets


Now your runbooks will execute as this account.

Make sure it has the necessary permission to execute in your environment!


Happy New year!

And lets make 2016 even better than the amazing 2015!

By |2015-12-31T13:46:30+00:00December 31st, 2015|Azure|2 Comments

About the Author:

Jakob Gottlieb Svendsen

Twitter: @JakobGSvendsen

Jakob Gottlieb Svendsen is a Microsoft Cloud and Data Center Management MVP (, Working as Global Lead Developer, Senior Consultant and Trainer at CTGlobal, where he is one of the driving forces in keeping CTGlobal a System Center Gold Partner and member of the System Center Alliance.

Since he started at Coretech in 2007, he has focused on Scripting and Development, primarily developing tools, extensions and scripts for the System Center Suite. His main area is Automation (including OMS/Azure Automation, Service Management Automation, PowerShell and Orchestrator). Another area is Windows Azure Pack / Azure Stack, where he does implementation, development, workshops and presentations. He is a world-wide renowned voice in the Automation field.

He is passionately devoted to the community, to which he contributes by being a moderator at TechNet and sharing his knowledge at

  • Co-founder: PowerShell User Group Denmark
  • Speaker at MMS 2016, Minneapolis (
  • SCU Europe 2014, 2015, 2016 (
  • Microsoft TechEd North America 2014, Houston
  • NIC 2012,2013,2014,2015, Oslo (
  • Microsoft CampusDays 2011, 2013, Copenhagen
  • Microsoft TechDays 2015, Sweden (
  • Microsoft Partner Event: New in SC2012 SP1
  • User group meetings (PSUG.DK , SCUG.DK/BE/NO, AZMUG + more)
  • Microsoft Certified Trainer.
  • Microsoft Scripting Guys Forum Moderator

Main working areas:

  • Automation (Azure Automation, SMA, SCO)
  • Windows Azure Pack / Azure Stack
  • System CenterVisual Studio Team Services / Team Foundation Server
  • Development:C#.Net, VB.NET, VBScript, PowerShell, Service Manager, OpsMgr, ConfigMgr
  • Orchestrator
  • Windows Azure Pack / Azure Stack


  • Azure Automation
  • Service Management Automation
  • System Center Orchestrator
  • PowerShell, VBScript, C#.Net, VB.Net
  • Windows Azure Pack / Azure Stack Development Workshops


  1. […] Hybrid Worker registered. Note that you since a couple of weeks can run your Hybrid worker with a other credentials then local system, which is really nice in our particular case. Since I will use Tao […]

  2. Neil April 11, 2016 at 15:25 - Reply


    Did you ever look into how to set this programatically? Via REST/PowerShell etc?

Leave A Comment