Merge pull request #286743 from SnehaSudhirG/15Sep-AUMV1RetirementUpdate

v-regandowner · web-flow · commit 2b2306b49b10 · 2024-09-15T17:04:56.000-04:00
Added the retirement announcement
diff --git a/articles/automation/includes/automation-update-management-retirement-announcement.md b/articles/automation/includes/automation-update-management-retirement-announcement.md
@@ -0,0 +1,9 @@
+---
+author: SnehaSudhir
+ms.author: sudhirsneha
+ms.topic: include
+ms.date: 09/15/2024
+---
+
+> [!Important]
+> Automation Update Management has retired on **31 August 2024** and we recommend that you use Azure Update Manager. Follow the guidelines for [migration from Automation Update Management to Azure Update Manager](../../update-manager/migration-overview.md).
diff --git a/articles/automation/update-management/configure-alerts.md b/articles/automation/update-management/configure-alerts.md
@@ -10,7 +10,7 @@ ms.service: azure-automation
 
 # How to create alerts for Update Management
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 Alerts in Azure proactively notify you of results from runbook jobs, service health issues, or other scenarios related to your Automation account. Azure Automation does not include pre-configured alert rules, but you can create your own based on data that it generates. This article provides guidance on creating alert rules using the metrics included with Update Management
 
diff --git a/articles/automation/update-management/configure-groups.md b/articles/automation/update-management/configure-groups.md
@@ -3,13 +3,15 @@ title: Use dynamic groups with Azure Automation Update Management
 description: This article tells how to use dynamic groups with Azure Automation Update Management.
 services: automation
 ms.subservice: update-management
-ms.date: 09/10/2024
+ms.date: 09/15/2024
 ms.topic: how-to
 ms.service: azure-automation
 ---
 
 # Use dynamic groups with Update Management
 
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
+
 Update Management allows you to target a dynamic group of Azure or non-Azure VMs for update deployments. Using a dynamic group keeps you from having to edit your deployment to update machines.
 
 > [!NOTE]
diff --git a/articles/automation/update-management/configure-wuagent.md b/articles/automation/update-management/configure-wuagent.md
@@ -9,6 +9,8 @@ ms.service: azure-automation
 ---
 # Configure Windows Update settings for Azure Automation Update Management
 
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
+
 Azure Automation Update Management relies on the [Windows Update client](/windows/deployment/update/windows-update-overview) to download and install Windows updates. There are specific settings that are used by the Windows Update client when connecting to Windows Server Update Services (WSUS) or Windows Update. Many of these settings can be managed with:
 
 - Local Group Policy Editor
diff --git a/articles/automation/update-management/deploy-updates.md b/articles/automation/update-management/deploy-updates.md
@@ -13,7 +13,7 @@ ms.service: azure-automation
 > [!CAUTION]
 > This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 This article describes how to schedule an update deployment and review the process after the deployment is complete. You can configure an update deployment from a selected Azure virtual machine, from the selected Azure Arc-enabled server, or from the Automation account across all configured machines and servers.
 
diff --git a/articles/automation/update-management/enable-from-automation-account.md b/articles/automation/update-management/enable-from-automation-account.md
@@ -11,7 +11,7 @@ ms.service: azure-automation
 
 # Enable Update Management from an Automation account
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 This article describes how you can use your Automation account to enable the [Update Management](overview.md) feature for VMs in your environment, including machines or servers registered with [Azure Arc-enabled servers](../../azure-arc/servers/overview.md). To enable Azure VMs at scale, you must enable an existing Azure VM using Update Management.
 
diff --git a/articles/automation/update-management/enable-from-portal.md b/articles/automation/update-management/enable-from-portal.md
@@ -11,7 +11,7 @@ ms.service: azure-automation
 
 # Enable Update Management from the Azure portal
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 This article describes how you can enable the [Update Management](overview.md) feature for VMs by browsing the Azure portal. To enable Azure VMs at scale, you must enable an existing Azure VM using Update Management.
 
diff --git a/articles/automation/update-management/enable-from-runbook.md b/articles/automation/update-management/enable-from-runbook.md
@@ -4,14 +4,14 @@ description: This article tells how to enable Update Management from a runbook.
 services: automation
 ms.subservice: update-management
 ms.topic: how-to
-ms.date: 09/10/2024
+ms.date: 09/15/2024
 ms.custom: mvc
 ms.service: azure-automation
 ---
 
 # Enable Update Management from a runbook
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 This article describes how you can use a runbook to enable the [Update Management](overview.md) feature for VMs in your environment. To enable Azure VMs at scale, you must enable an existing VM with Update Management.
 
