edits

Author: v-albemi

support/azure/partner-solutions/datadog/metrics-not-emitted.md

@@ -28,75 +28,30 @@ This article helps you resolve the problem in which Datadog isn't receiving metr
 
 ## Cause
 
-Datadog requires the Monitoring Reader role on the appropriate scope (Azure subscription or resource group) to collect platform metrics. If the Datadog resource identity isn't assigned this role at the correct scope, Datadog can't read metrics and they won't be emitted to Datadog.
+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.
 
-## Solution 1: Verify role assignment and assign Monitoring Reader
+## Solution 
 
 1. In the Azure portal, open the subscription that contains the resources.
 
-2. Select Access control (IAM) from the left pane.
+1. Select **Access control (IAM)** in the left pane.
 
-3. In the Role assignments tab, search for the Datadog resource name or principal ID.
+1. On the **Role assignments** tab, search for the Datadog resource name.
 
-4. If you do not find a Monitoring Reader assignment for the Datadog identity at the subscription scope, follow these steps to add one:
+1. If you don't find a Monitoring Reader assignment for the Datadog identity, complete these steps to add one:
 
-   1. Select + Add > Add role assignment.
+   1. Select **Add** > **Add role assignment**.
 
-   2. In Role, choose Monitoring Reader.
+   1. On the **Role** tab, select **Monitoring Reader** and then select **Next**.
 
-   3. In Assign access to, choose Managed identity or Service principal as appropriate.
+   1. In **Assign access to**, select managed identity or service principal, as appropriate.
 
-   4. Select the Datadog resource identity and complete the assignment.
+   1. Select the Datadog resource identity and then click **Select**.
 
-5. Wait a few minutes for RBAC propagation, then verify metrics are received in Datadog.
+1. Wait a few minutes for RBAC propagation, and then verify that Datadog is recieving metrics.
 
-## Solution 2: Verify role scope and identity type (CLI/PowerShell)
-
-If you prefer or cannot use the portal, verify the assignment using CLI or PowerShell.
-
-- Azure CLI example (checks role assignments for a principal at subscription scope):
-
-  az role assignment list --assignee {principal-id} --role "Monitoring Reader" --scope "/subscriptions/{subscription-id}" --output table
-
-- PowerShell example (Az module):
-
-  Get-AzRoleAssignment -ObjectId {principal-id} -RoleDefinitionName "Monitoring Reader" -Scope "/subscriptions/{subscription-id}"
-
-If the assignment is missing at the subscription level, create it with Azure CLI:
-
-  az role assignment create --assignee {principal-id} --role "Monitoring Reader" --scope "/subscriptions/{subscription-id}"
-
-Or with PowerShell:
-
-  New-AzRoleAssignment -ObjectId {principal-id} -RoleDefinitionName "Monitoring Reader" -Scope "/subscriptions/{subscription-id}"
-
-Notes:
-
-- Ensure you assign the role at the proper scope: Datadog typically needs subscription-level access for metrics collection across resources. Assigning at a resource group or resource scope limits access to that scope only.
-
-- Confirm the Datadog identity is the one used by the Datadog integration (managed identity vs service principal). If you assign the role to the wrong principal, Datadog will still not receive metrics.
-
-## Determine the cause if role assignment is present
-
-If the Monitoring Reader role is already assigned and metrics are still not emitted, check the following:
-
-- RBAC propagation delay: allow 5–15 minutes after assignment and re-check.
-
-- Disabled or deleted principal: verify the managed identity or service principal is enabled.
-
-- Datadog integration configuration: confirm the integration is configured to use the correct Azure subscription and principal.
-
-- Azure Monitor metric availability: confirm the resource emits metrics to Azure Monitor (some resource types or SKU levels may not emit all metrics).
-
-- Network or service issues in Datadog: check Datadog status and logs for ingestion errors.
-
-## Verify
-
-- In Datadog, open Metrics Explorer or the relevant dashboard and confirm recently emitted metrics appear for the affected resources.
-
-- In the Azure portal, confirm the Datadog identity appears with the Monitoring Reader role assignment at the expected scope.
-
-- Use CLI to list role assignments again and confirm the Monitoring Reader role is present for the Datadog principal.
+> [!Notes]
+> Confirm the Datadog identity is the one used by the Datadog integration (managed identity vs. service principal). If you assign the role to the wrong principal, Datadog won't receive metrics.
 
 ## Related content