Hi @Goel, Akanksha ,
Thank you for your post! I can see that you are currently running the runbook from an Azure Sandbox which is the default cloud worker rather than a Hybrid Runbook worker.
Azure sandboxes are like random internet systems because they are used by all Azure customers by default. We do not create individual sandboxes on your local network so it will never be able to connect directly to your VM on a private network. You can however run your Automation runbooks on a Hybrid runbook worker directly on an Azure or non-Azure machine per the following document here.
As an alternative, you could also issue a command from an Azure Cloud Runbook that runs a script on your Azure VM using Invoke-AzVMRunCommand since the runbook at that point would not be connecting directly to the Azure VM. I have a attached a couple of sample scripts you can use for testing this method as well.
Please let me know if you have any further questions or concerns.
Thanks!
Carlos V.
Hi @Carlos Villagomez , How to run the parent and child script together in single runbook? Can we have call to discuss on this?
Hello @Goel, Akanksha ,
Thank you for your response. I just wanted to clarify from my previous response that the parent and child script approach requires running both scripts on your Azure VM using the Invoke-AzVMRunCommand cmdlet in order to get the Windows or Linux VM's PS information from the runbook and then run the OS related remotely. For further instructions on how to connect your VM to Azure Runbook, please reference the following thread here on how to run both runbook scripts on the VM and to help guide you through the process.
Please let me know if you have any further questions or concerns
Thanks,
Carlos V.
@Goel, Akanksha ,
If you have a support plan then to request assistance with a troubleshooting call here, I recommend you reach out to the Azure technical support team by raising a support ticket as mentioned here.
Sign in to comment