Updates

Author: ryanberg-aquent

support/azure/partner-solutions/datadog/installation-fails.md

@@ -14,11 +14,13 @@ ai-usage: ai-assisted
 
 # Datadaog agent installation fails, or default API key is incorrect
 
-The Azure Datadog integration enables you to install Datadog agent on a virtual machine or app service. This article helps you troubleshoot Datadog agent installation failures that are caused by a missing default API key. It also describes how to change the default key.
+## Summary
+
+The Azure Datadog integration enables you to install a Datadog agent on a virtual machine or app service. This article helps you troubleshoot Datadog agent installation failures that are caused by a missing default API key. It also describes how to change the default key.
 
 ## Prerequisites
 
-- Access to the Azure portal with permissions to view or configure the Datadog integration and to restart VMs or app services, if required.
+- Access to the [Azure portal](https://portal.azure.com) with permissions to view or configure the Datadog integration and to restart virutal machines (VMs) or app services if required.
 
 ## Problems and solutions
 
@@ -29,17 +31,19 @@ If a default API key isn't selected, the Datadog agent installation fails.
 #### Solution
 
 1. In the Azure portal, go to the Datadog resource. 
-1. In the left pane, select **Keys** under **Settings**.
-1. Under **API Keys**, select or create a default key.
+1. Select **Settings** > **Keys**.
+1. In **API Keys**, change the default key.
 1. Try again to install the agent. 
 
 ### Problem: Incorrect API key configured on the resource
 
+The API key for the resource is incorrect.
+
 #### Solution
 
 1. In the Azure portal, go to the Datadog resource. 
-1. In the left pane, select, select **Keys** under **Settings**.
-1. Under **API Keys**, change the default key.
+1. Select **Settings** > **Keys**.
+1. In **API Keys**, change the default key.
 1. Uninstall the Datadog agent and reinstall it.
 
 ## Related content

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

@@ -14,27 +14,29 @@ ai-usage: ai-assisted
 
 # Metrics not being emitted
 
-This article helps you resolve the problem in which Datadog isn't receiving metrics from Azure resources because the Datadog resource identity doesn't have the required Monitoring Reader role assignment.
+## Summary
+
+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.
 
 ## Prerequisites
 
-- Access to the Azure portal with permissions to view access control (IAM) for the target subscription (Reader) and to assign roles (Contributor/Owner) if you will remediate the problem.
+- 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.
 - The Datadog resource identity (managed identity or service principal) name or principal ID.
 
 ## Symptoms
 
 - Metrics from Azure resources don't appear in the Datadog UI.
-- The Datadog resource doesn't show a Monitoring Reader role assignment in the subscription's access control (IAM) list.
+- The Datadog resource doesn't show a **Monitoring Reader** role assignment in the subscription's IAM list.
 
 ## Cause
 
-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.
+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. In the Azure portal, open the subscription that contains the resource.
 
-1. Select **Access control (IAM)** in the left pane.
+1. Select **Access control (IAM)**.
 
 1. On the **Role assignments** tab, search for the Datadog resource name.
 
@@ -44,19 +46,19 @@ Datadog requires the Monitoring Reader role on the appropriate Azure subscriptio
 
    1. On the **Role** tab, select **Monitoring Reader**, and then select **Next**.
 
-   1. In **Assign access to**, select managed identity or service principal, as appropriate.
+   1. In **Assign access to**, select **Managed identity** or **Service principal** as appropriate.
 
-   1. Select the Datadog resource identity and then click **Select**.
+   1. Select the Datadog resource identity and then choose **Select**.
 
-1. Wait a few minutes for RBAC propagation, and then verify that Datadog is receiving metrics.
+1. Wait a few minutes for role-based access control (RBAC) propagation, and then verify that Datadog is receiving metrics.
 
 > [!warning]
-> If you remove the system managed identity or the Monitoring Reader role assignment, the Datadog can't collect metrics from your Azure resources.
+> If you remove the system managed identity or the Monitoring Reader role assignment, Datadog can't collect metrics from your Azure resources.
 
 > [!Note]
-> Confirm that 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.
+> 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.
 
-## Related content
+## Resources
 
 - [Azure role-based access control (RBAC)](/azure/role-based-access-control/)
 - [Assign Azure roles using the Azure CLI](/azure/role-based-access-control/role-assignments-cli)