Merge pull request #265921 from ChaseCrum/CEOL-5

American-Dipper · web-flow · commit 06924d283efd · 2024-02-09T13:44:52.000-08:00
EOL Message insert
diff --git a/articles/azure-arc/servers/agent-release-notes-archive.md b/articles/azure-arc/servers/agent-release-notes-archive.md
@@ -8,6 +8,9 @@ ms.custom: references_regions
 
 # Archive for What's new with Azure Connected Machine agent
 
+> [!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 Connected Machine agent?](agent-release-notes.md) article contains updates for the last six months, while this article contains all the older information.
 
 The Azure Connected Machine agent receives improvements on an ongoing basis. This article provides you with information about:
diff --git a/articles/azure-arc/servers/manage-agent.md b/articles/azure-arc/servers/manage-agent.md
@@ -9,6 +9,9 @@ ms.custom:
 
 # Managing and maintaining the Connected Machine agent
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 After initial deployment of the Azure Connected Machine agent, you may need to reconfigure the agent, upgrade it, or remove it from the computer. These routine maintenance tasks can be done manually or through automation (which reduces both operational error and expenses). This article describes the operational aspects of the agent. See the [azcmagent CLI documentation](azcmagent.md) for command line reference information.
 
 ## Installing a specific version of the agent
diff --git a/articles/azure-arc/servers/manage-vm-extensions.md b/articles/azure-arc/servers/manage-vm-extensions.md
@@ -7,6 +7,9 @@ ms.topic: conceptual
 
 # Virtual machine extension management with Azure Arc-enabled servers
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 Virtual machine (VM) extensions are small applications that provide post-deployment configuration and automation tasks on Azure VMs. For example, if a virtual machine requires software installation, anti-virus protection, or to run a script in it, a VM extension can be used.
 
 Azure Arc-enabled servers enables you to deploy, remove, and update Azure VM extensions to non-Azure Windows and Linux VMs, simplifying the management of your hybrid machine through their lifecycle. VM extensions can be managed using the following methods on your hybrid machines or servers managed by Arc-enabled servers:
diff --git a/articles/azure-arc/servers/plan-evaluate-on-azure-virtual-machine.md b/articles/azure-arc/servers/plan-evaluate-on-azure-virtual-machine.md
@@ -7,6 +7,9 @@ ms.topic: conceptual
 
 # Evaluate Azure Arc-enabled servers on an Azure virtual machine
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 Azure Arc-enabled servers is designed to help you connect servers running on-premises or in other clouds to Azure. Normally, you would not use Azure Arc-enabled servers on an Azure virtual machine because all the same capabilities are natively available for these VMs, including a representation of the VM in Azure Resource Manager, VM extensions, managed identities, and Azure Policy. If you attempt to install Azure Arc-enabled servers on an Azure VM, you'll receive an error message stating that it is unsupported and the agent installation will be canceled.
 
 While you cannot install Azure Arc-enabled servers on an Azure VM for production scenarios, it is possible to configure Azure Arc-enabled servers to run on an Azure VM for *evaluation and testing purposes only*. This article will help you set up an Azure VM before you can enable Azure Arc-enabled servers on it.
diff --git a/articles/azure-arc/servers/prerequisites.md b/articles/azure-arc/servers/prerequisites.md
@@ -8,6 +8,9 @@ ms.custom: devx-track-azurepowershell
 
 # Connected Machine agent prerequisites
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 This topic describes the basic requirements for installing the Connected Machine agent to onboard a physical server or virtual machine to Azure Arc-enabled servers. Some [onboarding methods](deployment-options.md) may have more requirements.
 
 ## Supported environments
diff --git a/articles/azure-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md b/articles/azure-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
@@ -4,16 +4,20 @@ description: This article explains the steps to cleanly remove your VMware vCent
 author: Farha-Bano
 ms.author: v-farhabano
 manager: jsuri
-ms.topic: how-to 
+ms.topic: how-to
 ms.date: 11/30/2023
 ms.service: azure-arc
 ms.subservice: azure-arc-vmware-vsphere
 ms.custom:
 # Customer intent: As an infrastructure admin, I want to cleanly remove my VMware vCenter environment from Azure Arc-enabled VMware vSphere.
+
 ---
 
 # Remove your VMware vCenter  environment from Azure Arc
 