diff --git a/articles/automation/update-management/enable-from-template.md b/articles/automation/update-management/enable-from-template.md
@@ -11,7 +11,7 @@ ms.service: azure-automation
 
 # Enable Update Management using Azure Resource Manager template
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 You can use an [Azure Resource Manager template](../../azure-resource-manager/templates/syntax.md) to enable the Azure Automation Update Management feature in your resource group. This article provides a sample template that automates the following:
 
diff --git a/articles/automation/update-management/enable-from-vm.md b/articles/automation/update-management/enable-from-vm.md
@@ -3,15 +3,15 @@ title: Enable Azure Automation Update Management for an Azure VM
 description: This article tells how to enable Update Management for an Azure VM.
 services: automation
 ms.subservice: update-management
-ms.date: 09/10/2024
+ms.date: 09/15/2024
 ms.topic: how-to
 ms.custom: mvc
 ms.service: azure-automation
 ---
 
 # Enable Update Management for an Azure VM
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 This article describes how you can enable the [Update Management](overview.md) feature on one or more Azure virtual machines (VM). To enable Azure VMs at scale, you must enable an existing Azure VM using Update Management.
 
diff --git a/articles/automation/update-management/manage-updates-for-vm.md b/articles/automation/update-management/manage-updates-for-vm.md
@@ -5,7 +5,7 @@ services: automation
 ms.subservice: update-management
 ms.custom: linux-related-content
 ms.topic: overview
-ms.date: 09/10/2024
+ms.date: 09/15/2024
 ms.service: azure-automation
 ---
 
@@ -14,7 +14,7 @@ ms.service: azure-automation
 > [!CAUTION]
 > This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 Software updates in Azure Automation Update Management provides a set of tools and resources that can help manage the complex task of tracking and applying software updates to machines in Azure and hybrid cloud. An effective software update management process is necessary to maintain operational efficiency, overcome security issues, and reduce the risks of increased cyber security threats. However, because of the changing nature of technology and the continual appearance of new security threats, effective software update management requires consistent and continual attention.
 
diff --git a/articles/automation/update-management/mecmintegration.md b/articles/automation/update-management/mecmintegration.md
@@ -3,14 +3,14 @@ title: Integrate Azure Automation Update Management with Microsoft Configuration
 description: This article tells how to configure Microsoft Configuration Manager with Update Management to deploy software updates to manager clients.
 services: automation
 ms.subservice: update-management
-ms.date: 09/10/2024
+ms.date: 09/15/2024
 ms.topic: overview
 ms.service: azure-automation
 ---
 
 # Integrate Update Management with Microsoft Configuration Manager
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 Customers who have invested in Microsoft Configuration Manager to manage PCs, servers, and mobile devices also rely on its strength and maturity in managing software updates as part of their software update management (SUM) cycle.
 
diff --git a/articles/automation/update-management/operating-system-requirements.md b/articles/automation/update-management/operating-system-requirements.md
@@ -4,7 +4,7 @@ description: This article describes the supported Windows and Linux operating sy
 services: automation
 ms.subservice: update-management
 ms.custom: linux-related-content
-ms.date: 09/10/2024
+ms.date: 09/15/2024
 ms.topic: overview
 ms.service: azure-automation
 ---
@@ -16,7 +16,7 @@ ms.service: azure-automation
 
 This article details the Windows and Linux operating systems supported and system requirements for machines or servers managed by Update Management.
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 ## Supported operating systems
 
diff --git a/articles/automation/update-management/overview.md b/articles/automation/update-management/overview.md
@@ -4,7 +4,7 @@ description: This article provides an overview of the Update Management feature
 services: automation
 ms.subservice: update-management
 ms.custom: linux-related-content
-ms.date: 09/10/2024
+ms.date: 09/15/2024
 ms.topic: overview
 ms.service: azure-automation
 ---
@@ -14,9 +14,10 @@ ms.service: azure-automation
 > [!CAUTION]
 > This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
+
 > [!Important]
-> - Azure Automation Update Management has retired on **31 August 2024**. Follow the guidelines for [migration to Azure Update Manager](../../update-manager/guidance-migration-automation-update-management-azure-update-manager.md).
-> - Azure Log Analytics agent, also known as the Microsoft Monitoring Agent (MMA) has [retired in August 2024](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). Azure Automation Update Management solution relies on this agent and may encounter issues once the agent is retired as it does not work with Azure Monitoring Agent (AMA). Therefore, if you are using the Azure Automation Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. All the capabilities of Azure Automation Update management solution will be available on Azure Update Manager before the retirement date. Follow the [guidance](../../update-center/guidance-migration-automation-update-management-azure-update-manager.md) to move your machines and schedules from Automation Update Management to Azure Update Manager.
+> Azure Log Analytics agent, also known as the Microsoft Monitoring Agent (MMA) has [retired in August 2024](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). Azure Automation Update Management solution relies on this agent and may encounter issues once the agent is retired as it does not work with Azure Monitoring Agent (AMA). Therefore, if you are using the Azure Automation Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. All the capabilities of Azure Automation Update management solution will be available on Azure Update Manager before the retirement date.
 
 You can use Update Management in Azure Automation to manage operating system updates for your Windows and Linux virtual machines in Azure, physical or VMs in on-premises environments, and in other cloud environments. You can quickly assess the status of available updates and manage the process of installing required updates for your machines reporting to Update Management. 
 
