Cut Azure verification issue from known issues list in azure-local#4175
Cut Azure verification issue from known issues list in azure-local#4175cpuck wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
This Azure verification issue was fixed in 2509. It needs to be removed from known issues lists in 2510 -> current.
|
@cpuck : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 6c990b0: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Removes an Azure VM activation (“Azure Verification”) issue from the Azure Local known issues documentation, based on the claim that it was fixed in version 2509.
Changes:
- Removed the “Azure Verification” row from the “Known issues from previous releases” table in the current (2602) section.
- Normalized formatting for the “Next steps” bullet list at the end of the document.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| |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). | |
There was a problem hiding this comment.
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).
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
This Azure verification issue was fixed in 2509. It needs to be removed from known issues lists in 2510 -> current.