New feedback updated; added images; sections

Author: SnehaSudhirG

articles/automation/manage-runtime-environment.md

@@ -3,7 +3,7 @@ title: Manage Runtime environment and associated runbooks in Azure Automation
 description: This article tells how to manage runbooks in Runtime environment and associated runbooks Azure Automation
 services: automation
 ms.subservice: process-automation
-ms.date: 12/29/2023
+ms.date: 01/16/2024
 ms.topic: conceptual
 ms.custom: references_regions
 ---
@@ -63,7 +63,7 @@ An Azure Automation account in supported public region (except Central India, Ge
 
        :::image type="content" source="./media/manage-runtime-environment/create-runtime-environment.png" alt-text="Screenshot shows the entries in basics tab of create runtime environment.":::
 
-1. Select **Next** and in the **Packages** tab, upload the packages required during the runbook execution. The *Az PowerShell package* is uploaded by default for all PowerShell Runtime environments, which includes all cmdlets for managing Azure resources. You can choose the version of Az package from the dropdown.
+1. Select **Next** and in the **Packages** tab, upload the packages required during the runbook execution. The *Az PowerShell package* is uploaded by default for all PowerShell Runtime environments, which includes all cmdlets for managing Azure resources. You can choose the version of Az package from the dropdown. Select **None** if you don't want the Package to be uploaded during runbook execution.
 
    :::image type="content" source="./media/manage-runtime-environment/packages-runtime-environment.png" alt-text="Screenshot shows the selections in packages tab of create runtime environment.":::
 
@@ -145,6 +145,15 @@ https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<reso
 ```
 ---
 
+### View components of Az PowerShell package
+
+To view all the component packages of *Az PowerShell package*, run `Get-Module -ListAvailable` cmdlet in a PowerShell runbook. 
+
+Job output would show all the component packages and their versions.
+
+:::image type="content" source="./media/manage-runtime-environment/view-components-powershell-package.png" alt-text="Screenshot shows the components of powershell package." lightbox="./media/manage-runtime-environment/view-components-powershell-package.png":::
+
+
 ### Delete Runtime environment
 
 To delete the Runtime environment from the Automation account, follow these steps:
@@ -265,7 +274,7 @@ https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<reso
 
 ### Update Runbook
 
-You can update runbook by changing the Runtime environment linked to the runbook. You can choose single or multiple runbooks for update.
+You can update runbook by changing the Runtime environment linked to the runbook. You can choose single or multiple runbooks for update. Runbook in running status would not be impacted by changing the Runtime environment linked to that runbook.
 
 #### [Azure portal](#tab/update-runbook-portal)
 1. In your Automation account, under **Process Automation**, select **Runbooks**.
@@ -317,9 +326,10 @@ To test runbook execution before publishing Runtime environment changes, follow
    :::image type="content" source="./media/manage-runtime-environment/access-runbook.png" alt-text="Screenshot shows how to go to Runbooks page to select runbook." lightbox="./media/manage-runtime-environment/access-runbook.png":::
 
 1. In the **Edit runbook** page, select **Edit in Portal** to open the text editor.
-1. The Runtime environment field shows the existing configuration. Select the new Runtime environment from the dropdown list .
+1. The Runtime environment field shows the existing configuration. Select the new Runtime environment from the dropdown list.
 
    :::image type="content" source="./media/manage-runtime-environment/edit-runbook.png" alt-text="Screenshot shows how to select new Runtime environment." lightbox="./media/manage-runtime-environment/edit-runbook.png":::
+
 1. Select **Test pane** to test runbook execution with the updated Runtime environment. Select **Start** to begin the test run.
 1. Close the test pane and make the required changes in Runbook code or Runtime environment if necessary.
 1. Select **Publish** to update the Runtime environment linked to the runbook. 

articles/automation/media/manage-runtime-environment/view-components-powershell-package.png

@@ -3,7 +3,7 @@ title: Add support for Azure CLI in PowerShell 7.2 runbooks in Runtime environme
 titleSuffix: Azure Automation
 description: This article shows how to add support for Azure CLI in PowerShell 7.2 runbooks in Runtime environment.
 services: automation
-ms.date: 01/03/2024
+ms.date: 01/16/2024
 ms.topic: conceptual
 ms.custom: references_regions
 ---
@@ -35,8 +35,11 @@ You can run Azure CLI commands in runbooks linked with PowerShell 7.2 Runtime en
 1. On **Packages** tab, in the **Package version** dropdown list, you would see **Az version 8.3** and **Azure CLI version 2.52.0** already present.
 1. Select **+Add from gallery** to add more packages from gallery and select **Next**.
 1. On **Review + create** tab, review the entries and select **Create**.
-
+      
    A notification appears to confirm that a Runtime environment is successfully created.
+   
+   :::image type="content" source="./media/quickstart-cli-support-powershell-runbook-runtime-environment/create-runtime-environment.png" alt-text="Screenshot shows how to create a runtime environment." lightbox="./media/quickstart-cli-support-powershell-runbook-runtime-environment/create-runtime-environment.png":::
+
 
 ## Create Runbook
 

articles/automation/media/quickstart-cli-support-powershell-runbook-runtime-environment/create-runtime-environment.png

@@ -3,17 +3,17 @@ title: Update PowerShell runbook in Azure Runtime environment
 titleSuffix: Azure Automation
 description: This article shows how to update a runbook from PowerShell 5.1 to PowerShell 7.2 in Runtime environment.
 services: automation
-ms.date: 01/02/2024
+ms.date: 01/16/2024
 ms.topic: conceptual
 ms.custom: references_regions
 ---
 
 # Update runbook from PowerShell 5.1 to PowerShell 7.2
 
-Using the Runtime environment, you can upgrade a runbook from one Runtime version to the other by creating a different Runtime environment and then linking the runbook to it.
+Using the Runtime environment, you can upgrade a runbook from one Runtime version to the other by creating a different Runtime environment and then linking the runbook to it. You can follow similar steps for updating Python runbooks. 
 
 > [!NOTE]
-> A runbook can be mapped to a single Runtime environment, while a specific Runtime environment can be mapped to multiple runbooks.
+> [PowerShell 7.1](https://learn.microsoft.com/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.3#powershell-end-of-support-dates) and [Python 2.7](https://devguide.python.org/versions/) are no longer supported by their respective parent products PowerShell and Python. We recommend that you update outdated runbooks to latest supported versions using Runtime environment.
 
 ## Prerequisites
 

articles/automation/media/runtime-environment-overview/system-generated.png

@@ -3,7 +3,7 @@ title: Runtime environment in Azure Automation
 description: This article provides an overview on Runtime environment in Azure Automation.
 services: automation
 ms.subservice: process-automation
-ms.date: 01/03/2024
+ms.date: 01/16/2024
 ms.topic: conceptual
 ms.custom: references_regions
 ---
@@ -41,6 +41,12 @@ Runtime environment captures the following details about the job execution envir
 > [!NOTE]
 > Azure CLI commands are supported (public preview) in runbooks associated with PowerShell 7.2 Runtime environment. Azure CLI commands version 2.52.0 is available as a default package in PowerShell 7.2 Runtime environment.
 
+## Azure CLI package in Runtime environment 
+
+Azure CLI commands are supported (public preview) in runbooks associated with PowerShell 7.2 Runtime environment. **Azure CLI version 2.56.0** is available as a default package in PowerShell 7.2 Runtime environment. Azure Automation closely follows the release cadence of newer versions of Azure CLI and supports them in runbooks. 
+
+Runbooks linked to PowerShell 7.2 Runtime environment would always execute with the latest Azure CLI version supported by Azure Automation. Likewise, versions declared end-of-support by parent product Azure CLI would no longer be supported by Azure Automation as these could potentially suffer from bugs or security vulnerabilities. Ensure your runbooks are designed to execute seamlessly in newer versions of Azure CLI.
+
 ## System-generated Runtime environments
 
 Azure Automation creates system-generated Runtime environments based on the Runtime language, version, and packages/modules present in your Azure Automation account. There are six system-generated Runtime environments:
@@ -52,12 +58,13 @@ Azure Automation creates system-generated Runtime environments based on the Runt
 - Python-3.8
 - Python-3.10
 
+  :::image type="content" source="./media/runtime-environment-overview/system-generated.png" alt-text="Screenshot shows the system generated Runtime environment." lightbox="./media/runtime-environment-overview/system-generated.png":::
+
 You can't edit these Runtime environments. However, any changes that are made in Modules/Packages for the Automation account are automatically reflected in these system-generated Runtime environments. 
 
 > [!NOTE]
 > Packages present in System-generated Runtime environments are unique to your Azure Automation account and might vary across different accounts. 
 
-
 ## Key Benefits
 
 - **Granular control** - enables you to configure the script execution environment by choosing the Runtime language, its version, and dependent modules.
@@ -74,7 +81,7 @@ You can't edit these Runtime environments. However, any changes that are made in
 - RBAC permissions cannot be assigned to Runtime environment.
 - Runtime environment can't be configured through Azure Automation extension for Visual Studio Code.
 - Deleted Runtime environments cannot be recovered.  
-- The feature is only supported through Azure portal and REST API.
+- The feature is only supported through Azure portal and [REST API](https://review.learn.microsoft.com/rest/api/automation/operation-groups?view=rest-automation-2023-05-15-preview&branch=automation202305).
 
 ## Switch between new and old experience