Azure runbooks stuck in suspended status after "connectedmachineagent" updates

Brass Contributor

Buckle up.
We are running Azure runbooks on a local server using a hybrid worker.

Occasionally (monthly?) the server will get routine updates and usually, after the updates, all runbooks on the machine will be stuck in "suspended" status.
Every time this happens, the permissions on the "C:/ProgramData/AzureConnectedMachineAgent/Tokens" folder have been reset, and this is the reason the runbooks get stuck- we fix this by giving the runas account Read access on this folder again.

after monitoring the situation for several months, i have found a pattern.

windows updates for "azureconnectedmachineagent" reset these folder permissions. so whenever such an update runs, our runbooks get stuck and i need to fix the folder permissions.

Sadly, i raised this with Azure support and they claim it's not an Azure issue. So i opened a ticket with Microsoft365 support who claim the same thing...... unsurprisingly, and sadly, Microsoft can't even manage to find the right team to handle this question- so here we are :)

Anyone else?

1 Reply
this happened most recently last night, with the "azureconnectedmachineagent version 1.27 - February 2023 update" update.