Skip to content

Update manage-runtime-environment.md #126184

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.

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
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

SeanMurray-MSFT
Copy link
Contributor

PowerShell 7.4 is available as an option when creating a new runtime environment but is not noted anywhere in this documentation - so using this PR to add this.

We have been instructed by the PG to advise customers to use a PowerShell 7.4 runtime environment as a suggested solution or workaround in certain Automation Runbook scenarios. So, it would be useful to include PowerShell 7.4 in this documentation.

PowerShell 7.4 is available as an option when creating a new runtime environment but is not noted anywhere in this documentation - so using this PR to add this.

We have been instructed by the PG to advise customers to use a PowerShell 7.4 runtime environment as a suggested solution or workaround in certain Automation Runbook scenarios. So, it would be useful to include PowerShell 7.4 in this documentation.
Copy link
Contributor

@SeanMurray-MSFT : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 13e4058:

✅ Validation status: passed

File Status Preview URL Details
articles/automation/manage-runtime-environment.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Mar 11, 2025
@SeanMurray-MSFT
Copy link
Contributor Author

@SnehaSudhirG - can we get an update on this please? This has been flagged by several our engineers. Customers are asking why there is no mention of PS 7.4 in the public Runtime Environment docs. Getting this approval would help alleviate that concern. Thanks.

@v-dirichards
Copy link
Contributor

@SnehaSudhirG - Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

@v-ccolin
Copy link
Contributor

v-ccolin commented May 1, 2025

I sent an email to the content owner today.

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

@v-dirichards
Copy link
Contributor

I sent a Teams message to the content owner today.

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

@v-dirichards v-dirichards assigned habibaum and unassigned SnehaSudhirG Jun 5, 2025
@v-dirichards
Copy link
Contributor

@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

@habibaum
Copy link
Contributor

@jyothisuri, As discussed, I’ve already reviewed this PR and am currently waiting for feedback and confirmation from the PM.

@jyothisuri
Copy link
Contributor

Hi @n-bajaj pls help with review/confirmation. Thanks.
cc
@habibaum

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants