Try it free

Introduction to creating an Azure connection

  • Latest Dynatrace
  • Explanation

Create your first Azure connection to start ingesting topology, metrics, logs, and events from your Azure environment into Dynatrace.

Once you onboard your Azure subscription, Dynatrace SaaS creates a connection to it and performs API calls to your Azure subscription to poll telemetry.

The integration does not deploy or use ActiveGate compute resources inside your Azure subscription to poll telemetry. The experience is transparent and fully managed by Dynatrace SaaS.

You can create your first Azure connection via:

  • Settings Settings app: Create an Azure connection and onboard Azure environments step by step using the onboarding wizard.

  • CLI: Create Azure connections and monitoring configurations using dtctl, the Dynatrace command-line interface.

  • API: Create Azure connections and monitoring configurations via the Dynatrace REST API, using federated identity or client secret authentication.

Limitations

Sovereign clouds

Azure Government and Azure China sovereign clouds are not supported.

Connection limit

A single Dynatrace environment allows up to 500 connections. If you need to exceed this limit, contact Dynatrace support.

One connection per service principal

Each Azure connection requires a dedicated service principal. The same service principal cannot be used across multiple connections.

Deletion is permanent

Deleting an existing Azure connection within Dynatrace permanently deletes its associated monitoring configuration. There is no way to restore it.

Lower limits for free and trial subscriptions

Free and trial Azure subscriptions are subject to lower API rate limits, so throttling may occur more frequently in those environments. See Azure Resource Manager request limits for details on the limits that apply to your subscription type.

Best practices

  • Do not onboard Azure subscriptions already monitored by the classic Azure integration, and avoid monitoring the same subscription across multiple Azure connections—both increase the risk of API throttling and service interruptions.
  • Use a dedicated service principal exclusively for Dynatrace. Do not share it across Dynatrace environments or use it for other non-Dynatrace workloads.
  • Keep the number of monitored resources per service principal under 100,000. Above this threshold, you may see throttling events in your Azure connection health. The actual limit varies depending on the services monitored and the number of metrics collected per resource.
  • If you have a Microsoft Entra Workload Identities Premium license, consider restricting the service principal to the Dynatrace hyperscaler authentication egress IP addresses with a Conditional Access policy. For details, see Microsoft Entra Conditional Access for workload identities.

Troubleshooting

If the same Azure subscription is monitored by more than one connection, see Identify and resolve overlapping Azure subscription monitoring.

Related tags
Infrastructure Observability