Manage your Azure connections

Latest Dynatrace
How-to guide
Published Oct 31, 2025
Preview

Once you have successfully onboarded your Azure environment, it becomes a Healthy Azure connection.

During Preview, the connection status only reflects the time the connection was on-boarded.

Manage an existing Azure connection

The Azure connections table in Settings > Cloud and Virtualization > Azure (Preview) is your cockpit for managing all the Azure connections.

The Filter all columns field allows you to swiftly filter connections. For example, enter Healthy and it will retrieve all connections with Healthy status.

Select a connection to explore it further by accessing the details window with the Overview and Health tabs.

Overview tab

The Overview tab provides a comprehensive view of your Azure connection's status and configuration.

Telemetry signal charts

The overview displays two real-time charts that show the status of signal ingest over the last 30 minutes:

Azure topology: Displays the number of topology updates received. Use this to verify that resource discovery is working correctly.
Azure Monitor metrics: Displays the count of metrics ingested. Use this to monitor metric collection health and identify changes after enabling new Azure services.

Connection properties

The properties section displays key metadata about your Azure connection:

Property	Description
Connection name	The display name for your connection. Select the pencil icon to rename it.
Service Principal ID	The Application (client) ID of the Azure service principal used for authentication.
Credential type	The authentication method: Client secret or Federated identity.
Created by	The Dynatrace user who created the connection.
Subscriptions	The number of Azure subscriptions being monitored through this connection.
Last modified	The date and time when the connection configuration was last changed.
Created	The date and time when the connection was initially created.

Health tab

The Health tab provides visibility into connection health and helps you troubleshoot issues.

General section

The General section displays three key health indicators:

Indicator	Description
Status	Current connection health status with a descriptive message (for example, "Connection is healthy and data is being ingested.")
Entra ID authentication errors	Count of authentication errors over the last 6 hours. A chart displays error distribution over time.
Throttling events	Count of Azure API throttling events over the last 6 hours. A chart shows when throttling occurred.

Connection status types

There are several connection status types:

Pending: During onboarding, the connection is initially in the Pending status until all onboarding steps are completed.
Healthy: The Dynatrace SaaS platform successfully authenticated using the provided Azure credentials. This does not necessarily mean that all signals are successfully polled or ingested.
Unhealthy: The Dynatrace SaaS platform was unable to authenticate using the provided Azure credentials. The connection is not functioning correctly.
Inactive: A user-generated status when a connection is disabled. All poll-based signal ingest is suspended. You cannot change monitoring settings or view the health status while in this state.

During the Preview, only Pending and Healthy connection statuses are supported.

Connection logs

The Connection logs section displays a searchable table of log events related to your connection. Use this to investigate errors and troubleshoot issues.

The log table includes the following columns:

Column	Description
`timestamp`	The date and time when the event occurred.
`da.clouds.status`	The status of the event (for example, `ERROR`, `INFO`).
`da.clouds.source`	The source component (for example, `azure-metric-poller`).
`da.clouds.content`	A brief description of the event (for example, `Throttling`).

You can:

Search and filter log entries using the search field.
Open logs in other tools using the Open with option.
Show or hide additional columns.
Adjust the number of rows displayed per page.

Microsoft Entra ID authentication and authorization

A Healthy connection indicates successful authentication against your Microsoft Entra ID tenant.

When transitioning to an Unhealthy status, authentication errors appear in the Entra ID authentication errors chart and are logged to the connection logs section.

Service principal permissions may change over time. Missing Azure RBAC permissions do not impact connection status but will affect functionality.

Customize your monitoring settings

To customize your monitoring settings, select Manage in the upper-right corner of the overview window. Your current settings depend on your onboarding flow.

In the Manage window, you can customize the following settings:

Azure Monitor metrics

Use this section to enable or disable Azure services and configure their metric collection sets.

Enabling services: Schedules the metric poller to fetch Azure Monitor metrics at 5-minute intervals.
Monitored regions: Limits metric polling to specific Azure regions you choose to enable.

Monitored regions do not affect the topology service. Topology polling covers the entire tenant based on the permissions granted to the service principal.

Azure tag enrichment

Use this section to specify Azure tag keys that enrich supported signals such as Azure Monitor metrics.

Tag (key + value) length cannot exceed 23 characters.
Tags must use allowed characters: ^[a-zA-Z0-9_.: -/]*$

Tag enrichment notes

Changes can take up to 15 minutes to propagate.
Tag enrichment requires the signal to be linked to an entity.

Dynatrace attribute enrichment

This feature enables advanced platform use cases by enriching signals with well-known Dynatrace attributes. This supports capabilities such as fine-grained permissions.

You can set attribute values in two ways:

Literal values: Specify a custom arbitrary value directly.
Azure tag: Reference an Azure tag key name, which resolves to the tag value at runtime.

These capabilities are powered by primary Grail tags.

When using Azure tags for attribute enrichment, changes can take up to 15 minutes to propagate.

Delete a connection

Connections may need to be deleted and/or re-created. For now, to completely delete a connection:

In the Azure Portal

Log in to your Azure Portal and go to Microsoft Entra ID > App Registrations.
Search for the related app registration matching your Dynatrace Azure connection.
Select Delete.

In Dynatrace

Go to Settings > Cloud and Virtualization > Azure (Preview) to access all Azure connections.
Find and select the connection action menu on the right.
Select Delete.

During the Preview you may be asked to re-create your connection.

Disable a connection

You may face use cases which require disabling a connection

Sudden API throttling due to multiple Azure API consumers.
Sudden rise in signals ingest count which cannot be attributed to configuration changes on your side.
Act upon a request from a Dynatrace support specialist, for troubleshooting purposes.
Suspend the connection due to maintenance work on the Azure subscription.

If you disable a connection, its status will change into Inactive.

A disabled connection in an Inactive status does NOT delete existing data points or any configurations. It only suspends the connection.

To resume the suspended connection

Go to Settings > Cloud and Virtualization > Azure (Preview) to access all Azure connections.
Find and select the connection action menu on the right.
Select Enable.

The enabled connection will change from Inactive to either Healthy or Unhealthy.

Paths and customizations

—Auto-enabled (not possible to disable/configure)

—Fully customizable

Topology is core auto-enabled signal in all paths; it's not possible to disable it.

The Recommended path auto-enables signals with customizations possible after a successful onboarding.

The Advanced path allows you to customize most of the signals as well as monitoring settings while onboarding.

⁴

In connection management, it's possible to customize all supported monitoring settings features.

Limitations

For now, the Health tab contains only visual designs and example data.
For now, only Pending and Healthy statuses are supported, the support is only during onboarding.