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
+10-1Lines changed: 10 additions & 1 deletion
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: 07/02/2025
6
+
ms.date: 07/15/2025
7
7
ms.author: alkohli
8
8
ms.reviewer: alkohli
9
9
---
@@ -76,6 +76,15 @@ The following table lists the known issues from previous releases:
76
76
| Deployment <!--33471589-->| After Azure portal deployment, SConfig network settings shows the error: `Set-SCfNetworksetting : Cannot bind argument to parameter 'Value' because it is null.`| There's no known workaround in this release. |
77
77
| Update <!--33448368-->| Cluster-Aware Updating runs might fail with the error:<br>`Type 'SBEPartnerConfirmCauDone' of Role 'SBE' raised an exception:<br>SBE_MsftCIOnlyCommon_CommonForTesting_4.2.2504.16: ErrorID: SBE-CAU-RUNNING-AFTER-DONE -- CAU run is still in progress when it should be done. See https://aka.ms/AzureLocal/SBE/CauHelp for help. Review full Get-CauRun output it identify if it is progressing or stuck. Wait for it to complete if progressing.`| For detailed steps on how to resolve this issue, see the [Troubleshooting guide](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/SolutionExtension/SBE-CAU-RUNNING-AFTER-DONE-Single-node-fail-SBE-Update.md).|
78
78
79
+
## Known and expected behaviors
80
+
81
+
The following table lists the known and expected system behaviors that shouldn't be considered as bugs or limitations.
82
+
83
+
| Feature | Behavior | Workaround |
84
+
|---------|---------|---------|
85
+
| 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. ||
86
+
| 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. |
0 commit comments