Skip to content

Cut Azure verification issue from known issues list in azure-local #4175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cpuck wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Cut Azure verification issue from known issues list in azure-local #4175

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions azure-local/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,6 @@ The following table lists the known issues from previous releases:

|Feature |Issue |Workaround |
|---------|---------|---------|
| Azure Verification <!--58937961--> | VMs on Azure Local running Windows Server Azure Edition, Windows 10, or Windows 11 multi-session OS may not activate properly. A pop-up message or a watermark may display, indicating that Windows isn't activated. The VM will function, but the watermark will persist. | There's no known workaround in this release. |
| Add server <br> Repair server <!--32447442--> | The `Add-server` and `Repair-server` cmdlets fail with the error: <br> `Cluster Build ID matches node to add's Build ID`. | Use the OS image of the same solution version as that running on the existing cluster. To get the OS image, identify and download the image version from this [Release table](https://github.com/Azure-Samples/AzureLocal/blob/main/os-image/os-image-tracking-table.md). |
| Deployment <!--33008717--> | In this release and previous releases, registration fails with the following error when you try to register Azure Local machines with Azure Arc: <br>`AZCMAgent command failed with error: >> exitcode: 42. Additional Info: See https://aka.ms/arc/azcmerror`. | For detailed steps on how to resolve this issue, see the [Troubleshooting guide](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/ArcRegistration/TSG-Arc-registration-failing-with-error-42.md). |
Comment on lines 66 to 69
Copy link

Copilot AI Mar 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description says the Azure Verification known issue was fixed in 2509 and should be removed from known-issues lists for 2510 through current, but this change only removes it from the 2602 "Known issues from previous releases" table. The same Azure Verification row () still appears in later version sections (for example 2601, 2512, 2511, and 2510) under "Known issues from previous releases". Please remove that row from those sections as well (leaving it only where historically accurate, e.g., 2509 fixed issues / earlier known issues).

Copilot uses AI. Check for mistakes.
| Azure Local VM management | The Mochostagent service might appear to be running but can get stuck without updating logs for over a month. You can identify this issue by checking the service logs in `C:\programdata\mochostagent\logs` to see if logs are being updated. | Run the following command to restart the mochostagent service: `restart-service mochostagent`. |
Expand Down Expand Up @@ -958,4 +957,4 @@ The following table lists the known issues from previous releases:
## Next steps

- Read the [Deployment overview](./deploy/deployment-introduction.md).
- For more information about previous releases, see [Known issues in Azure Local 23xx releases](previous-releases/known-issues-23.md) and [Known issues in Azure Local 24xx releases](previous-releases/known-issues-24.md).
- For more information about previous releases, see [Known issues in Azure Local 23xx releases](previous-releases/known-issues-23.md) and [Known issues in Azure Local 24xx releases](previous-releases/known-issues-24.md).