Update pre-post-prerequisites.md

[wjpigott]

Added better example of IaM role needed or Custom Role

[prmerger-automator[bot]]

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

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

Learn Build status updates of commit 7da5aef:

:warning: Validation status: warnings

File	Status	Preview URL	Details
articles/update-manager/includes/pre-post-prerequisites.md	:warning:Warning		Details

articles/update-manager/includes/pre-post-prerequisites.md

• Line 24, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
• Line 28, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

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

[Jak-MS]

@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

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

Learn Build status updates of commit ddc04ae:

:warning: Validation status: warnings

File	Status	Preview URL	Details
articles/update-manager/includes/pre-post-prerequisites.md	:warning:Warning		Details

articles/update-manager/includes/pre-post-prerequisites.md

• Line 24, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
• Line 28, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

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

[wjpigott]

@SnehaSudhirG any updates on this merge?

[wjpigott]

@Jak-MS any updates on this article getting changed? Thanks!

[Jak-MS]

@SnehaSudhirG - nudge, can you review this? thanks!

[v-ccolin]

I sent an email to the content owner today.

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

[SnehaSudhirG]

@wjpigott - Thank you for your patience. Awaiting confirmation on this update. Will confirm on this soon.

@v-ccolin - Thanks for the follow-up Will update shortly.

[v-dirichards]

@SnehaSudhirG Have you received confirmation yet? Thanks.

[v-dirichards]

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

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

[ttorble]

I sent email to the content owner today.

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

[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.

[v-ccolin]

I sent an email to the content owner today.

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

[v-dirichards]

I sent a Teams message to the content owner today.

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

[v-dirichards]

@habibaum

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

IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. If the changes no longer apply, add an explanation and a #please-close comment to close the PR.

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

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

Learn Build status updates of commit 9a27323:

:warning: Validation status: warnings

File	Status	Preview URL	Details
articles/update-manager/includes/pre-post-prerequisites.md	:warning:Warning		Details

articles/update-manager/includes/pre-post-prerequisites.md

• Line 24, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
• Line 28, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
• Line 37, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
• Line 47, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

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

Learn Build status updates of commit 9a27323:

:warning: Validation status: warnings

File	Status	Preview URL	Details
articles/update-manager/includes/pre-post-prerequisites.md	:warning:Warning		Details

articles/update-manager/includes/pre-post-prerequisites.md

• Line 24, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
• Line 28, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
• Line 37, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
• Line 47, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[v-dirichards]

@wjpigott Can you fix these errors in the meantime?

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

Learn Build status updates of commit ce99186:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/update-manager/includes/pre-post-prerequisites.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

[prmerger-automator[bot]]

PRMerger Results

Issue	Description
File Change Percent	This PR contains file(s) with more than 30% file change.

[wjpigott]

Removed the indents sorry I wasnt sure who was supposed to remove those. Let me know if anything else is needed.

[v-dirichards]

@habibaum - Would you add a comment to indicate what action to take on this PR?

Thanks!

[habibaum]

@v-dirichards, I have reviewed this PR and am currently waiting for feedback and confirmation from the PM.

[habibaum]

@v-dirichards, i have reviewed this PR and waiting for PM confirmation.

[habibaum]

No response from PM Still waiting for PM confirmation.

[habibaum]

@tbhavya, awaiting your response. I kindly request you to pls confirm.

CC: @JYOTHIRMAISURI

[wjpigott]

Why is it taking a year to get this reviewed??

[habibaum]

@v-dirichards, the PM confirmed the changes are good to publish.

CC: @JYOTHIRMAISURI