Updated text

Author: ronmiab

azure-local/concepts/telemetry-and-diagnostics-overview.md

@@ -24,11 +24,33 @@ Use the telemetry and diagnostics extension to monitor and assess the performanc
 
 For more information, see [Azure Arc extension management on Azure Local](../manage/arc-extension-management.md#azure-managed-extensions-in-azure-local).
 
-## Prerequisites
+### Test observability
 
-To use the telemetry and diagnostics extension, you must have:
+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.
 
-- An Azure Local instance deployed and running.
+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
+```
 
 ## Benefits
 
@@ -42,26 +64,11 @@ Some of the advantages of the telemetry and diagnostics extension include:
 
 - **Resource consumption controls:** Ensures that no more than 5% CPU is consumed. Control of the process is enforced via the Azure Arc extension framework.
 
-## Diagnostic data collection
-
-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:
-
-- `Send-DiagnosticData`
-- The Azure portal
-
-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.
-
-For more information, see [Collect diagnostic logs](../manage/collect-logs.md).
-
-To collect and send diagnostic logs to Microsoft using the Azure portal, follow these steps:
+## Prerequisites
 
-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.
+To use the telemetry and diagnostics extension, you must have:
 
-:::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":::
+- An Azure Local instance deployed and running.
 
 ## Data collection consent
 
@@ -81,33 +88,26 @@ 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.
 
-## Test observability
+## Diagnostic data collection
 
-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.
+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:
 
-Here's sample output:
+- `Send-DiagnosticData`
+- The Azure portal
 
-```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
-```
+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.
+
+For more information, see [Collect diagnostic logs](../manage/collect-logs.md).
+
+To collect and send diagnostic logs to Microsoft using the Azure portal, follow these steps:
+
+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.
+
+:::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":::
 
 ## Support operations
 

azure-local/manage/get-remote-support.md

@@ -25,7 +25,7 @@ After you enable remote support, Microsoft support gets just-in-time (JIT) limit
 
 ## Remote support terms and conditions
 
-The following are the data handling terms and conditions for remote access. Carefully read them before granting access.
+The following are the data handling terms and conditions for remote access. Carefully read them before granting access. Everything under this section should be remain as is without making any changes to the text.
 
 > By approving this request, the Microsoft support organization or the Azure engineering team supporting this feature ("Microsoft Support Engineer") will be given direct access to your device for troubleshooting purposes and/or resolving the technical issue described in the Microsoft support case.
 >
@@ -41,18 +41,11 @@ For more information about the personal data that Microsoft processes, how Micro
 
 The high-level workflow to enable remote support is as follows:
 
-- [Remote support extension](./remote-support-arc-extension.md)
 - [Configure proxy settings](#configure-proxy-settings)
 - [Enable remote support via PowerShell](#enable-remote-support-via-powershell)
 - [Submit a support request](#submit-a-support-request)
 - [Other remote support operations](#other-remote-support-operations)
 
-## Remote support extension
-
-The Remote Support Arc extension, listed as **AzureEdgeRemoteSupport** in the Azure portal, makes setup easier and boosts support efficiency. It comes preinstalled on all system nodes, so there's no action for you to take. This extension enables key capabilities like configuring scheduled tasks for [Just Enough Administration](/powershell/scripting/security/remoting/jea/overview?view=powershell-7.5&preserve-view=true) and it lays the groundwork for secure, streamlined support interactions.
-
-For more information about the Remote Support Arc extension, see [Azure Local remote support Arc extension](./remote-support-arc-extension.md).
-
 ## Configure proxy settings
 
 If you use a proxy with Azure Local, add the following endpoints to your allowlist:
@@ -69,6 +62,8 @@ If you use a proxy with Azure Local, add the following endpoints to your allowli
 
 ## Enable remote support via PowerShell
 
+The Remote Support Arc extension, listed as **AzureEdgeRemoteSupport** in the Azure portal, makes setup easier and boosts support efficiency. It comes preinstalled on all system nodes, so there's no action for you to take. For more information about the Remote Support Arc extension, see [Azure Local remote support Arc extension](./remote-support-arc-extension.md).
+
 To enable remote support on your Azure Local, follow these steps:
 
 1. On the client you use to connect to your system, run PowerShell as an admin.
@@ -99,7 +94,7 @@ To enable remote support on your Azure Local, follow these steps:
     Enable-RemoteSupport -AccessLevel <Diagnostics Or DiagnosticsRepair> -ExpireInMinutes <1440>
     ```
 
-    Here's a sample output:
+    Here's sample output:
 
     ```console
     PS C:\Users\Administrator> etsn -ComputerName v-host1 -Credential $cred

azure-local/manage/remote-support-arc-extension.md

@@ -5,7 +5,7 @@ author: ronmiab
 ms.author: robess
 ms.topic: overview
 ms.reviewer: shisab
-ms.lastreviewed: 06/18/2024
+ms.lastreviewed: 06/18/2025
 ms.date: 06/18/2025
 ---