Merge pull request #18232 from ronmiab/rb-shireen-2

Remote support - Updated text and images

Author: JamesJBarnett

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

@@ -104,7 +104,7 @@ The following table describes the types of data, their storage location, default
 
 | Types Of data | Description | Data storage location | Default setting | Retention period | How data can be viewed |
 |--|--|--|--|--|--|
-| Telemetry | Telemetry data includes performance metrics, usage patterns, and other information related to user behavior and system health. It doesn't contain any personally identifiable information. | Telemetry data is always stored within the US. | It is enabled by default. To change the default setting, see [Telemetry and diagnostics settings](./telemetry-and-diagnostics-overview.md#telemetry-and-diagnostics-settings). | The data is retained for up to two years. | You can view data in \\\\\<NodeName>\c$\GMACache\TelemetryCache\Tables/\*.tsf. |
+| Telemetry | Telemetry data includes performance metrics, usage patterns, and other information related to user behavior and system health. It doesn't contain any personally identifiable information. | Telemetry data is always stored within the US. | It is enabled by default. For more information on telemetry, see [Telemetry and diagnostics overview](./telemetry-and-diagnostics-overview.md). | The data is retained for up to two years. | You can view data in \\\\\<NodeName>\c$\GMACache\TelemetryCache\Tables/\*.tsf. |
 | Diagnostics | Diagnostics data helps Microsoft detect, diagnose, and fix problems to restore service health and improve products. | Diagnostics data is stored either globally or in the EU, based on the customer’s deployment choice. | Various methods exist to transmit diagnostic data. For details, see [Diagnostics](#diagnostics)| Typically retained for 30 days, potentially longer for ongoing support issues. | You can view data in the `C:\observability` folder of every machine. |
 | Metrics | Metrics are numerical values collected at regular intervals, describing aspects of a system. | Metrics data is sent to the respective region in which resource is deployed. | Enabled by default and can be disabled anytime. | Platform metrics are stored for 93 days, however, you can only query (in the Metrics tile) for a maximum of 30 days' worth of data on any single chart. | You can use metrics explorer to interactively analyze the data in your metric database. |
 | Billing and census | Billing data includes the system ID and the number of physical cores and hours used. Census data is required to enable basic management from Azure and includes system information (system name and ID, system connection status, storage pool ID, trial days remaining and billing model), machine information (number of machines, machine name, OS version, machine manufacturer, model and serial number, number of physical cores and memory size), and basic configuration such as, enablement of Azure verification for VMs, Azure managed identity and diagnostics level setting. | Billing and census data is sent to the respective resource region where the customer registered the device. | Billing is always enabled as it is required to charge for Azure Local usage. Census data is also always enabled, as it includes the minimal information required to manage Azure Local from Azure. | Data is deleted when the resource is deleted, except for billing data, which is retained. | To view billing data, navigate to the Azure Local system resource page in Azure portal, select **Overview** in the left pane, in the Essentials section select the **Billing status** link, followed by **View Cost Management**. To view census data, select **JSON View** located in the top right corner of the Essentials section. |

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

@@ -6,111 +6,110 @@ ms.author: robess
 ms.topic: how-to
 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: 07/31/2025
 ---
 # Azure Local telemetry and diagnostics extension
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2-22h2.md)]
 
-This article provides a brief overview, benefits, and available options for the telemetry and diagnostics extension used for your Azure Local.
+This article gives an overview, lists benefits, and describes options for the telemetry and diagnostics extension in Azure Local.
 
 ## 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.
-
-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.
-
-For more information, see [Azure Arc extension management on Azure Local](../manage/arc-extension-management.md#azure-managed-extensions-in-azure-local).
-
-## Benefits
-
-Some of the advantages of the telemetry and diagnostics extension include:
-
-- **Improved compliance:** Enables the telemetry and diagnostics data to comply with regional service and data residency requirements during data uploads.
-  
-- **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.
-
-- **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
+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.
 
-You maintain control over whether you send telemetry data to Microsoft, even after you've installed and run the telemetry extension.
+:::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":::
 
-To access the options to send telemetry data, follow these steps:
+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.
 
-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":::
+For more information, see [Azure Arc extension management on Azure Local](../manage/arc-extension-management.md#azure-managed-extensions-in-azure-local).
 
-2. Choose one of the following options for sharing telemetry data:
+### 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
+```
 
-   - **Off:** Select this option to not send system data to Microsoft.
+## Benefits
 
-   - **Basic:** Select this option to send Microsoft the minimum system data required to keep systems current, secure, and operating properly.
+Some advantages of the telemetry and diagnostics extension include:
 
-   - **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**.
+- **Improved compliance:** Lets telemetry and diagnostics data comply with regional service and data residency requirements during data uploads.
 
-     Some of the benefits of enhanced data sharing include:
+- **Simplified log gathering and faster case resolution:** Lets you easily collect diagnostics logs. Microsoft Support and the engineering team use these logs to fix system issues quickly.
 
-     - 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.
+- **Reduced update impact:** Lets you update your Azure Local instance without disruption and doesn't require a reboot of the host machine.
 
-## Diagnostic data collection
+- **Resource consumption controls:** Makes sure that no more than 5 percent CPU is used. The Azure Arc extension framework enforces control of the process.
 
-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.
+## Prerequisites
 
-For more information, see [Collect diagnostic logs](../manage/collect-logs.md).
+To use the telemetry and diagnostics extension, make sure you have an Azure Local instance is deployed and running.
 
 ## Data collection consent
 
 Microsoft collects data in accordance with its [standard privacy practices](https://privacy.microsoft.com/). The new telemetry agent doesn't override your existing control setting.
 
 If you withdraw your consent for data collection, any data collected before withdrawal isn't affected. Microsoft continues to handle and use the data collected in accordance with the terms that were in place at the time of the data collection.
 
-Here are a couple of things to consider with data collection:
+Consider these points about data collection:
 
-- Understand how Microsoft handles and uses your data. Review Microsoft's privacy practices and policies.
+- Learn how Microsoft handles and uses your data. Review Microsoft's privacy practices and policies.
 
-- Understand the implications of consenting to data collection and the withdrawal of consent. Consult with legal or privacy professionals to ensure complete understanding.
+- Learn the implications of consenting to data collection and withdrawing consent. Consult legal or privacy professionals to make sure you understand.
 
 ### Data privacy considerations
 
 Azure Local routes system data back to a protected cloud storage location. Only Microsoft personnel with a valid business need are given access to the system data. Microsoft doesn't share personal customer data with third parties, except at the customer's discretion or for the limited purposes described in the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement). Data sharing decisions are made by an internal Microsoft team including privacy, legal, and data management stakeholders.
 
 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.
+## Diagnostic data collection
 
-**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`.
+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:
 
-### Error code 9
+- `Send-DiagnosticData`
+- The Azure portal
 
-**Error message:** There's insufficient disk space available on the drive. To proceed with the extension installation, delete some files to free up space.
+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.
 
-**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.
+For more information, see [Collect diagnostic logs](../manage/collect-logs.md).
 
-**Suggested resolution:** Free up the disk space to allow the extension to continue.
+To collect and send diagnostic logs to Microsoft using the Azure portal, follow these steps:
 
-### Error code 12
+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. Select the **Collect and upload logs** button.
 
-**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.
+:::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":::
 
-**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.
+## Support operations
 
-**Suggested resolution:** Verify Azure Local registration.
+You can grant remote access to Microsoft support by using remote support operations. After you enable 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).
 
 ## Next step