Start Azure V2 VMs Azure Automation Graphical PowerShell runbook - Best solution to replace
Hello! Hope you all are doing great. Currently, we are encountering a challenge in our Azure environment with a need to transition from deprecated RunAs Accounts to Managed Identity for our Automation Account runbooks. We have successfully deployed the "Start Azure V2 VMs Azure Automation Graphical PowerShell" runbook (refer: https://github.com/azureautomation/start-azure-v2-vms) in our environment. It is configured with numerous schedules for various VMs. Although we have adjusted the 'Connect to Azure' graphical interface section, it appears that the runbook continues to utilize the RunAs Account connection in other areas. I'm struggling to find an effective way to modify this. Moreover, the commands executed by the runbook are based on the AzureRM module, which is slated for deprecation soon. I am reaching out to solicit your guidance on the following queries: Is there an efficient and standard method to transition these runbooks from using RunAs Accounts? How can we effectively convert the AzureRM code in the graphical sections to the Az Module? Is there an alternate, perhaps newer, method to schedule VM start and stop in Azure that we should consider migrating to? Thank you in advance for your assistance and insight on this matter. Looking forward to your recommendations. Best regards,
Azure runbook is failing to execute due to Authentication issue with azure storage account
Iam facing one issue with authentication of storage account for automation runbook in azure. Scene:- Runbook will runasaccount and its based on service principle. This runbook will get the azurevm status and triggers to store that to storage account every two days. Issue: Runbook execution is successful if I put networking as publicly accessible Runbook is failing to store vm data in storage account if changed networking to selected network. In selected networking, I added resource instance of runbook and allowed trusted azure service, But still it is showing authentication issues. I provided contributor and storage blob data contributor role to the service principle also,still authentication issue. Any idea how to resolve this. Note:I don't want to make storage account publicly accessible.
