Skip to content

Commit e60bfe5

Browse files
committed
update
1 parent e5f87a1 commit e60bfe5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

azure-local/known-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -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 validator fails, suggesting that Azure Government clouds are not supported. | There is no known workaround in this release. |
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. |
7676

7777

7878
## Known issues from previous releases

0 commit comments

Comments
 (0)