Skip to content

Commit 67e4db8

Browse files
committed
Updating Arc extensions OOB
1 parent 9276196 commit 67e4db8

File tree

2 files changed

+6
-2
lines changed

2 files changed

+6
-2
lines changed

azure-local/known-issues.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Release notes with fixed and known issues in Azure Local
33
description: Read about the known issues and fixed issues in Azure Local.
44
author: alkohli
55
ms.topic: conceptual
6-
ms.date: 06/03/2025
6+
ms.date: 06/09/2025
77
ms.author: alkohli
88
ms.reviewer: alkohli
99
---
@@ -70,6 +70,7 @@ The following table lists the known issues in this release:
7070
|Feature |Issue |Workaround |
7171
|---------|---------|---------|
7272
| Update <!--54889342--> | A critical VM operational status not OK alert is shown in the Azure portal under **Update readiness** and in the **Alerts** pane after the update has completed successfully. Additionally, the alert appears when running the `Get-HealthFault` cmdlet. | No action is required on your part. This alert will resolve automatically in a few days. |
73+
| Deployment <!-- 33153622-->| Updating Azure Arc extensions out of band from the **Azure Local Machine** page via the Azure portal will result in issues during deployment. The extensions that shouldn't be updated out of band are: `AzureEdgeDeviceManagement`, `AzureEdgeLifecycleManager`, and `AzureEdgeAKVBackupForWindows`. | The correct versions of these extensions are automatically installed during deployment. |
7374

7475
## Known issues from previous releases
7576

azure-local/manage/arc-extension-management.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: robess
66
ms.topic: how-to
77
ms.custom: devx-track-azurecli, devx-track-azurepowershell
88
ms.reviewer: arduppal
9-
ms.date: 10/22/2024
9+
ms.date: 06/09/2025
1010
---
1111

1212
# Azure Arc extension management on Azure Local
@@ -389,6 +389,9 @@ The manual extension upgrade works like the [Automatic extension upgrade](/azure
389389

390390
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).
391391

392+
> [!NOTE]
393+
> Updating Azure Arc extensions out of band from the **Azure Local Machine** page from the Azure portal will result in issues during deployment.
394+
392395
Use the manual workflow in these scenarios:
393396

394397
- A new version of the extension is available and you want to upgrade it manually.

0 commit comments

Comments
 (0)