DNS records for Azure regions used by Azure Automation
The Azure Automation service uses a number of DNS records for features to connect to the service. If you have an Automation account that's defined for a specific region, you can restrict communication to that regional datacenter. You might need to know these records to allow the following Automation features to work when it is hosted behind a firewall:
- Hybrid Runbook Worker
- State Configuration
- Webhooks
Note
Linux Hybrid Runbook Worker registration will fail with the new records unless it is version 1.6.10.2 or higher. You must upgrade to a newer version of the Log Analytics agent for Linux in order for the machine to receive an updated version of the worker role and use these new records. Existing machines will continue working without any issues.
DNS records per region
The following table provides the DNS record for each region.
Note
While the list of Automation DNS records provided here have been retired, they still remain functional to allow time for you to migrate to the new records listed under support for Private Link and prevent failures with your automation processes.
| Region | DNS record |
|---|---|
| Australia Central | ac-jobruntimedata-prod-su1.azure-automation.netac-agentservice-prod-1.azure-automation.net |
| Australia East | ae-jobruntimedata-prod-su1.azure-automation.netae-agentservice-prod-1.azure-automation.net |
| Australia South East | ase-jobruntimedata-prod-su1.azure-automation.netase-agentservice-prod-1.azure-automation.net |
| Canada Central | cc-jobruntimedata-prod-su1.azure-automation.netcc-agentservice-prod-1.azure-automation.net |
| Central India | cid-jobruntimedata-prod-su1.azure-automation.netcid-agentservice-prod-1.azure-automation.net |
| East US 2 | eus2-jobruntimedata-prod-su1.azure-automation.neteus2-agentservice-prod-1.azure-automation.net |
| Japan East | jpe-jobruntimedata-prod-su1.azure-automation.netjpe-agentservice-prod-1.azure-automation.net |
| North Europe | ne-jobruntimedata-prod-su1.azure-automation.netne-agentservice-prod-1.azure-automation.net |
| South Central US | scus-jobruntimedata-prod-su1.azure-automation.netscus-agentservice-prod-1.azure-automation.net |
| South East Asia | sea-jobruntimedata-prod-su1.azure-automation.netsea-agentservice-prod-1.azure-automation.net |
| Switzerland North | stzn-jobruntimedata-prod-su1.azure-automation.netstzn-agentservice-prod-su1.azure-automation.net |
| UK South | uks-jobruntimedata-prod-su1.azure-automation.netuks-agentservice-prod-1.azure-automation.net |
| US Gov Virginia | usge-jobruntimedata-prod-su1.azure-automation.us usge-agentservice-prod-1.azure-automation.us |
| West Central US | wcus-jobruntimedata-prod-su1.azure-automation.netwcus-agentservice-prod-1.azure-automation.net |
| West Europe | we-jobruntimedata-prod-su1.azure-automation.netwe-agentservice-prod-1.azure-automation.net |
| West US 2 | wus2-jobruntimedata-prod-su1.azure-automation.netwus2-agentservice-prod-1.azure-automation.net |
Support for Private Link
To support Private Link in Azure Automation, the DNS records for every supported datacenter have been updated. Instead of region-specific URLs, the URLs are Automation account specific.
| Region | DNS record |
|---|---|
| South Africa North | https://<accountId>.webhook.san.azure-automation.nethttps://<accountId>.agentsvc.san.azure-automation.nethttps://<accountId>.jrds.san.azure-automation.net |
| East Asia | https://<accountId>.webhook.ea.azure-automation.nethttps://<accountId>.agentsvc.ea.azure-automation.nethttps://<accountId>.jrds.ea.azure-automation.net |
| South East Asia | https://<accountId>.webhook.sea.azure-automation.nethttps://<accountId>.agentsvc.sea.azure-automation.nethttps://<accountId>.jrds.sea.azure-automation.net |
| Australia Central | https://<accountId>.webhook.ac.azure-automation.nethttps://<accountId>.agentsvc.ac.azure-automation.nethttps://<accountId>.jrds.ac.azure-automation.net |
| Australia Central 2 | https://<accountId>.webhook.cbr2.azure-automation.nethttps://<accountId>.agentsvc.cbr2.azure-automation.nethttps://<accountId>.jrds.cbr2.azure-automation.net |
| Australia South East | https://<accountId>.webhook.ase.azure-automation.nethttps://<accountId>.agentsvc.ase.azure-automation.nethttps://<accountId>.jrds.ase.azure-automation.net |
| Australia East | https://<accountId>.webhook.ae.azure-automation.nethttps://<accountId>.agentsvc.ae.azure-automation.nethttps://<accountId>.jrds.ae.azure-automation.net |
| Brazil South | https://<accountId>.webhook.brs.azure-automation.nethttps://<accountId>.agentsvc.brs.azure-automation.nethttps://<accountId>.jrds.brs.azure-automation.net |
| Brazil Southeast | https://<accountId>.webhook.brse.azure-automation.nethttps://<accountId>.agentsvc.brse.azure-automation.nethttps://<accountId>.jrds.brse.azure-automation.net |
| Canada Central | https://<accountId>.webhook.cc.azure-automation.nethttps://<accountId>.agentsvc.cc.azure-automation.nethttps://<accountId>.jrds.cc.azure-automation.net |
| China East 2 | https://<accountId>.webhook.sha2.azure-automation.cnhttps://<accountId>.agentsvc.sha2.azure-automation.cnhttps://<accountId>.jrds.sha2.azure-automation.cn |
| China North | https://<accountId>.webhook.bjb.azure-automation.cnhttps://<accountId>.agentsvc.bjb.azure-automation.cnhttps://<accountId>.jrds.bjb.azure-automation.cn |
| China North 2 | https://<accountId>.webhook.bjs2.azure-automation.cnhttps://<accountId>.agentsvc.bjs2.azure-automation.cnhttps://<accountId>.jrds.bjs2.azure-automation.cn |
| West Europe | https://<accountId>.webhook.we.azure-automation.nethttps://<accountId>.agentsvc.we.azure-automation.nethttps://<accountId>.jrds.we.azure-automation.net |
| North Europe | https://<accountId>.webhook.ne.azure-automation.nethttps://<accountId>.agentsvc.ne.azure-automation.nethttps://<accountId>.jrds.ne.azure-automation.net |
| France Central | https://<accountId>.webhook.fc.azure-automation.nethttps://<accountId>.agentsvc.fc.azure-automation.nethttps://<accountId>.jrds.fc.azure-automation.net |
| France South | https://<accountId>.webhook.mrs.azure-automation.nethttps://<accountId>.agentsvc.mrs.azure-automation.nethttps://<accountId>.jrds.mrs.azure-automation.net |
| Germany West Central | https://<accountId>.webhook.dewc.azure-automation.dehttps://<accountId>.agentsvc.dewc.azure-automation.dehttps://<accountId>.jrds.dewc.azure-automation.de |
| Central India | https://<accountId>.webhook.cid.azure-automation.nethttps://<accountId>.agentsvc.cid.azure-automation.nethttps://<accountId>.jrds.cid.azure-automation.net |
| South India | https://<accountId>.webhook.ma.azure-automation.nethttps://<accountId>.agentsvc.ma.azure-automation.nethttps://<accountId>.jrds.ma.azure-automation.net |
| Japan East | https://<accountId>.webhook.jpe.azure-automation.nethttps://<accountId>.agentsvc.jpe.azure-automation.nethttps://<accountId>.jrds.jpe.azure-automation.net |
| Japan West | https://<accountId>.webhook.jpw.azure-automation.nethttps://<accountId>.agentsvc.jpw.azure-automation.nethttps://<accountId>.jrds.jpw.azure-automation.net |
| Korea Central | https://<accountId>.webhook.kc.azure-automation.nethttps://<accountId>.agentsvc.kc.azure-automation.nethttps://<accountId>.jrds.kc.azure-automation.net |
| Korea South | https://<accountId>.webhook.ps.azure-automation.nethttps://<accountId>.agentsvc.ps.azure-automation.nethttps://<accountId>.jrds.ps.azure-automation.net |
| Norway East | https://<accountId>.webhook.noe.azure-automation.nethttps://<accountId>.agentsvc.noe.azure-automation.nethttps://<accountId>.jrds.noe.azure-automation.net |
| Norway West | https://<accountId>.webhook.now.azure-automation.nethttps://<accountId>.agentsvc.now.azure-automation.nethttps://<accountId>.jrds.now.azure-automation.net |
| Switzerland West | https://<accountId>.webhook.stzw.azure-automation.nethttps://<accountId>.agentsvc.stzw.azure-automation.nethttps://<accountId>.jrds.stzw.azure-automation.net |
| UAE Central | https://<accountId>.webhook.auh.azure-automation.nethttps://<accountId>.agentsvc.auh.azure-automation.nethttps://<accountId>.jrds.auh.azure-automation.net |
| UAE North | https://<accountId>.webhook.uaen.azure-automation.nethttps://<accountId>.agentsvc.uaen.azure-automation.nethttps://<accountId>.jrds.uaen.azure-automation.net |
| UK West | https://<accountId>.webhook.cw.azure-automation.nethttps://<accountId>.agentsvc.cw.azure-automation.nethttps://<accountId>.jrds.cw.azure-automation.net |
| UK South | https://<accountId>.webhook.uks.azure-automation.nethttps://<accountId>.agentsvc.uks.azure-automation.nethttps://<accountId>.jrds.uks.azure-automation.net |
| Central US | https://<accountId>.webhook.cus.azure-automation.nethttps://<accountId>.agentsvc.cus.azure-automation.nethttps://<accountId>.jrds.cus.azure-automation.net |
| East US | https://<accountId>.webhook.eus.azure-automation.nethttps://<accountId>.agentsvc.eus.azure-automation.nethttps://<accountId>.jrds.eus.azure-automation.net |
| East US 2 | https://<accountId>.webhook.eus2.azure-automation.nethttps://<accountId>.agentsvc.eus2.azure-automation.nethttps://<accountId>.jrds.eus2.azure-automation.net |
| North Central US | https://<accountId>.webhook.ncus.azure-automation.nethttps://<accountId>.agentsvc.ncus.azure-automation.nethttps://<accountId>.jrds.ncus.azure-automation.net |
| South Central US | https://<accountId>.webhook.scus.azure-automation.nethttps://<accountId>.agentsvc.scus.azure-automation.nethttps://<accountId>.jrds.scus.azure-automation.net |
| West Central US | https://<accountId>.webhook.wcus.azure-automation.nethttps://<accountId>.agentsvc.wcus.azure-automation.nethttps://<accountId>.jrds.wcus.azure-automation.net |
| West US | https://<accountId>.webhook.wus.azure-automation.nethttps://<accountId>.agentsvc.wus.azure-automation.nethttps://<accountId>.jrds.wus.azure-automation.net |
| West US 2 | https://<accountId>.webhook.wus2.azure-automation.nethttps://<accountId>.agentsvc.wus2.azure-automation.nethttps://<accountId>.jrds.wus2.azure-automation.net |
| West US 3 | https://<accountId>.webhook.usw3.azure-automation.nethttps://<accountId>.agentsvc.usw3.azure-automation.nethttps://<accountId>.jrds.usw3.azure-automation.net |
| US Gov Virginia | https://<accountId>.webhook.usge.azure-automation.ushttps://<accountId>.agentsvc.usge.azure-automation.ushttps://<accountId>.jrds.usge.azure-automation.us |
| US Gov Texas | https://<accountId>.webhook.ussc.azure-automation.ushttps://<accountId>.agentsvc.ussc.azure-automation.ushttps://<accountId>.jrds.ussc.azure-automation.us |
| US Gov Arizona | https://<accountId>.webhook.phx.azure-automation.ushttps://<accountId>.agentsvc.phx.azure-automation.ushttps://<accountId>.jrds.phx.azure-automation.us |
Replace <accountId> in the DNS record with GUID representing your Automation Account ID from the value URL. You can get the ID required from Keys under Account Settings in the Azure portal.
Copy the value after accounts/ from the URL field - https://<GUID>.agentsvc.<region>.azure-automation.net/accounts/<GUID>
Note
All of the Webhook and agentservice DNS records have been updated to the new style DNS records to support Private Link. For JRDS DNS records, both old and new style DNS records are supported. If you are not using Private Link, you will see the old style DNS records, while those using Private Link will see new style of DNS records.
We recommend that you use the addresses listed when defining exceptions. For a list of region IP addresses instead of region names, download the JSON file from the Microsoft Download Center for the following cloud environments:
- Azure IP Ranges and Service Tags - Azure public
- Azure IP Ranges and Service Tags- Azure Government
- Azure IP Ranges and Service Tags - Azure Germany
- Azure IP Ranges and Service Tags - Azure China Vianet 21
The IP address file lists the IP address ranges that are used in the Microsoft Azure datacenters. It includes compute, SQL, and storage ranges, and reflects currently deployed ranges and any upcoming changes to the IP ranges. New ranges that appear in the file aren't used in the datacenters for at least one week.
It's a good idea to download the new IP address file every week. Then, update your site to correctly identify services running in Azure.
Note
If you're using Azure ExpressRoute, remember that the IP address file is used to update the Border Gateway Protocol (BGP) advertisement of Azure space in the first week of each month.
Next steps
To learn how to troubleshoot your Hybrid Runbook Workers, see Troubleshoot Hybrid Runbook Worker issues.
To learn how to troubleshoot issues with State Configuration, see Troubleshoot State Configuration issues.
Feedback
Submit and view feedback for