You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article provides a brief overview, benefits, and available options for the telemetry and diagnostics extension used for your Azure Local.
15
+
This article gives an overview, lists benefits, and describes options for the telemetry and diagnostics extension in Azure Local.
16
16
17
17
## About the extension
18
18
@@ -54,31 +54,31 @@ Repair Description: N/A
54
54
55
55
## Benefits
56
56
57
-
Some of the advantages of the telemetry and diagnostics extension include:
57
+
Some advantages of the telemetry and diagnostics extension include:
58
58
59
-
-**Improved compliance:** Enables the telemetry and diagnostics data to comply with regional service and data residency requirements during data uploads.
60
-
61
-
-**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.
59
+
-**Improved compliance:** Lets telemetry and diagnostics data comply with regional service and data residency requirements during data uploads.
62
60
63
-
-**Reduced update impact:**Allows nondisruptive update of your Azure Local instance and doesn't require a reboot of the host machine.
61
+
-**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.
64
62
65
-
-**Resource consumption controls:** Ensures that no more than 5% CPU is consumed. Control of the process is enforced via the Azure Arc extension framework.
63
+
-**Reduced update impact:** Lets you update your Azure Local instance without disruption and doesn't require a reboot of the host machine.
64
+
65
+
-**Resource consumption controls:** Makes sure that no more than 5 percent CPU is used. The Azure Arc extension framework enforces control of the process.
66
66
67
67
## Prerequisites
68
68
69
-
To use the telemetry and diagnostics extension, you must have an Azure Local instance deployed and running.
69
+
To use the telemetry and diagnostics extension, make sure you have an Azure Local instance is deployed and running.
70
70
71
71
## Data collection consent
72
72
73
73
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.
74
74
75
75
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.
76
76
77
-
Here are a couple of things to consider with data collection:
77
+
Consider these points about data collection:
78
78
79
-
-Understand how Microsoft handles and uses your data. Review Microsoft's privacy practices and policies.
79
+
-Learn how Microsoft handles and uses your data. Review Microsoft's privacy practices and policies.
80
80
81
-
-Understand the implications of consenting to data collection and the withdrawal of consent. Consult with legal or privacy professionals to ensure complete understanding.
81
+
-Learn the implications of consenting to data collection and withdrawing consent. Consult legal or privacy professionals to make sure you understand.
82
82
83
83
### Data privacy considerations
84
84
@@ -103,13 +103,13 @@ To collect and send diagnostic logs to Microsoft using the Azure portal, follow
103
103
1. In the left pane, under **Settings**, select **Diagnostics and Remote Support**.
104
104
1. Select **Send logs**.
105
105
1. In the Diagnostics pane, set your **Log start time** and **Log end time**.
106
-
1.Click the **Collect and upload logs** button.
106
+
1.Select the **Collect and upload logs** button.
107
107
108
108
:::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":::
109
109
110
110
## Support operations
111
111
112
-
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).
112
+
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).
This article describes how to install, upgrade, and manage Azure Arc extensions on Azure Local.
16
+
This article explains how to install, upgrade, and manage Azure Arc extensions on Azure Local.
17
17
18
18
## Customer-managed Azure Arc extensions on Azure Local
19
19
@@ -27,11 +27,11 @@ Here are the individual extensions you can install and manage.
27
27
28
28
## Azure-managed extensions in Azure Local
29
29
30
-
Once you've successfully registered your new Azure Local with Azure, Azure-managed extensions are automatically installed on your system. These extensions are essential for the functionality and quality of your system and can't be uninstalled. You can manage the behavior of these extensions in the Azure portal by navigating to the **Extensions** page and selecting the **Settings** menu.
30
+
After you successfully register your new Azure Local with Azure, Azure-managed extensions automatically install on your system. These extensions are essential for your system's functionality and quality, and you can't uninstall them. You can manage extension behavior in the Azure portal on the **Extensions** page by selecting the **Settings** menu.
31
31
32
32
If you have an existing Azure Local that is registered to Azure without these extensions, a banner shows on the **Overview** or **Extensions** page in the Azure portal. You can use the information in the banner to guide you through installing these extensions.
33
33
34
-
Here are the Azure-managed extensions:
34
+
Azure-managed extensions include:
35
35
36
36
-[Telemetry and diagnostics](../concepts/telemetry-and-diagnostics-overview.md)
37
37
-[Remote Support Arc extension](../manage/remote-support-arc-extension.md)
@@ -40,19 +40,19 @@ Here are the Azure-managed extensions:
40
40
41
41
### [Azure portal](#tab/azureportal)
42
42
43
-
You can install extensions from the **Capabilities** tab for your Azure Local Arc-enabled servers as shown in the screenshot. You can use the capabilities tab to install most extensions.
43
+
You can install extensions from the **Capabilities** tab for your Azure Local Arc-enabled servers, as shown in the screenshot. You can use the capabilities tab to install most extensions.
44
44
45
45
:::image type="content" source="media/arc-extension-management/arc-extension-overview.png" alt-text="Screenshot of the Capabilities tab and options in the Azure portal." lightbox="media/arc-extension-management/arc-extension-overview.png":::
46
46
47
-
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.
47
+
Installing an extension in the Azure portal is a cluster-aware operation. The extension installs on all nodes of the system. If you add more nodes to your system, all installed extensions are automatically added to the new servers.
48
48
49
49
### [Azure CLI](#tab/azurecli)
50
50
51
-
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).
51
+
Azure CLI is available to install in Windows, macOS, and Linux environments. You can also run it in Azure Cloud Shell. For more information, refer [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
52
52
53
-
Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to install an extension following these steps:
53
+
Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to install an extension by following these steps:
54
54
55
-
1. Set up parameters from your subscription, resource group, and clusters
55
+
1. Set up parameters for your subscription, resource group, and clusters.
56
56
57
57
```azurecli
58
58
subscription="00000000-0000-0000-0000-000000000000" # Replace with your subscription ID
@@ -63,7 +63,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to install an
63
63
clusters=($(az graph query -q "resources | where type == 'microsoft.azurestackhci/clusters'| where resourceGroup =~ '${resourceGroup}' | project name" | jq -r '.data[].name'))
64
64
```
65
65
66
-
1. To install the Windows Admin Center extension on all the systems under the resource group, run the following command:
66
+
1. Install the Windows Admin Center extension on all the systems under the resource group by running the following command:
67
67
68
68
```azurecli
69
69
extensionName="AdminCenter"
@@ -93,7 +93,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to install an
93
93
done
94
94
```
95
95
96
-
1. To install the Azure Monitor Agent extension on all the systems under the resource group, run the following command:
96
+
1. Install the Azure Monitor Agent extension on all the systems under the resource group by running the following command:
97
97
98
98
```azurecli
99
99
extensionName="AzureMonitorWindowsAgent"
@@ -114,7 +114,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to install an
114
114
done
115
115
```
116
116
117
-
1. To install the Azure Site Recovery extension on all the systems under the resource group, run the following command:
117
+
1. Install the Azure Site Recovery extension on all the systems under the resource group by running the following command:
118
118
119
119
```azurecli
120
120
asrSubscription="00000000-0000-0000-0000-000000000000" # Replace with your ASR subscription ID
@@ -149,11 +149,11 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to install an
149
149
150
150
### [Azure PowerShell](#tab/azurepowershell)
151
151
152
-
Azure PowerShell can be run in Azure Cloud Shell. This document details how to use PowerShell in Azure Cloud Shell. For more information, refer [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
152
+
Run Azure PowerShell in Azure Cloud Shell. This article details how to use PowerShell in Azure Cloud Shell. For more information, see [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
153
153
154
-
Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to install an extension following these steps:
154
+
Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to install an extension by following these steps:
155
155
156
-
1. Set up parameters from your subscription, resource group, and clusters:
156
+
1. Set up parameters for your subscription, resource group, and clusters.
157
157
158
158
```powershell
159
159
$subscription = "00000000-0000-0000-0000-000000000000" # Replace with your subscription ID
@@ -163,7 +163,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to insta
1. To install the Windows Admin Center extension on all the systems under the resource group, run the following command:
166
+
1. Install the Windows Admin Center extension on all the systems under the resource group by running the following command:
167
167
168
168
```powershell
169
169
$extensionName = "AdminCenter"
@@ -200,7 +200,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to insta
200
200
}
201
201
```
202
202
203
-
1. To install the Azure Monitor Agent extension on all the systems under the resource group, run the following command:
203
+
1. Install the Azure Monitor Agent extension on all the systems under the resource group by running the following command:
204
204
205
205
```powershell
206
206
$extensionName = "AzureMonitorWindowsAgent"
@@ -222,7 +222,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to insta
222
222
}
223
223
```
224
224
225
-
1. To install the Azure Site Recovery extension on all the systems under the resource group, create a JSON parameter file and then run the following command:
225
+
1. Install the Azure Site Recovery extension on all the systems under the resource group, create a JSON parameter file, and then run the following command:
226
226
227
227
```powershell
228
228
$settings = @{
@@ -272,9 +272,9 @@ You can check the status of an extension on each server from the **Extensions**
272
272
273
273
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).
274
274
275
-
Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to check the status of an extension following these steps:
275
+
Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to check the status of an extension by following these steps:
276
276
277
-
1. Set up parameters from your subscription, resource group, cluster name, and extension name
277
+
1. Set up parameters for your subscription, resource group, cluster name, and extension name.
278
278
279
279
```azurecli
280
280
subscription="00000000-0000-0000-0000-000000000000" # Replace with your subscription ID
@@ -295,7 +295,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to check the s
295
295
-o table
296
296
```
297
297
298
-
1. To filter out a specific extension like `AzureMonitorWindowsAgent`, run the following command:
298
+
1. To filter out a specific extension, like `AzureMonitorWindowsAgent`, run the following command:
299
299
300
300
```azurecli
301
301
az stack-hci extension list \
@@ -310,7 +310,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to check the s
310
310
311
311
Azure PowerShell can be run in Azure Cloud Shell. This document details how to use PowerShell in Azure Cloud Shell. For more information, refer [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
312
312
313
-
Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to check the status of an extension following these steps:
313
+
Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to check the status of an extension by following these steps:
314
314
315
315
1. Set up parameters from your subscription, resource group, and cluster name
316
316
@@ -322,7 +322,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to check
1. To list all the extensions on a system, run the following command:
325
+
1. List all the extensions on a system by running the following command:
326
326
327
327
```powershell
328
328
foreach ($cluster in $clusters) {
@@ -410,7 +410,7 @@ New-AzStackHciExtension `
410
410
411
411
### Manual extension upgrade via the Azure portal
412
412
413
-
The manual extension upgrade works like the [Automatic extension upgrade](/azure/azure-arc/servers/manage-automatic-vm-extension-upgrade?tabs=azure-portal#how-does-automatic-extension-upgrade-work). On an Azure Local Arc-enabled cluster, when you manually upgrade an extension, Azure saves the version you've selected. Azure then attempts to upgrade the extension on all nodes in the cluster to that version. Make sure that [extensions are supported for manual upgrade](#extensions-not-supported-for-manual-upgrade).
413
+
The manual extension upgrade works like the [Automatic extension upgrade](/azure/azure-arc/servers/manage-automatic-vm-extension-upgrade?tabs=azure-portal#how-does-automatic-extension-upgrade-work). On an Azure Local Arc-enabled cluster, when you manually upgrade an extension, Azure saves the version you selected. Azure then attempts to upgrade the extension on all nodes in the cluster to that version. Make sure that [extensions are supported for manual upgrade](#extensions-not-supported-for-manual-upgrade).
414
414
415
415
On some servers, if the extension upgrade fails, the platform attempts to upgrade to the selected version during the next [Azure Local cloud sync](../faq.yml).
416
416
@@ -431,7 +431,7 @@ To manually upgrade an extension, follow these steps:
431
431
432
432
#### Extensions not supported for manual upgrade
433
433
434
-
Updating Azure Arc extensions manually from the Azure Local Machine page via the Azure portal may result in issues during deployment. The extensions that shouldn't be updated manually are: `AzureEdgeDeviceManagement`, `AzureEdgeLifecycleManager`, and `AzureEdgeAKVBackupForWindows` as shown in the figure.
434
+
Updating Azure Arc extensions manually from the Azure Local Machine page via the Azure portal might result in issues during deployment. The extensions that shouldn't be updated manually are: `AzureEdgeDeviceManagement`, `AzureEdgeLifecycleManager`, and `AzureEdgeAKVBackupForWindows` as shown in the figure.
435
435
436
436
:::image type="content" source="media/arc-extension-management/arc-extension-installation.png" alt-text="Screenshot of extensions that shouldn't be manually updated." lightbox="media/arc-extension-management/arc-extension-installation.png":::
437
437
@@ -476,21 +476,21 @@ If multiple extension upgrades are available for a node, they might be batched t
476
476
477
477
### [Azure portal](#tab/azureportal)
478
478
479
-
If desired, you can uninstall some extensions from your Azure Local in the Azure portal. To uninstall an extension, use these steps:
479
+
If needed, you can uninstall some extensions from your Azure Local in the Azure portal. To uninstall an extension, use these steps:
480
480
481
481
1. Go to the **Extensions page**.
482
-
2. Choose the extension you want to uninstall. The uninstall button isn't available for Azure-managed extensions.
482
+
1. Choose the extension you want to uninstall. The **Uninstall** button isn't available for Azure-managed extensions.
483
483
484
484
:::image type="content" source="media/arc-extension-management/arc-extension-uninstall-extension-1.png" alt-text="Screenshot of how to uninstall an extension in the Azure portal." lightbox="media/arc-extension-management/arc-extension-uninstall-extension-1.png":::
485
485
486
-
3. Select **Uninstall** from the top menu.
487
-
4. Confirm the intent and select **Yes**.
486
+
1. Select **Uninstall** from the top menu.
487
+
1. Confirm that you want to uninstall the extension and select **Yes**.
488
488
489
489
:::image type="content" source="media/arc-extension-management/arc-extension-uninstall-extension-2.png" alt-text="Screenshot of the notification to uninstall an extension in the Azure portal." lightbox="media/arc-extension-management/arc-extension-uninstall-extension-2.png":::
490
490
491
491
### [Azure CLI](#tab/azurecli)
492
492
493
-
To remove a specific extension like `AzureMonitorWindowsAgent`, run the following command:
493
+
To remove a specific extension, like `AzureMonitorWindowsAgent`, run the following command:
494
494
495
495
```azurecli
496
496
extensionName="AzureMonitorWindowsAgent" # Replace with the extension name
@@ -506,7 +506,7 @@ az stack-hci extension delete \
506
506
507
507
### [Azure PowerShell](#tab/azurepowershell)
508
508
509
-
To remove a specific extension like `AzureMonitorWindowsAgent`, run the following command:
509
+
To remove a specific extension, like `AzureMonitorWindowsAgent`, run the following command:
510
510
511
511
```powershell
512
512
$clusterName = "HCICluster" # Replace with your cluster name
0 commit comments