Updated text and images

Author: ronmiab

azure-local/concepts/media/telemetry-and-diagnostics-overview/send-logs-azure-portal.png

@@ -6,9 +6,7 @@ ms.author: robess
 ms.topic: conceptual
 ms.service: azure-local
 ms.reviewer: shisab
-ms.date: 10/22/2024
-
-# CustomerIntent: As a content writer for Azure Local, I want to share viable information on the telemetry and diagnostics extension that will help users understand the feature and ways they can benefit from using it.
+ms.date: 06/18/2025
 ---
 # Azure Local telemetry and diagnostics extension
 
@@ -18,12 +16,20 @@ This article provides a brief overview, benefits, and available options for the
 
 ## About the extension
 
-The Telemetry and Diagnostics Arc extension (shown as AzureEdgeTelemetryAndDiagnostics in the Azure portal) enables the collection of telemetry and diagnostics information from your Azure Local instance. This information helps Microsoft gain valuable insights into the system's behavior.
+The Telemetry and Diagnostics Arc extension, shown as AzureEdgeTelemetryAndDiagnostics in the Azure portal, enables the collection of telemetry and diagnostics information from your Azure Local instance. This data provides Microsoft with valuable insights into the system's behavior.
+
+:::image type="content" source="../concepts/media/telemetry-and-diagnostics-overview/telemetry-diagnostics-extension-1.png" alt-text="Screenshot of the Telemetry and Diagnostics extension in the Azure portal." lightbox="../concepts/media/telemetry-and-diagnostics-overview/telemetry-diagnostics-extension-1.png":::
 
