Azure Automation updated DNS records
Published date: June 22, 2020
To support new features in Azure Automation, like Azure Private Links, the automation URLs have been updated. Instead of region-specific URLs, there are now account-specific URLs. If you have an Automation account that's defined for a specific region, use the following DNS records in your firewall security rules or to restrict hybrid runbook worker communication to that regional datacenter.
Old automation URLs:
ac-jobruntimedata-prod-su1.azure-automation.net
ac-agentservice-prod-1.azure-automation.net
Change to these for public cloud:
https://<accountId>.webhook.<region>.azure-automation.net :
Required to start runbooks by doing a POST on webhook URL.
https://<accountId>.agentsvc.<region>.azure-automation.net :
Required for Automation state configuration scenario.
https://<accountId>.jrds.<region>.azure-automation.net :
Required by the hybrid runbook worker for hybrid jobs.
Where
<accountID> would be automation account ID,
<region> would be region code for each automation region.
Fetch the automation account ID from the keys section in the Automation Account blade:
Note: Linux hybrid worker registration will fail with the new URLs unless 1.6.10.2 or the version above is used. For your *NEW* registrations, upgrade to the new version of Linux hybrid worker.
All existing machines will continue working without any issues. The old Automation URLs as mentioned here remain functional to allow time for you to migrate.
Learn more about new DNS records for each region here.