Merge pull request #265931 from ChaseCrum/CEOL-10

prmerger-automator[bot] · web-flow · commit 53d687037144 · 2024-02-09T22:50:57.000Z
EOL message insert
diff --git a/articles/automation/automation-linux-hrw-install.md b/articles/automation/automation-linux-hrw-install.md
@@ -10,6 +10,9 @@ ms.topic: conceptual
 
 # Deploy an agent-based Linux Hybrid Runbook Worker in Automation
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 > [!IMPORTANT]
 >  Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on **31 August 2024** and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting **1 November 2023**, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md).
 
diff --git a/articles/automation/change-tracking/overview.md b/articles/automation/change-tracking/overview.md
@@ -10,6 +10,9 @@ ms.topic: conceptual
 
 # Change Tracking and Inventory overview
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 > [!Important]
 > - Change Tracking and Inventory using Log Analytics agent will  retire on **31 August 2024** and we recommend that you use Azure Monitoring Agent as the new supporting agent. Follow the guidelines for  [migration from Change Tracking and inventory using Log Analytics to Change Tracking and inventory using Azure Monitoring Agent version](guidance-migration-log-analytics-monitoring-agent.md).
 
diff --git a/articles/automation/quickstarts/dsc-configuration.md b/articles/automation/quickstarts/dsc-configuration.md
@@ -11,6 +11,9 @@ ms.custom: mvc, mode-other
 
 # Configure a VM with Desired State Configuration
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 By enabling Azure Automation State Configuration, you can manage and monitor the configurations of your Windows and Linux servers using Desired State Configuration (DSC). Configurations that drift from a desired configuration can be identified or auto-corrected. This quickstart steps through enabling an Azure Linux VM and deploying a LAMP stack using Azure Automation State Configuration.
 
 ## Prerequisites
diff --git a/articles/automation/troubleshoot/update-management.md b/articles/automation/troubleshoot/update-management.md
@@ -10,6 +10,9 @@ ms.custom: devx-track-azurepowershell
 
 # Troubleshoot Update Management issues
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 This article discusses issues that you might run into when using the Update Management feature to assess and manage updates on your machines. There's an agent troubleshooter for the Hybrid Runbook Worker agent to help determine the underlying problem. To learn more about the troubleshooter, see [Troubleshoot Windows update agent issues](update-agent-issues.md) and [Troubleshoot Linux update agent issues](update-agent-issues-linux.md). For other feature deployment issues, see [Troubleshoot feature deployment issues](onboarding.md).
 
 >[!NOTE]
diff --git a/articles/automation/update-management/deploy-updates.md b/articles/automation/update-management/deploy-updates.md
@@ -9,6 +9,9 @@ ms.topic: conceptual
 
 # How to deploy updates and review results
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 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.
 
 Under each scenario, the deployment you create targets that selected machine or server, or in the case of creating a deployment from your Automation account, you can target one or more machines. When you schedule an update deployment from an Azure VM or Azure Arc-enabled server, the steps are the same as deploying from your Automation account, with the following exceptions:
diff --git a/articles/automation/update-management/manage-updates-for-vm.md b/articles/automation/update-management/manage-updates-for-vm.md
@@ -9,6 +9,9 @@ ms.date: 08/25/2021
 
 # Manage updates and patches for your VMs
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 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.
 
 > [!NOTE]
@@ -69,4 +72,4 @@ After the deployment is complete, review the process to determine the success of
 
 * To learn how to create alerts to notify you about update deployment results, see [create alerts for Update Management](configure-alerts.md).
 
-* You can [query Azure Monitor logs](query-logs.md) to analyze update assessments, deployments, and other related management tasks. It includes pre-defined queries to help you get started.
+* You can [query Azure Monitor logs](query-logs.md) to analyze update assessments, deployments, and other related management tasks. It includes pre-defined queries to help you get started.
diff --git a/articles/automation/update-management/operating-system-requirements.md b/articles/automation/update-management/operating-system-requirements.md
@@ -9,6 +9,9 @@ ms.topic: conceptual
 
 # Operating systems supported by Update Management
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 This article details the Windows and Linux operating systems supported and system requirements for machines or servers managed by Update Management.
 
 ## Supported operating systems
diff --git a/articles/automation/update-management/overview.md b/articles/automation/update-management/overview.md
@@ -9,6 +9,9 @@ ms.topic: conceptual
 
 # Update Management overview
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 > [!Important]
 > - Azure Automation Update Management will  retire 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) will be [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.
diff --git a/articles/automation/update-management/view-update-assessments.md b/articles/automation/update-management/view-update-assessments.md
@@ -9,6 +9,9 @@ ms.topic: conceptual
 
 # View update assessments in Update Management
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 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.
 
 ## View update assessment
diff --git a/articles/automation/whats-new-archive.md b/articles/automation/whats-new-archive.md
@@ -9,6 +9,9 @@ ms.custom: references_regions
 
 # Archive for What's new in Azure Automation?
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 The primary [What's new in Azure Automation?](whats-new.md) article contains updates for the last six months, while this article contains all the older information.
 
 What's new in Azure Automation? provides you with information about:
