|
| 1 | +--- |
| 2 | +title: Metrics Not Being Emitted |
| 3 | +description: Resolve the problem in which Datadog doesn't receive metrics from Azure resources because of a missing or incorrect role assignment. |
| 4 | +author: agrimayadav |
| 5 | +ms.author: jarrettr |
| 6 | +ms.service: partner-services |
| 7 | +ms.topic: troubleshooting-problem-resolution |
| 8 | +ms.date: 09/19/2025 |
| 9 | +ai-usage: ai-assisted |
| 10 | + |
| 11 | +#customer intent: As an Azure administrator or user, I want to resolve an issue in which Datadog isn't emitting metrics. |
| 12 | + |
| 13 | +--- |
| 14 | + |
| 15 | +# Metrics not being emitted |
| 16 | + |
| 17 | +## Summary |
| 18 | + |
| 19 | +This article helps you resolve when Datadog isn't receiving metrics from Azure resources because the Datadog resource identity doesn't have the required Monitoring Reader role assignment. |
| 20 | + |
| 21 | +## Prerequisites |
| 22 | + |
| 23 | +- Access to the [Azure portal](https://portal.azure.com) with permissions to view access control (IAM) for the target subscription (Reader) and to assign roles (Contributor/Owner) if you will remediate the problem. |
| 24 | +- The Datadog resource identity (managed identity or service principal) name or principal ID. |
| 25 | + |
| 26 | +## Symptoms |
| 27 | + |
| 28 | +- Metrics from Azure resources don't appear in the Datadog UI. |
| 29 | +- The Datadog resource doesn't show a **Monitoring Reader** role assignment in the subscription's IAM list. |
| 30 | + |
| 31 | +## Cause |
| 32 | + |
| 33 | +Datadog requires the **Monitoring Reader** role on the appropriate Azure subscription to collect platform metrics. If the Datadog resource identity isn't assigned this role, Datadog can't read metrics and they won't be emitted to Datadog. |
| 34 | + |
| 35 | +## Solution |
| 36 | + |
| 37 | +1. In the Azure portal, open the subscription that contains the resource. |
| 38 | + |
| 39 | +1. Select **Access control (IAM)**. |
| 40 | + |
| 41 | +1. On the **Role assignments** tab, search for the Datadog resource name. |
| 42 | + |
| 43 | +1. If you don't find a Monitoring Reader assignment for the Datadog identity, complete these steps to add one: |
| 44 | + |
| 45 | + 1. Select **Add** > **Add role assignment**. |
| 46 | + |
| 47 | + 1. On the **Role** tab, select **Monitoring Reader**, and then select **Next**. |
| 48 | + |
| 49 | + 1. In **Assign access to**, select **Managed identity** or **Service principal** as appropriate. |
| 50 | + |
| 51 | + 1. Select the Datadog resource identity and then choose **Select**. |
| 52 | + |
| 53 | +1. Wait a few minutes for role-based access control (RBAC) propagation, and then verify that Datadog is receiving metrics. |
| 54 | + |
| 55 | +> [!warning] |
| 56 | +> If you remove the system managed identity or the Monitoring Reader role assignment, Datadog can't collect metrics from your Azure resources. |
| 57 | +
|
| 58 | +> [!Note] |
| 59 | +> Confirm that the Datadog identity is the one used by the Datadog integration (managed identity versus service principal). If you assign the role to the wrong principal, Datadog won't receive metrics. |
| 60 | +
|
| 61 | +## Resources |
| 62 | + |
| 63 | +- [Azure role-based access control (RBAC)](/azure/role-based-access-control/) |
| 64 | +- [Assign Azure roles using the Azure CLI](/azure/role-based-access-control/role-assignments-cli) |
| 65 | +- [Datadog Azure integration documentation](https://docs.datadoghq.com/integrations/azure/) |
0 commit comments