Skip to content

Commit 7f8f89d

Browse files
committed
update
1 parent e60bfe5 commit 7f8f89d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

azure-local/known-issues.md

Lines changed: 2 additions & 2 deletions
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: release-notes
6-
ms.date: 06/12/2025
6+
ms.date: 06/20/2025
77
ms.author: alkohli
88
ms.reviewer: alkohli
99
---
@@ -72,7 +72,7 @@ The following table lists the known issues in this release:
7272
|---------|---------|---------|
7373
| 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. |
7474
| Deployment <!--33153622-->| Updating Azure Arc extensions manually from the Azure Local Machine page via the Azure portal will result in issues during deployment. The extensions that shouldn't be updated manually are: `AzureEdgeDeviceManagement`, `AzureEdgeLifecycleManager`, and `AzureEdgeAKVBackupForWindows`. | Installing extensions manually from the Azure Local machine page is not supported. |
75-
| Update <!--33417006-->| The upgrade banner is currently available for users using the Azure Government cloud. However, the environment checker fails, suggesting that Azure Government clouds are not supported. | There's no workaround in this release. If you encounter this issue, contact Microsoft Support to determine next steps. |
75+
| Upgrade <!--33417006-->| The upgrade banner is currently available for users using the Azure Government cloud. However, the environment checker fails, suggesting that Azure Government clouds are not supported. | There's no workaround in this release. If you encounter this issue, contact Microsoft Support to determine next steps. |
7676

7777

7878
## Known issues from previous releases

0 commit comments

Comments
 (0)