+> [!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 learn how to cleanly remove your VMware vCenter environment from Azure Arc-enabled VMware vSphere. For VMware vSphere environments that you no longer want to manage with Azure Arc-enabled VMware vSphere, follow the steps in the article to:
 
 1. Remove guest management from VMware virtual machines
@@ -23,7 +27,7 @@ In this article, you learn how to cleanly remove your VMware vCenter environment
 ## 1. Remove guest management from VMware virtual machines
 
 To prevent continued billing of Azure management services after you remove the vSphere environment from Azure Arc, you must first cleanly remove guest management from all Arc-enabled VMware vSphere virtual machines where it was enabled.
-When you enable guest management on Arc-enabled VMware vSphere virtual machines, the Arc connected machine agent is installed on them. 
+When you enable guest management on Arc-enabled VMware vSphere virtual machines, the Arc connected machine agent is installed on them.
 
 Once guest management is enabled, you can install VM extensions on them and use Azure management services like the Log Analytics on them.
 To cleanly remove guest management, you must follow the steps below to remove any VM extensions from the virtual machine, disconnect the agent, and uninstall the software from your virtual machine. It's important to complete each of the three steps to fully remove all related software components from your virtual machines.
@@ -110,7 +114,7 @@ To run the deboarding script, follow these steps:
 2. Run the following command to allow the script to run because it's an unsigned script. (If you close the session before you complete all the steps, run this command again for the new session.)
 
     ```powershell-interactive
-    Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass 
+    Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
     ```
 3. Run the script.
 
@@ -126,7 +130,7 @@ To run the deboarding script, follow these steps:
 
 - **ApplianceConfigFilePath (optional)**: Path to kubeconfig, output from deploy command. Providing applianceconfigfilepath also deletes the appliance VM running on the vCenter.
 
-- **Force**: Using the Force flag deletes all the Azure resources without reaching resource bridge. Use this option if resource bridge VM isn't in running state.  
+- **Force**: Using the Force flag deletes all the Azure resources without reaching resource bridge. Use this option if resource bridge VM isn't in running state.
 
 ### Remove VMware vSphere resources from Azure manually
 
@@ -147,7 +151,7 @@ If you aren't using the deboarding script, follow these steps to remove the VMwa
 
 6. Select **Remove from Azure**.
 
-    This action only removes these resource representations from Azure. The resources continue to remain in your vCenter. 
+    This action only removes these resource representations from Azure. The resources continue to remain in your vCenter.
 
 7. Do the steps 4, 5, and 6 for **Resources pools/clusters/hosts**, **Templates**, **Networks**, and **Datastores**
 
diff --git a/articles/azure-arc/vmware-vsphere/troubleshoot-guest-management-issues.md b/articles/azure-arc/vmware-vsphere/troubleshoot-guest-management-issues.md
@@ -10,10 +10,14 @@ ms.author: v-farhabano
 manager: jsuri
 
 # Customer intent: As a VI admin, I want to understand the troubleshooting process for guest management issues.
+
 ---
 # Troubleshoot Guest Management for Linux VMs
 
-This article provides information on how to troubleshoot and resolve the issues that can occur while you enable guest management on Arc-enabled VMware vSphere virtual machines.  
+> [!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 provides information on how to troubleshoot and resolve the issues that can occur while you enable guest management on Arc-enabled VMware vSphere virtual machines.
 
 ## Troubleshoot issues while enabling Guest Management on a domain-joined Linux VM
 
@@ -51,7 +55,7 @@ Default: The default set of PAM service names includes:
 
 ## Troubleshoot issues while enabling Guest Management on RHEL-based Linux VMs
 
-Applies to: 
+Applies to:
 
 - RedHat Linux
 - CentOS
@@ -71,7 +75,7 @@ Before you enable the guest agent, follow these steps on the VM:
 
 1. Create file `vmtools_unconfined_rpm_script_kcs5347781.te` using the following:
 
-     `policy_module(vmtools_unconfined_rpm_script_kcs5347781, 1.0) 
+     `policy_module(vmtools_unconfined_rpm_script_kcs5347781, 1.0)
      gen_require(`
      type vmtools_unconfined_t;
      ')
@@ -111,4 +115,4 @@ If you don't see your problem here or you can't resolve your issue, try one of t
 
 - Connect with [@AzureSupport](https://twitter.com/azuresupport), the official Microsoft Azure account for improving customer experience. Azure Support connects the Azure community to answers, support, and experts.
 
-- [Open an Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md).
+- [Open an Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md).
diff --git a/articles/azure-vmware/remove-arc-enabled-azure-vmware-solution-vsphere-resources-from-azure.md b/articles/azure-vmware/remove-arc-enabled-azure-vmware-solution-vsphere-resources-from-azure.md
@@ -9,6 +9,9 @@ ms.custom: references_regions, engagement-fy23
 
 # Remove Arc-enabled Azure VMware Solution vSphere resources from Azure
 
+> [!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, learn how to cleanly remove your VMware vCenter environment from Azure Arc-enabled VMware vSphere. For VMware vSphere environments that you no longer want to manage with Azure Arc-enabled VMware vSphere, use the information in this article to perform the following actions: 
 
 - Remove guest management from VMware virtual machines (VMs). 
diff --git a/articles/migrate/common-questions-server-migration.md b/articles/migrate/common-questions-server-migration.md
@@ -12,6 +12,9 @@ ms.custom: engagement-fy23
 
 # Migration and modernization: Common questions
 
+> [!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 answers common questions about the Migration and modernization tool. If you've other questions, check these resources:
 
 - [General questions](resources-faq.md) about Azure Migrate
diff --git a/articles/sentinel/troubleshooting-cef-syslog.md b/articles/sentinel/troubleshooting-cef-syslog.md
@@ -9,6 +9,9 @@ ms.author: lwainstein
 
 # Troubleshoot your CEF or Syslog data connector
 
+> [!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 common methods for verifying and troubleshooting a CEF or Syslog data connector for Microsoft Sentinel.
 
 For example, if your logs are not appearing in Microsoft Sentinel, either in the Syslog or the Common Security Log tables, your data source may be failing to connect or there may be another reason your data is not being ingested.