-Use the telemetry and diagnostics extension to monitor and assess the performance, functionality, and overall health of your Azure Local. Microsoft can also use the diagnostics information from this extension to troubleshoot and address any potential issues in your system.
+Use the telemetry and diagnostics extension to monitor and assess the performance, functionality, and overall health of your Azure Local environment. The diagnostic information collection through this extension helps Microsoft more effectively troubleshoot and address any potential issues in your system.
 
 For more information, see [Azure Arc extension management on Azure Local](../manage/arc-extension-management.md#azure-managed-extensions-in-azure-local).
 
+## Prerequisites
+
+To use the telemetry and diagnostics extension, you must have:
+
+- An Azure Local instance deployed and running.
+
 ## Benefits
 
 Some of the advantages of the telemetry and diagnostics extension include:
@@ -32,38 +38,30 @@ Some of the advantages of the telemetry and diagnostics extension include:
 
 - **Simplified log gathering and faster case resolution:** Lets you easily collect diagnostics logs. These logs are used by Microsoft Support and engineering team to resolve any system issues quickly.
 
-- **Reduced update impact:** Allows non-disruptive update of your Azure Local instance and doesn't require a reboot of the host machine.
+- **Reduced update impact:** Allows nondisruptive update of your Azure Local instance and doesn't require a reboot of the host machine.
 
 - **Resource consumption controls:** Ensures that no more than 5% CPU is consumed. Control of the process is enforced via the Azure Arc extension framework.
 
-## Telemetry and diagnostics settings
-
-You maintain control over whether you send telemetry data to Microsoft, even after you've installed and run the telemetry extension.
-
-To access the options to send telemetry data, follow these steps:
-
-1. Go to your Azure Local resource in the Azure portal. In the left-pane, go to **Settings** and then select **Extensions**.
-
-   :::image type="content" source="media/telemetry-and-diagnostics-overview/telemetry-diagnostics-extension-1.png" alt-text="Screenshot of the extension settings screen." lightbox="media/telemetry-and-diagnostics-overview/telemetry-diagnostics-extension-1.png":::
-
-2. Choose one of the following options for sharing telemetry data:
-
-   - **Off:** Select this option to not send system data to Microsoft.
+## Diagnostic data collection
 
-   - **Basic:** Select this option to send Microsoft the minimum system data required to keep systems current, secure, and operating properly.
+To identify and fix issues with your Azure Local solution, you can collect and send diagnostic logs to Microsoft using one of the following methods:
 
-   - **Enhanced:** Select this option to send more system data to help Microsoft identify and fix operational issues and for product improvements. We strongly recommend that you enable **enhanced diagnostics**.
+- `Send-DiagnosticData`
+- The Azure portal
 
-     Some of the benefits of enhanced data sharing include:
+To manually collect and send diagnostic logs to Microsoft, use the `Send-DiagnosticData` cmdlet from any Azure Local machine. We recommend that you use this cmdlet to upload diagnostic data before opening a support case.
 
-     - Retention of system data for up to a month.
-     - Automatic capture of error and diagnostics information for speedier issue resolution. No operator intervention is required.
+For more information, see [Collect diagnostic logs](../manage/collect-logs.md).
 
-## Diagnostic data collection
+To collect and send diagnostic logs to Microsoft using the Azure portal, follow these steps:
 
-To identify and fix issues with your Azure Local solution, you can collect and send diagnostic logs to Microsoft. To manually collect and send diagnostic logs to Microsoft, use the `Send-DiagnosticData` cmdlet from any Azure Local machine. We recommend that you use this cmdlet to upload diagnostic data before opening a support case.
+1. In the Azure portal, navigate to your Azure Local instance.
+1. In the left pane, under **Settings**, select **Diagnostics and Remote Support**.
+1. Select **Send logs**.
+1. In the Diagnostics pane, set your **Log start time** and **Log end time**.
+1. Click the **Collect and upload logs** button.
 
-For more information, see [Collect diagnostic logs](../manage/collect-logs.md).
+:::image type="content" source="../concepts/media/telemetry-and-diagnostics-overview/send-logs-azure-portal.png" alt-text="Screenshot of the steps to collect and send diagnostics logs via the Azure portal." lightbox="../concepts/media/telemetry-and-diagnostics-overview/send-logs-azure-portal.png":::
 
 ## Data collection consent
 
@@ -83,34 +81,41 @@ Azure Local routes system data back to a protected cloud storage location. Only
 
 Don't include any confidential information or personal information in resource or file names. For example, VM names, volume names, configuration file names, storage file names (VHD names), or system resource names.
 
-## Error handling
-
-The following section discusses the error codes, messages and suggested resolution for any issues that you may experience with the telemetry and diagnostics extension:
-
-### Error code 1
-
-**Error message:** An unhandled exception has occurred.
-
-**Cause:** If an unhandled exception occurs, an error message is displayed. You can find the complete error message and its stack trace in the Extension logs.
-
-**Suggested resolution:** Check the generic error message and contact Microsoft Support. Collect the logs from the following path and provide these logs to Microsoft Support:
-`C:\ProgramData\GuestConfig\extension_logs\Microsoft.AzureStack.Observability.TelemetrAndDiagnostics\ObservabilityExtension.log`.
-
-### Error code 9
-
-**Error message:** There's insufficient disk space available on the drive. To proceed with the extension installation, delete some files to free up space.
-
-**Cause:** The extension validates as a pre-installation step and requires a minimum of 20 GB of space for the GMA cache on the system drive. If the drive doesn't have enough space, the extension raises an error message for this issue.
-
-**Suggested resolution:** Free up the disk space to allow the extension to continue.
-
-### Error code 12
-
-**Error message:** The extension can't create the tenant JSON configuration files if either the `Get-AzureStackHCI` or `Get-ClusterNode` cmdlet isn't available to retrieve the necessary information.
-
-**Cause:** The extension uses the `Get-AzureStackHCI` and `Get-ClusterNode` cmdlets to identify parameters and retrieve information needed to create the tenant JSONs. If these cmdlets aren't present, the extension raises an error message with an indication that it can't proceed without them.
-
-**Suggested resolution:** Verify Azure Local registration.
+## Test observability
+
+Test Observability is a feature designed to diagnose issues related to the telemetry and diagnostics extension. This feature ensures the proper functionality of the data transmission pipeline to Microsoft. It validates the existence and accuracy of configuration files, checks the status of relevant services, and confirms endpoint connectivity.
+
+Here's sample output:
+
+```output
+Test-Observability Report 
+Overall Result: PASS
+General Information
+GCSEnvironment:                   DiagnosticsPROD
+GCSGenevaAccount:                 AzureEdgeObsPPE
+GCSNamespace:                     AEOppeDiag
+AEOAssemblyBuild:                 99.9999.0.2
+AEOClusternodeName:               V-HOST1
+AEONodeid:                        cluster-test1
+AEOClusterNodeARCResourceUri:     /Subscription/<subscriptionid>/
+AEODeviceArmResourceUri:          /Subscription/<subscriptionid>/
+AEORegion:                        westeurope
+AEOStampid:                       cluster-test1
+AEOClusterName:                   my-cluster
+AEOOSBuild:                       10.0.25398.763
+Test Name: TestTenantJSON
+Overall Result: PASS 
+Has Repair Action: No 
+Repair Description: N/A
+```
+
+## Support operations
+
+You can grant remote access to Microsoft support by using remote support operations. After enabling remote support, assign a specific access level to Microsoft support based on your requirements. For more information, see [Enable remote support diagnostics](../manage/get-remote-support.md#enable-remote-support-diagnostics) and the [List of Microsoft support operations](../manage/remote-support-arc-extension.md#list-of-microsoft-support-operations).
+
+## Troubleshoot telemetry and diagnostic errors
+
+For information on troubleshootings Arc extension errors, see [Troubleshoot Arc extensions on Azure Local](../manage/troubleshoot-arc-enabled-extensions.md).
 
 ## Next step
 

azure-local/concepts/media/telemetry-and-diagnostics-overview/telemetry-diagnostics-extension-1.png

@@ -6,7 +6,7 @@ ms.author: robess
 ms.topic: how-to
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
 ms.reviewer: arduppal
-ms.date: 10/22/2024
+ms.date: 06/18/2025
 ---
 
 # Azure Arc extension management on Azure Local
@@ -17,7 +17,7 @@ This article describes how to install, upgrade, and manage Azure Arc extensions
 
 ## Customer-managed Azure Arc extensions on Azure Local
 
-You can install, uninstall and update Azure Arc extensions on your Azure Local. Azure Arc lets you run hybrid services like monitoring and Windows Admin Center in the Azure portal.
+You can install, uninstall, and update Azure Arc extensions on your Azure Local. Azure Arc lets you run hybrid services like monitoring and Windows Admin Center in the Azure portal.
 
 Here are the individual extensions you can install and manage.
 
@@ -45,7 +45,7 @@ You can install extensions from the **Capabilities** tab for your Azure Local Ar
 When you install an extension in the Azure portal, it's a cluster-aware operation. The extension is installed on all nodes of the system. If you add more nodes to your system, all the extensions installed on your system are automatically added to the new servers.
 
 ### [Azure CLI](#tab/azurecli)
-Azure CLI is available to install in Windows, macOS and Linux environments. It can also be run in Azure Cloud Shell. For more information, refer [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
+Azure CLI is available to install in Windows, macOS, and Linux environments. It can also be run in Azure Cloud Shell. For more information, refer [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
 
 Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to install an extension following these steps:
 1. Set up parameters from your subscription, resource group, and clusters
@@ -107,7 +107,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to install an
     done
     ```
 
-1. To install the Azure Site Recovery extension on all the systems under the resource group run the following command:
+1. To install the Azure Site Recovery extension on all the systems under the resource group, run the following command:
     ```azurecli
     asrSubscription="00000000-0000-0000-0000-000000000000" # Replace with your ASR subscription ID
     asrResourceGroup="asr-rg" # Replace with your ASR resource group
@@ -253,7 +253,7 @@ You can check the status of an extension on each server from the **Extensions**
 :::image type="content" source="media/arc-extension-management/arc-extension-status-view.png" alt-text="Screenshot of the different extension statuses in the Azure portal." lightbox="media/arc-extension-management/arc-extension-status-view.png":::
 
 ### [Azure CLI](#tab/azurecli)
-Azure CLI is available to install in Windows, macOS and Linux environments. It can also be run in Azure Cloud Shell. For more information, refer [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
+Azure CLI is available to install in Windows, macOS, and Linux environments. It can also be run in Azure Cloud Shell. For more information, refer [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
 
 Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to check the status of an extension following these steps:
 
@@ -316,7 +316,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to check
 
 ## How the extension upgrade works
 
-When published by the extension publisher team, the extension upgrade process replaces the existing extension version with a newly supported one. By default, the automatic extension upgrade feature is enabled for all extensions deployed on Azure Local Arc-enabled clusters unless you explicitly opt-out of automatic upgrades.
+When published by the extension publisher team, the extension upgrade process replaces the existing extension version with a newly supported one. By default, the automatic extension upgrade feature is enabled for all extensions deployed on Azure Local Arc-enabled clusters unless you explicitly opt out of automatic upgrades.
 
 Currently, automatic extension upgrades are only supported in the Windows Admin Center extension, but more extensions will be added in the future.
 
@@ -341,7 +341,7 @@ To enable an automatic upgrade, navigate to the **Extensions** page and perform
     :::image type="content" source="media/arc-extension-management/arc-extension-enable-auto-upgrade-2.png" alt-text="Screenshot of the notification to enable auto upgrade in the Azure portal." lightbox="media/arc-extension-management/arc-extension-enable-auto-upgrade-2.png":::
 
 ### [Azure CLI](#tab/azurecli)
-To install and enable auto upgrade for a specific extension like `AzureMonitorWindowsAgent` run the following command:
+To install and enable auto upgrade for a specific extension like `AzureMonitorWindowsAgent`, run the following command:
 
 ```azurecli
 clusterName="HCICluster" # Replace with your cluster name
@@ -362,7 +362,7 @@ az stack-hci extension create \
 ```
 
 ### [Azure PowerShell](#tab/azurepowershell)
-To install and enable auto upgrade for a specific extension like `AzureMonitorWindowsAgent` run the following command:
+To install and enable auto upgrade for a specific extension like `AzureMonitorWindowsAgent`, run the following command:
 
 ```powershell
 $clusterName = "HCICluster" # Replace with your cluster name
@@ -458,7 +458,7 @@ If desired, you can uninstall some extensions from your Azure Local in the Azure
 
 ### [Azure CLI](#tab/azurecli)
 
-To remove a specific extension like `AzureMonitorWindowsAgent` run the following command:
+To remove a specific extension like `AzureMonitorWindowsAgent`, run the following command:
 ```azurecli
 extensionName="AzureMonitorWindowsAgent" # Replace with the extension name
 resourceGroup="hcicluster-rg" # Replace with your resource group name
@@ -472,7 +472,7 @@ az stack-hci extension delete \
 ```
 
 ### [Azure PowerShell](#tab/azurepowershell)
-To remove a specific extension like `AzureMonitorWindowsAgent` run the following command:
+To remove a specific extension like `AzureMonitorWindowsAgent`, run the following command:
 ```powershell
 $clusterName = "HCICluster" # Replace with your cluster name
 $resourceGroup = "hcicluster-rg" # Replace with your resource group name
@@ -485,17 +485,8 @@ Remove-AzStackHciExtension `
     -ArcSettingName "default" `
     -Name "${extensionName}"
 ```
----
-
-## Troubleshooting extension errors
-
-**Extension Status**: Failed
 
-:::image type="content" source="media/arc-extension-management/arc-extension-troubleshoot-extension-1.png" alt-text="Screenshot of how to troubleshoot an extension in the Azure portal." lightbox="media/arc-extension-management/arc-extension-troubleshoot-extension-1.png":::
-
-**Recommendation**: For an extension with a failed status, select the **Failed (View details)** link. View all the information about the failure and apply the troubleshooting tips.
-
-:::image type="content" source="media/arc-extension-management/arc-extension-troubleshoot-extension-2.png" alt-text="Screenshot of tips to troubleshoot a failed extension." lightbox="media/arc-extension-management/arc-extension-troubleshoot-extension-2.png":::
+---
 
 ## Next step