diff --git a/articles/automation/update-management/plan-deployment.md b/articles/automation/update-management/plan-deployment.md
@@ -4,14 +4,14 @@ description: This article describes the considerations and decisions to be made
 services: automation
 ms.subservice: update-management
 ms.custom: linux-related-content
-ms.date: 09/10/2024
+ms.date: 09/15/2024
 ms.topic: overview
 ms.service: azure-automation
 ---
 
 # Plan your Update Management deployment
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 ## Step 1: Automation account
 
diff --git a/articles/automation/update-management/pre-post-scripts.md b/articles/automation/update-management/pre-post-scripts.md
@@ -3,16 +3,15 @@ title: Manage pre-scripts and post-scripts in your Update Management deployment
 description: This article tells how to configure and manage pre-scripts and post-scripts for update deployments.
 services: automation
 ms.subservice: update-management
-ms.date: 09/10/2024
+ms.date: 09/15/2024
 ms.topic: how-to 
 ms.custom: devx-track-azurepowershell
 ms.service: azure-automation
 ---
 
 # Manage pre-scripts and post-scripts
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
-
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 Pre-scripts and post-scripts are runbooks to run in your Azure Automation account before (pre-task) and after (post-task) an update deployment. Pre-scripts and post-scripts run in the Azure context, not locally. Pre-scripts run at the beginning of the update deployment. On Windows, post-scripts run at the end of the deployment and after any reboots that are configured. For Linux, post-scripts run after the end of the deployment, not after the machine reboots. 
 
diff --git a/articles/automation/update-management/query-logs.md b/articles/automation/update-management/query-logs.md
@@ -3,13 +3,15 @@ title: Query Azure Automation Update Management logs
 description: This article tells how to query the logs for Update Management in your Log Analytics workspace.
 services: automation
 ms.subservice: update-management
-ms.date: 09/10/2024
+ms.date: 09/15/2024
 ms.topic: how-to
 ms.service: azure-automation
 ---
 
 # Query Update Management logs
 
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
+
 In addition to the details that are provided during Update Management deployment, you can search the logs stored in your Log Analytics workspace. To search the logs from your Automation account, select **Update management** and open the Log Analytics workspace associated with your deployment.
 
 You can also customize the log queries or use them from different clients. See [Log Analytics search API documentation](/rest/api/loganalytics/).
diff --git a/articles/automation/update-management/remove-feature.md b/articles/automation/update-management/remove-feature.md
@@ -9,7 +9,7 @@ ms.custom: mvc
 
 # Remove Update Management from Automation account
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 After you enable management of updates on your virtual machines using Azure Automation Update Management, you may decide to stop using it and remove the configuration from the account and linked Log Analytics workspace.  This article tells you how to completely remove Update Management from the managed VMs, your Automation account, and Log Analytics workspace.
 
diff --git a/articles/automation/update-management/remove-vms.md b/articles/automation/update-management/remove-vms.md
@@ -11,7 +11,7 @@ ms.custom: mvc
 
 # Remove VMs from Update Management
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 When you're finished managing updates on your Azure or non-Azure machines in your environment, you can stop managing them with the [Update Management](overview.md) feature. To stop managing them, you will edit the saved search query `MicrosoftDefaultComputerGroup` in your Log Analytics workspace that is linked to your Automation account.
 
diff --git a/articles/automation/update-management/scope-configuration.md b/articles/automation/update-management/scope-configuration.md
@@ -9,6 +9,8 @@ ms.custom: mvc
 
 # Limit Update Management deployment scope
 
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
+
 This article describes how to work with scope configurations when using the [Update Management](overview.md) feature to deploy updates and patches to your machines. For more information, see [Targeting monitoring solutions in Azure Monitor (Preview)](/previous-versions/azure/azure-monitor/insights/solution-targeting).
 
 ## About scope configurations
diff --git a/articles/automation/update-management/view-update-assessments.md b/articles/automation/update-management/view-update-assessments.md
@@ -14,7 +14,7 @@ ms.service: azure-automation
 > This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
 
-[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+[!INCLUDE [./automation-update-management-retirement-announcement.md](../includes/automation-update-management-retirement-announcement.md)]
 
 
 In Update Management, you can view information about your machines, missing updates, update deployments, and scheduled update deployments. You can view the assessment information scoped to the selected Azure virtual machine, from the selected Azure Arc-enabled server, or from the Automation account across all configured machines and servers.
