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
Copy file name to clipboardExpand all lines: azure-local/known-issues.md
+6-11Lines changed: 6 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Release notes with fixed and known issues in Azure Local
3
3
description: Read about the known issues and fixed issues in Azure Local.
4
4
author: alkohli
5
5
ms.topic: conceptual
6
-
ms.date: 10/23/2025
6
+
ms.date: 11/03/2025
7
7
ms.author: alkohli
8
8
ms.reviewer: alkohli
9
9
---
@@ -413,7 +413,7 @@ The following table lists the known and expected system behaviors that shouldn't
413
413
414
414
::: moniker-end
415
415
416
-
::: moniker range="=azloc-2505"
416
+
::: moniker range="=azloc-previous"
417
417
418
418
This article identifies critical known issues and their workarounds in Azure Local.
419
419
@@ -441,7 +441,7 @@ Release notes for this version include the issues fixed in this release, known i
441
441
> [!NOTE]
442
442
> For detailed remediation for common known issues, see the [Azure Local Supportability](https://github.com/Azure/AzureStackHCI-Supportability) GitHub repository.
443
443
444
-
## Fixed issues
444
+
###Fixed issues
445
445
446
446
The following table lists the fixed issues in this release:
447
447
@@ -468,7 +468,7 @@ The following table lists the fixed issues in this release:
468
468
| Security management <!--57340784-->| Fixed **Security defaults**, **Application control**, and **Data protections** pages showing as *Unknown* in the security compliance report. ||
469
469
| Add server <br> Repair server <!--32483959-->| Fixed running `Add-server` and `Repair-server` cmdlets with a customized storage adapter IP in Azure Local which resulted in the error: `Type 'ConfigureAzureStackHostStorageAdpaterIPAddressesInAddRepairNode' of Role 'HostNetwork' raised an exception: Connecting to remote server <MACHINE> failed with the following error message: Access is denied.`. ||
470
470
471
-
## Known issues in this release
471
+
###Known issues in this release
472
472
473
473
The following table lists the known issues in this release:
474
474
@@ -478,8 +478,7 @@ The following table lists the known issues in this release:
478
478
| 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 isn't supported. |
479
479
| 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. |
480
480
481
-
482
-
## Known issues from previous releases
481
+
### Known issues from previous releases
483
482
484
483
The following table lists the known issues from previous releases:
485
484
@@ -496,7 +495,7 @@ The following table lists the known issues from previous releases:
496
495
| Upgrade <!--32812323-->| Failed to upgrade cluster with `Get-AzureStackHCI ConnectionStatus` in `RepairRegistration` due to the Virtualization-Based Security (VBS) master key lost during Secure Boot certificate installation. | For detailed steps on how to resolve this issue, see the [Troubleshooting guide](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/BreakFix-Update-Resolve-subscription-status-precheck-failure.md). |
497
496
| Registration <!--32812323-->| After installing certain updates (including BIOS), clusters may report `RepairRegistrationRequired` and show a stale connection state. | For detailed steps on how to resolve this issue, see the [Troubleshooting guide](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/ClusterRegistration/BreakFix-Registration-How-to-resolve-a-repairregistrationrequired-connection-status-after-service-or-bios-updates.md). |
498
497
499
-
## Known and expected behaviors
498
+
###Known and expected behaviors
500
499
501
500
The following table lists the known and expected system behaviors that shouldn't be considered as bugs or limitations.
502
501
@@ -505,10 +504,6 @@ The following table lists the known and expected system behaviors that shouldn't
505
504
| Operating system | Restoring the registry using *RegBack* isn't supported on Azure Local. This operation can remove the Lifecycle Manager (LCM) and Microsoft On-premises Cloud (MOC) settings on your Azure Local instance, which can corrupt the solution. ||
506
505
| Azure Local VM management| Using an exported Azure VM OS disk as a VHD to create a gallery image for provisioning an Azure Local VM is unsupported. | Run the command `restart-service mochostagent` to restart the mochostagent service. |
507
506
508
-
::: moniker-end
509
-
510
-
::: moniker range="=azloc-previous"
511
-
512
507
## Known issues for version 2504
513
508
514
509
For the 2504 release of Azure Local, Microsoft released two security updates: one for existing deployments and another for new deployments. The following table provides information about different deployment types, their corresponding security updates, and OS builds:
0 commit comments