Ingest telemetry

Learn about the Azure topology.

Learn about the Azure Monitor platform metrics.

Learn about Azure logs and events ingestion.

See the full list of supported Azure services, including topology relationships and available metric collection sets.

Overview

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.

Azure Government and Azure China sovereign clouds are not supported.
Each Azure connection requires a dedicated service principal; the same service principal cannot be used across multiple connections.
Deleting an existing Azure connection within Dynatrace permanently deletes its associated monitoring configuration; there is no way to restore it.
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.

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