updated the note

Author: SnehaSudhirG

articles/automation/automation-update-azure-modules.md

@@ -3,7 +3,7 @@ title: Update Azure PowerShell modules in Azure Automation
 description: This article tells how to update common Azure PowerShell modules provided by default in Azure Automation.
 services: automation
 ms.subservice: process-automation
-ms.date: 07/03/2023
+ms.date: 07/17/2024
 ms.topic: conceptual 
 ms.custom: devx-track-azurepowershell
 ---
@@ -13,7 +13,9 @@ ms.custom: devx-track-azurepowershell
 The most common PowerShell modules are provided by default in each Automation account. See [Default modules](shared-resources/modules.md#default-modules). As the Azure team updates the Azure modules regularly, changes can occur with the included cmdlets. These changes, for example, renaming a parameter or deprecating a cmdlet entirely, can negatively affect your runbooks. 
 
 > [!NOTE]
-> You can't delete global modules, which are modules that Automation provides out of the box.
+> - You can't delete global modules, which are modules that Automation provides out of the box.
+> [!IMPORTANT]
+> - New Runtime environment experience allows you to manage modules and packages by allowing you to configure the job execution environment. In the new experience, Modules and Packages blades are not available. To manage modules and packages, see [Manage Runtime environment and associated runbooks](../manage-runtime-environment.md).
 
 ## Set up an Automation account
 

articles/automation/runtime-environment-overview.md

@@ -3,7 +3,7 @@ title: Runtime environment (preview) in Azure Automation
 description: This article provides an overview on Runtime environment in Azure Automation.
 services: automation
 ms.subservice: process-automation
-ms.date: 04/01/2024
+ms.date: 07/17/2024
 ms.topic: conceptual
 ms.custom: references_regions, devx-track-azurecli
 ---
@@ -83,6 +83,7 @@ You can't edit these Runtime environments. However, any changes that are made in
 - 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](/rest/api/automation/runtime-environments?view=rest-automation-2023-05-15-preview&preserve-view=true).
+- Management of modules for Azure Automation State Configuration is not supported through Runtime environment experience. You can continue using the old experience for managing modules and packages for Azure Automation State Configuration.
 
 ## Switch between new and old experience
 

articles/automation/shared-resources/modules.md

@@ -3,7 +3,7 @@ title: Manage modules in Azure Automation
 description: This article tells how to use PowerShell modules to enable cmdlets in runbooks and DSC resources in DSC configurations.
 services: automation
 ms.subservice: shared-capabilities
-ms.date: 11/01/2021
+ms.date: 07/17/2024
 ms.topic: conceptual 
 ms.custom: devx-track-azurepowershell, devx-track-python
 ---
@@ -21,6 +21,9 @@ Azure Automation uses a number of PowerShell modules to enable cmdlets in runboo
 
 When you create an Automation account, Azure Automation imports some modules by default. See [Default modules](#default-modules).
 
+> [!IMPORTANT]
+> New Runtime environment experience allows you to manage modules and packages by allowing you to configure the job execution environment. In the new experience, Modules and Packages blades are not available. To manage modules and packages, see [Manage Runtime environment and associated runbooks](../manage-runtime-environment.md).
+
 ## Sandboxes
 
 When Automation executes runbook and DSC compilation jobs, it loads the modules into sandboxes where the runbooks can run and the DSC configurations can compile. Automation also automatically places any DSC resources in modules on the DSC pull server. Machines can pull the resources when they apply the DSC configurations.