Use Azure Private Link to securely connect networks to Azure Automation (preview)
Azure Private Endpoint is a network interface that connects you privately and securely to a service powered by Azure Private Link. Private Endpoint uses a private IP address from your VNet, effectively bringing the Automation service into your VNet. Network traffic between the machines on the VNet and the Automation account traverses over the VNet and a private link on the Microsoft backbone network, eliminating exposure from the public internet.
For example, you have a VNet where you have disabled outbound internet access. However, you want to access your Automation account privately and use Automation features like Webhooks, State Configuration, and runbook jobs on Hybrid Runbook Workers. Moreover, you want users to have access to the Automation account only through the VNET. Deploying private endpoint achieves these goals.
This article covers when to use and how to set up a private endpoint with your Automation account (preview).
Private Link support with Azure Automation (preview) is available only in Azure Commercial and Azure US Government clouds.
With Private Link you can:
Connect privately to Azure Automation without opening up any public network access.
Connect privately to Azure Monitor Log Analytics workspace without opening any public network access.
This is required if your Automation account is linked to a Log Analytics workspace to forward job data, and when you have enabled features such as Update Management, Change Tracking and Inventory, State Configuration, or Start/Stop VMs during off-hours. For more information about Private Link for Azure Monitor, see Use Azure Private Link to securely connect networks to Azure Monitor.
Ensure your Automation data is only accessed through authorized private networks.
Prevent data exfiltration from your private networks by defining your Azure Automation resource that connects through your private endpoint.
Securely connect your private on-premises network to Azure Automation using ExpressRoute and Private Link.
Keep all traffic inside the Microsoft Azure backbone network.
For more information, see Key Benefits of Private Link.
How it works
Azure Automation Private Link connects one or more private endpoints (and therefore the virtual networks they are contained in) to your Automation Account resource. These endpoints are machines using webhooks to start a runbook, machines hosting the Hybrid Runbook Worker role, and DSC nodes.
After you create private endpoints for Automation, each of the public facing Automation URLs, which you or a machine can directly contact, is mapped to one private endpoint in your VNet.
As part of the preview release, an Automation account cannot access Azure resources that are secured using private endpoint. For example, Azure Key Vault, Azure SQL, Azure Storage Account, etc.
You can start runbooks by doing a POST on the webhook URL. For example, the URL looks like:
State Configuration (agentsvc) scenario
State Configuration provides you with Azure configuration management service that allows you to write, manage, and compile PowerShell Desired State Configuration (DSC) configurations for nodes in any cloud or on-premises datacenter.
The agent on the machine registers with DSC service and then uses the service endpoint to pull DSC configuration. The agent service endpoint looks like:
The URL for public & private endpoint would be the same, however, it would be mapped to a private IP address when Private link is enabled.
Planning based on your network
Before setting up your Automation account resource, consider your network isolation requirements. Evaluate your virtual networks' access to public internet, and the access restrictions to your Automation account (including setting up a Private Link Group Scope to Azure Monitor Logs if integrated with your Automation account). Also include a review of the Automation service DNS records as part of your plan to ensure the supported features work without issue.
Connect to a private endpoint
Create a private endpoint to connect our network. You can create it in the Azure portal Private Link center. Once your changes to publicNetworkAccess and private link are applied, it can take up to 35 minutes for them to take effect.
In this section, you'll create a private endpoint for your Automation account.
On the upper-left side of the screen, select Create a resource > Networking > Private Link Center (Preview).
In Private Link Center - Overview, on the option to Build a private connection to a service, select Start.
In Create a virtual machine - Basics, enter or select the following information:
Setting Value PROJECT DETAILS Subscription Select your subscription. Resource group Select myResourceGroup. You created this in the previous section. INSTANCE DETAILS Name Enter your PrivateEndpoint. Region Select YourRegion.
Select Next: Resource.
In Create a private endpoint - Resource, enter or select the following information:
Setting Value Connection method Select connect to an Azure resource in my directory. Subscription Select your subscription. Resource type Select Microsoft.Automation/automationAccounts. Resource Select myAutomationAccount Target subresource Select Webhook or DSCAndHybridWorker depending on your scenario.
Select Next: Configuration.
In Create a private endpoint - Configuration, enter or select the following information:
Setting Value NETWORKING Virtual network Select MyVirtualNetwork. Subnet Select mySubnet. PRIVATE DNS INTEGRATION Integrate with private DNS zone Select Yes. Private DNS Zone Select (New)privatelink.azure-automation.net
Select Review + create. You're taken to the Review + create page where Azure validates your configuration.
When you see the Validation passed message, select Create.
In the Private Link Center (Preview), select Private endpoints to view your private link resource.
Select the resource to see all the details. This creates a new private endpoint for your Automation account and assigns it a private IP from your virtual network. The Connection status shows as approved.
Similarly, a unique fully qualified domain name (FQDN) is created for the State Configuration (agentsvc) and for the Hybrid Runbook Worker job runtime (jrds). Each of them are assigned a separate IP from your VNet and the Connection status shows as approved.
If the service consumer has RBAC permissions on the Automation resource, they can choose the automatic approval method. In this case, when the request reaches the Automation provider resource, no action is required from the service provider and the connection is automatically approved.
Set public network access flags
You can configure an Automation account to deny all public configurations and allow only connections through private endpoints to further enhance the network security. If you want to restrict access to the Automation account from only within the VNet and not allow access from public internet, you can set
publicNetworkAccess property to
When Deny public network access setting is set to
true, only connections via private endpoints are allowed and all connections via public endpoints are denied with an error message.
The following PowerShell script shows how to
Set the Public Network Access property at the Automation account level:
$account = Get-AzResource -ResourceType Microsoft.Automation/automationAccounts -ResourceGroupName "<resourceGroupName>" -Name "<automationAccountName>" -ApiVersion "2020-01-13-preview" $account.Properties | Add-Member -Name 'publicNetworkAccess' -Type NoteProperty -Value $true $account | Set-AzResource -Force -ApiVersion "2020-01-13-preview"
When connecting to a private link resource using a fully qualified domain name (FQDN) as part of the connection string, it's important to correctly configure your DNS settings to resolve to the allocated private IP address. Existing Azure services might already have a DNS configuration to use when connecting over a public endpoint. Your DNS configuration should be reviewed and updated to connect using your private endpoint.
The network interface associated with the private endpoint contains the complete set of information required to configure your DNS, including FQDN and private IP addresses allocated for a given private link resource.
You can use the following options to configure your DNS settings for private endpoints:
Use the host file (only recommended for testing). You can use the host file on a virtual machine to override using DNS for name resolution first.
Use a private DNS zone. You can use private DNS zones to override the DNS resolution for a particular private endpoint. A private DNS zone can be linked to your virtual network to resolve specific domains. To enable the agent on your virtual machine to communicate over the private endpoint, create a Private DNS record as
privatelink.azure-automation.net. Add a new DNS A record mapping to the IP of the private endpoint.
Use your DNS forwarder (optional). You can use your DNS forwarder to override the DNS resolution for a particular private link resource. If your DNS server is hosted on a virtual network, you can create a DNS forwarding rule to use a private DNS zone to simplify the configuration for all private link resources.
For more information, see Azure Private Endpoint DNS configuration.
To learn more about Private Endpoint, see What is Azure Private Endpoint?.