Fixed IP for Automation PowerShell sandbox in order to fit ACL requirements for public endpoints
If VM has external endpoints (WinRM, SSH) protected by ACL, the Azure Automation doesn't able to connect for such VMs.
Thanks for this suggestion!
I need this so that I can setup named locations for conditional access. My tenant is blocking legacy authentication. So I cannot connect to azure or O365 with PowerShell. I need to be able to create an exclusion policy.
Lee Hardy (Strategic Cloud Solutions) commented
It would be useful to have a published list of public IP's we can whitelist for Azure Automation, as the hybrid worker solution is over-complicating a simple solution we're trying to provide - some basic automation against a firewall enabled storage account.
Ramon Ayala commented
Just wanted to add my voice to the mix.
Is this this something that is being seriously considered? I'm guessing not since it's been under review since 2014.
This would make scripts a lot simpler and secure if we don't have to run hybrid workers, we can move to a more serverless environment and keep everything in azure.
Hi Tae Shin commented