Automation Account can't identify when using Start / Stop VMs during off-hours

Shunrui Cao 46 Reputation points
2022-08-03T02:33:04.77+00:00

Hi experts,

Does any one meet the same problem?
When I set Start / Stop VMs during off-hours, the system can't recognize the automation ID defaultly, enen though there was one and I created a new one follow the help. I also checked the permissions, but there seems to be no problem

As this problem's solution, I made a runbook code to start and stop the VMs in a job schedule. But I still wonder to konow how to deal with this case.

Best regards!
Shunrui Cao

Azure Automation
Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
1,255 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. tbgangav-MSFT 10,416 Reputation points
    2022-08-10T07:13:16.907+00:00

    Hi @Shunrui Cao ,

    Check if this issue is related to supported mappings i.e., only certain regions are supported to link Automation account and Log Analytics workspace together. In general, the mapping is not applicable if you plan to link an Automation account to a Log Analytics workspace that won't have these features enabled. For more information, refer this Azure document.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.