Manage your Azure connections

Latest Dynatrace
How-to guide
Published Oct 31, 2025

After you create an Azure connection, you can update its configuration at any time using Settings for a guided UI experience, or the REST API or CLI for automation and scripting.

Settings

Modify Azure connection monitoring configuration via Settings app.

API

Modify Azure connection monitoring configuration via REST API.

CLI

Modify Azure connection monitoring configuration via CLI.

Overview

General recommendations

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.

Limitations

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.