Merge pull request #199157 from davidsmatlak/ds-ghi85238

Updates Logz.io troubleshooting article

Author: 19BMG00

articles/partner-solutions/logzio/troubleshoot.md

@@ -1,15 +1,15 @@
 ---
-title: Logz.io troubleshooting - Azure partner solutions
-description: Learn about how to troubleshoot the Azure integration with Logz.io.
+title: Troubleshooting Logz.io - Azure partner solutions
+description: This article describes how to troubleshoot Logz.io integration with Azure.
 ms.topic: conceptual
-ms.date: 10/25/2021
+ms.date: 05/24/2022
 author: davidsmatlak
 ms.author: davidsmatlak
 ---
 
-# Troubleshoot Logz.io integration with Azure
+# Troubleshooting Logz.io integration with Azure
 
-This article describes how to troubleshoot the Azure integration with Logz.io.
+This article describes how to troubleshoot the Logz.io integration with Azure.
 
 ## Owner role needed to create resource
 
@@ -36,7 +36,7 @@ Use the following patterns to add new values:
 - **Identifier**: `urn:auth0:logzio:<Application ID>`
 - **Reply URL**: `https://logzio.auth0.com/login/callback?connection=<Application ID>`
 
-:::image type="content" source="./media/troubleshoot/basic-saml-config.png" alt-text="Basic SAML configuration settings.":::
+:::image type="content" source="./media/troubleshoot/basic-saml-config.png" alt-text="Screenshot of the Basic SAML configuration settings.":::
 
 ## Logs not being sent to Logz.io
 
@@ -47,19 +47,23 @@ To verify whether a resource is sending logs to Logz.io:
 1. Go to [Azure diagnostic setting](../../azure-monitor/essentials/diagnostic-settings.md) for the specific resource.
 1. Verify that there's a Logz.io diagnostic setting.
 
-:::image type="content" source="./media/troubleshoot/diagnostics.png" alt-text="Diagnostic settings.":::
+:::image type="content" source="./media/troubleshoot/diagnostics.png" alt-text="Screenshot of the Azure monitoring diagnostic settings for Logz.io.":::
+
+## Register resource provider
+
+You must register `Microsoft.Logz` in the Azure subscription that contains the Logz.io resource, and any subscriptions with resources that send data to Logz.io. For more information about troubleshooting resource provider registration, see [Resolve errors for resource provider registration](../../azure-resource-manager/troubleshooting/error-register-resource-provider.md).
 
 ## Limit reached in monitored resources
 
 Azure Monitor Diagnostics supports a maximum of five diagnostic settings on single resource or subscription. When you reach that limit, the resource will show **Limit reached** in **Monitored resources**. You can't add monitoring with Logz.io.
 
-:::image type="content" source="./media/troubleshoot/limit-monitored-resources.png" alt-text="Limit reached for monitored resources.":::
+:::image type="content" source="./media/troubleshoot/limit-monitored-resources.png" alt-text="Screenshot of the Logz configuration's monitored resources that shows the limit is reached.":::
 
 ## VM extension installation failed
 
 A virtual machine (VM) can only be monitored by a single Logz.io account (main or sub). If you try to install the agent on a VM that is already monitored by another account, you see the following error:
 
-:::image type="content" source="./media/troubleshoot/vm-agent-fail.png" alt-text="Virtual machine agent failed installation.":::
+:::image type="content" source="./media/troubleshoot/vm-agent-fail.png" alt-text="Screenshot of a notification that shows the virtual machine agent installation failed.":::
 
 ## Purchase errors