Update extension-based-hybrid-runbook-worker.md

[michaelmsonne]

Based on my test and issues me and my college had on this with a Hybrid worker and a custom account (not SYSTEM) at a customer project, we had the same issues with this that the jobs just hang too in "queued" after a reboot of the server where the Plugins "Microsoft.Azure.Automation.HybridWorker.HybridWorkerForWindows" is installed on (works fine until the reboot for many days) - and we find this to: https://learn.microsoft.com/en-us/answers/questions/1434892/permission-required-to-start-azure-runbook-on-hybr

Based on info I got too from the team at MS and based on our test (I'm a Microsoft MVP (https://mvp.microsoft.com/en-US/mvp/profile/b6a5bd91-5ebd-4c84-8965-023a95273093) and a member of the Microsoft CCP program, this is needed to be added to get it to work...

Just tested today for v. 1.13 - so until this is fixed IL will have this added, as that helps a lot if using a custom identity (we had used hours of debugging...)

[prmerger-automator[bot]]

@michaelmsonne : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod[bot]]

Learn Build status updates of commit b488292:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/automation/troubleshoot/extension-based-hybrid-runbook-worker.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@SnehaSudhirG

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

[michaelmsonne]

Any opdate here?

[PMEds28]

@SnehaSudhirG

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

[SnehaSudhirG]

@michaelmsonne - Thank you for your patience. Awaiting confirmation from PM/Engg. Will accordingly update.

[v-ccolin]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[SnehaSudhirG]

@michaelmsonne - Sorry for the delay on this PR. Following up with the team, will update soon. Thank you for your patience.

[Court72]

Hi @SnehaSudhirG - I'm just following up on this PR. Is it ready to be closed or merged?

[SnehaSudhirG]

@Court72 - Sorry about the delay. Will be able to confirm the status of this update by tomorrow

[michaelmsonne]

Any updates here or? :)

[ttorble]

I sent email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[michaelmsonne]

Hi all, I just seen this 2 commits: https://github.com/MicrosoftDocs/azure-docs/commit/c58e8ff26eba3f2ba39b616785e9113e0d0eb2e0 and https://github.com/MicrosoftDocs/azure-docs/commit/463d4fab0c62354f298e366aad4d8dc30ed5b9ec - so I see you all now agreed on my issue here I created but not planned to fix the bug - people need to fix the permission themself..

[v-dirichards]

Hi all, I just seen this 2 commits: c58e8ff and 463d4fa - so I see you all now agreed on my issue here I created but not planned to fix the bug - people need to fix the permission themself..

@SnehaSudhirG -- for review, thanks.

[ttorble]

I sent a Teams message to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[ttorble]

Content owner has updated to say that confirmation is needed for these changes, still in progress and actively monitored.

[SnehaSudhirG]

#sign-off