When Dynatrace monitors your Azure environment, it uses a dedicated service principal to authenticate against Azure APIs. By default, this service principal can authenticate from any IP address.
You can configure a Microsoft Entra Conditional Access policy that restricts the service principal to authenticate only from Dynatrace egress IP addresses. The policy limits where the client ID and secret (or federated credential) can be used, which reduces the exposure of the credentials.
If your organization has the Workload Identities Premium license, consider this policy for production environments or wherever your security policy requires least-privilege network access for non-human identities.
To restrict usage of the provided service principal to Dynatrace egress IP addresses only, configure a Conditional Access (CA) policy for workload identities in Microsoft Entra ID. You will need the following details:
Conditional Access (CA) policy for workload identities requires the Workload Identities Premium add-on.
In the Azure portal, go to Microsoft Entra ID > Protection > Conditional Access.
Select Named locations > IP ranges location. Enter a name (for example, Dynatrace egress IPs), select Mark as trusted location, and add each of the IP addresses listed under Hyperscaler authentication for your environment's region. For details, see Dynatrace egress IP addresses.
Select Create.
Select Policies > + New policy and enter a name (for example, Restrict Dynatrace service principal to egress IPs).
Under Assignments > Users, agents or workload identities, select Workload identities. Under Include, select Select service principals and choose the service principal by name or app ID.
Under Assignments > Network, set Include to Any network or location and set Exclude to the Dynatrace egress IPs named location created in step 2.
Under Access controls > Grant, select Block access.
Set Enable policy to On and select Create.
The policy defaults to Report-only mode. Switch to On only after verifying that no other workloads or automation use this service principal from outside the Dynatrace egress IP addresses—enabling it will immediately block all authentication from other locations.
Dynatrace authenticates to Azure from the IP addresses listed in Dynatrace egress IP addresses: Hyperscaler authentication. Use the table for the cloud provider that hosts your Dynatrace environment and the row for its region. Dynatrace doesn't publish IP addresses for GCP-hosted environments, so you can't use this restriction if your environment is hosted on GCP.
Use only the Hyperscaler authentication IP addresses. The data acquisition and OpenPipeline forwarding IP addresses are different for AWS-hosted environments and don't match the sign-in requests from Dynatrace.
Dynatrace can change these IP addresses or add new ones. Check Dynatrace egress IP addresses regularly and update your named location to match.