Merge pull request #265918 from ChaseCrum/CEOL-4

EOL message insert

Author: American-Dipper

articles/sentinel/connect-log-forwarder.md

@@ -9,6 +9,9 @@ ms.author: lwainstein
 
 # Deploy a log forwarder to ingest Syslog and CEF logs to Microsoft Sentinel
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 To ingest Syslog and CEF logs into Microsoft Sentinel, particularly from devices and appliances onto which you can't install the Log Analytics agent directly, you'll need to designate and configure a Linux machine that will collect the logs from your devices and forward them to your Microsoft Sentinel workspace. This machine can be a physical or virtual machine in your on-premises environment, an Azure VM, or a VM in another cloud. 
 
 This machine has two components that take part in this process:

articles/sentinel/connect-syslog.md

@@ -9,6 +9,9 @@ ms.author: yelevin
 
 # Collect data from Linux-based sources using Syslog
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 [!INCLUDE [reference-to-feature-availability](includes/reference-to-feature-availability.md)]
 
 **Syslog** is an event logging protocol that is common to Linux. You can use the Syslog daemon built into Linux devices and appliances to collect local events of the types you specify, and have it send those events to Microsoft Sentinel using the **Log Analytics agent for Linux** (formerly known as the OMS agent).

articles/site-recovery/site-recovery-whats-new.md

@@ -14,6 +14,9 @@ ms.custom:
 
 # What's new in Site Recovery
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 The [Azure Site Recovery](site-recovery-overview.md) service is updated and improved on an ongoing basis. To help you stay up-to-date, this article provides you with information about the latest releases, new features, and new content. This page is updated regularly.
 
 You can follow and subscribe to Site Recovery update notifications in the [Azure updates](https://azure.microsoft.com/updates/?product=site-recovery) channel.

articles/site-recovery/vmware-azure-disaster-recovery-powershell.md

@@ -13,6 +13,9 @@ ms.custom: devx-track-azurepowershell
 ---
 # Set up disaster recovery of VMware VMs to Azure with PowerShell
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 In this article, you see how to replicate and failover VMware virtual machines to Azure using Azure PowerShell.
 
 You learn how to:

articles/site-recovery/vmware-azure-install-linux-master-target.md

@@ -13,6 +13,10 @@ ms.date: 08/01/2023
 
 
 # Install a Linux master target server for failback
+
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 After you fail over your virtual machines to Azure, you can fail back the virtual machines to the on-premises site. To fail back, you need to reprotect the virtual machine from Azure to the on-premises site. For this process, you need an on-premises master target server to receive the traffic.
 
 If your protected virtual machine is a Windows virtual machine, then you need a Windows master target. For a Linux virtual machine, you need a Linux master target. Read the following steps to learn how to create and install a Linux master target.

articles/site-recovery/vmware-azure-install-mobility-service.md

@@ -12,6 +12,9 @@ ms.custom: engagement-fy23
 
 # Prepare source machine for push installation of mobility agent
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 When you set up disaster recovery for VMware VMs and physical servers using [Azure Site Recovery](site-recovery-overview.md), you install the [Site Recovery Mobility service](vmware-physical-mobility-service-overview.md) on each on-premises VMware VM and physical server.  The Mobility service captures data writes on the machine, and forwards them to the Site Recovery process server.
 
 ## Install on Windows machine

articles/site-recovery/vmware-azure-mobility-install-configuration-mgr.md

@@ -12,6 +12,9 @@ ms.date: 05/02/2022
 
 # Automate Mobility Service installation
 
+> [!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 automate installation and updates for the Mobility Service agent in [Azure Site Recovery](site-recovery-overview.md).
 
 When you deploy Site Recovery for disaster recovery of on-premises VMware VMs and physical servers to Azure, you install the Mobility Service agent on each machine you want to replicate. The Mobility Service captures data writes on the machine, and forwards them to the Site Recovery process server for replication. You can deploy the Mobility Service in a few ways:

articles/site-recovery/vmware-physical-azure-support-matrix.md

@@ -11,6 +11,9 @@ ms.custom: engagement-fy23
 
 # Support matrix for disaster recovery  of VMware VMs and physical servers to Azure
 
+> [!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 summarizes supported components and settings for disaster recovery of VMware VMs and physical servers to Azure using [Azure Site Recovery](site-recovery-overview.md).
 
 >[!NOTE]

articles/site-recovery/vmware-physical-manage-mobility-service.md

@@ -12,6 +12,9 @@ ms.date: 05/02/2023
 
 # Manage the Mobility agent
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 You set up mobility agent on your server when you use Azure Site Recovery for disaster recovery of VMware VMs and physical servers to Azure. Mobility agent coordinates communications between your protected machine, configuration server/scale-out process server and manages data replication. This article summarizes common tasks for managing mobility agent after it's deployed.
 
 >[!TIP]

articles/site-recovery/vmware-physical-mobility-service-overview.md

@@ -12,6 +12,9 @@ ms.custom: engagement-fy23, linux-related-content
 
 # About the Mobility service for VMware VMs and physical servers
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 When you set up disaster recovery for VMware virtual machines (VM) and physical servers using [Azure Site Recovery](site-recovery-overview.md), you install the Site Recovery Mobility service on each on-premises VMware VM and physical server. The Mobility service captures data, writes on the machine, and forwards them to the Site Recovery process server. The Mobility service is installed by the Mobility service agent software that you can deploy using the following methods:
 
 - [Push installation](#push-installation): When protection is enabled via the Azure portal, Site Recovery installs the Mobility service on the server.