Azure Migrate Collector Arc Extension: Clarify troubleshooting and required permissions - #128740
Azure Migrate Collector Arc Extension: Clarify troubleshooting and required permissions#128740Jan-Hendrik Peters (nyanhp) wants to merge 2 commits into
Conversation
|
Jan-Hendrik Peters (@nyanhp) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Jan-Hendrik Peters (@nyanhp) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 01d8eac: ✅ Validation status: passed
For more details, please refer to the build report. |
|
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
|
Jan-Hendrik Peters (@nyanhp), PR is reviewed and request you to make the necessary changes. Thanks. |
|
Learn Build status updates of commit 7f631ec: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Thank you Jan-Hendrik Peters (@nyanhp). |
|
Snehith Muvva (@snehithm), request you to pls review the proposed changes and confirm. |
4 participants
Having recently been stumped by a case in which several machines could not be onboarded, this PR aims to clarify two important bits to check during rollout of the Azure Migrate Collector extension on Arc-enabled servers.
The fact that the RBAC assignment of the
Migrate Arc Discovery Reader - Previewrole is required is easy to miss and hard to see when looking at agent and extension logs.As far as troubleshooting goes, the correct project scope should be included as well. In our case, resources were moved but the migrate project scope was not updated accordingly.