Merge pull request #266007 from ChaseCrum/CEOL-11

insert EOL message

Author: v-ccolin

articles/backup/backup-azure-policy-supported-skus.md

@@ -10,6 +10,9 @@ ms.author: v-abhmallick
 
 # Supported VM SKUs for Azure Policy
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 Azure Backup provides a built-in policy (using Azure Policy) that can be assigned to **all Azure VMs in a specified location within a subscription or resource group**. When this policy is assigned to a given scope, all new VMs created in that scope are automatically configured for backup to an **existing vault in the same location and subscription**. The table below lists all the VM SKUs supported by this policy.
 
 ## Supported VMs*

articles/backup/backup-azure-restore-files-from-vm.md

@@ -10,6 +10,9 @@ ms.author: v-abhmallick
 ---
 # Recover files from Azure virtual machine backup
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 Azure Backup provides the capability to restore [Azure virtual machines (VMs) and disks](./backup-azure-arm-restore-vms.md) from Azure VM backups, also known as recovery points. This article explains how to recover files and folders from an Azure VM backup. Restoring files and folders is available only for Azure VMs deployed using the Resource Manager model and protected to a Recovery Services vault.
 
 

articles/defender-for-cloud/apply-security-baseline.md

@@ -9,6 +9,9 @@ ms.date: 06/27/2023
 
 # Review hardening recommendations
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 > [!NOTE]
 > As the Log Analytics agent (also known as MMA) is set to retire in [August 2024](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/), all Defender for Servers features that currently depend on it, including those described on this page, will be available through either [Microsoft Defender for Endpoint integration](integration-defender-for-endpoint.md) or [agentless scanning](concept-agentless-data-collection.md), before the retirement date. For more information about the roadmap for each of the features that are currently rely on Log Analytics Agent, see [this announcement](upcoming-changes.md#defender-for-cloud-plan-and-strategy-for-the-log-analytics-agent-deprecation).
 

articles/defender-for-cloud/common-questions-microsoft-defender-vulnerability-management.md

@@ -7,6 +7,9 @@ ms.date: 11/30/2023
 
 # Common questions about the Microsoft Defender Vulnerability Management solution
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 Get answers to common questions on the new Container VA offering powered by Microsoft Defender Vulnerability Management solution.
 
 ## How do I transition to the container vulnerability assessment powered by Microsoft Defender Vulnerability Management?
@@ -62,7 +65,7 @@ There's no difference for coverage of language specific packages between the Qua
 - Vulnerability reports for OS packages are enriched with evidence on commands that can be used to find the vulnerable package.
 
 ## Next steps
-  
+
 - Learn about [Defender for Containers](defender-for-containers-introduction.md)
 - Learn more about [Vulnerability assessments for Azure with Microsoft Defender Vulnerability Management](agentless-vulnerability-assessment-azure.md)
 - Learn more about [Vulnerability assessments for AWS with Microsoft Defender Vulnerability Management](agentless-vulnerability-assessment-aws.md)

articles/defender-for-cloud/defender-for-containers-vulnerability-assessment-azure.md

@@ -10,6 +10,9 @@ ms.custom: build-2023
 
 # Vulnerability assessment for Azure powered by Qualys (Deprecated)
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 > [!IMPORTANT]
 >
 > The Defender for Cloud Containers Vulnerability Assessment powered by Qualys is now on a retirement path completing on **March 1st, 2024**. If you are currently using container vulnerability assessment powered by Qualys, start planning your transition to [Vulnerability assessments for Azure with Microsoft Defender Vulnerability Management](agentless-vulnerability-assessment-azure.md).

articles/defender-for-cloud/defender-for-containers-vulnerability-assessment-elastic.md

@@ -9,6 +9,9 @@ ms.topic: how-to
 
 # Use Defender for Containers to scan your AWS ECR images for vulnerabilities powered by Trivy (Deprecated)
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 Defender for Containers lets you scan the container images stored in your Amazon AWS Elastic Container Registry (ECR) as part of the protections provided within Microsoft Defender for Cloud.
 
 To enable scanning of vulnerabilities in containers, you have to [connect your AWS account to Defender for Cloud](quickstart-onboard-aws.md) and [enable Defender for Containers](defender-for-containers-enable.md). The agentless scanner, powered by the open-source scanner Trivy, scans your ECR repositories and reports vulnerabilities.
@@ -115,7 +118,7 @@ Vulnerability findings for an image are still shown in the recommendation for 48
 
     1. When you're sure the updated image has been pushed, scanned, and is no longer appearing in the recommendation, delete the “old” vulnerable image from your registry.
 
-<!-- 
+<!--
 ## Disable specific findings
 
 > [!NOTE]

articles/virtual-machine-scale-sets/flexible-virtual-machine-scale-sets-portal.md

@@ -12,6 +12,9 @@ ms.custom: mimckitt, vmss-flex, linux-related-content
 
 # Create virtual machines in a scale set using Azure portal
 
+> [!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 steps through using Azure portal to create a Virtual Machine Scale Set.
 ## Log in to Azure
 Sign in to the [Azure portal](https://portal.azure.com).

articles/virtual-machine-scale-sets/quick-create-portal.md

@@ -12,6 +12,9 @@ ms.custom: mimckitt, mode-ui, linux-related-content
 
 # Quickstart: Create a Virtual Machine Scale Set in the Azure portal
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
 **Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Uniform scale sets
 
 > [!NOTE]

articles/virtual-machine-scale-sets/spot-priority-mix.md

@@ -13,7 +13,10 @@ ms.custom: engagement-fy23
 
 # Spot Priority Mix for high availability and cost savings
 
-**Applies to:** :heavy_check_mark: Flexible scale sets 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
+
+**Applies to:** :heavy_check_mark: Flexible scale sets
 
 Azure allows you to have the flexibility of running a mix of uninterruptible standard VMs and interruptible Spot VMs for Virtual Machine Scale Set deployments. You're able to deploy this Spot Priority Mix using Flexible orchestration to easily balance between high-capacity availability and lower infrastructure costs according to your workload requirements. This feature allows you to easily manage your scale set capability to achieve the following goals:
 
@@ -49,21 +52,21 @@ You can set your Spot Priority Mix by using an ARM template to add the following
 
 You can refer to this [ARM template example](https://paste.microsoft.com/f84d2f83-f6bf-4d24-aa03-175b0c43da32) for more context.
 
-### [Portal](#tab/portal) 
+### [Portal](#tab/portal)
 
-You can set your Spot Priority Mix in the Spot tab of the Virtual Machine Scale Sets creation process in the Azure portal. The following steps instruct you on how to access this feature during that process. 
+You can set your Spot Priority Mix in the Spot tab of the Virtual Machine Scale Sets creation process in the Azure portal. The following steps instruct you on how to access this feature during that process.
 
 1. Log in to the [Azure portal](https://portal.azure.com).
 1. In the search bar, search for and select **Virtual Machine Scale Sets**.
 1. Select **Create** on the **Virtual Machine Scale Sets** page.
 1. In the **Basics** tab, fill out the required fields, select **Flexible** as the **Orchestration** mode, and select the checkbox for **Run with Azure Spot discount**.
 1. In the **Spot** tab, select the check-box next to *Scale with VMs and Spot VMs* option under the **Scale with VMs and discounted Spot VMs** section.
 1. Fill out the **Base VM (uninterruptible) count** and **Instance distribution** fields to configure your percentage split between Spot and Standard VMs.
-1. Continue through the Virtual Machine Scale Set creation process. 
+1. Continue through the Virtual Machine Scale Set creation process.
 
 ### [Azure CLI](#tab/cli)
 
-You can set your Spot Priority Mix using Azure CLI by setting the `priority` flag to `Spot` and including the `regular-priority-count` and `regular-priority-percentage` flags.  
+You can set your Spot Priority Mix using Azure CLI by setting the `priority` flag to `Spot` and including the `regular-priority-count` and `regular-priority-percentage` flags.
 
 ```azurecli
 az vmss create -n myScaleSet \
@@ -81,7 +84,7 @@ az vmss create -n myScaleSet \
 
 ### [Azure PowerShell](#tab/powershell)
 
-You can set your Spot Priority Mix using Azure PowerShell by setting the `Priority` parameter to `Spot` and including the `BaseRegularPriorityCount` and `RegularPriorityPercentage` parameters.  
+You can set your Spot Priority Mix using Azure PowerShell by setting the `Priority` parameter to `Spot` and including the `BaseRegularPriorityCount` and `RegularPriorityPercentage` parameters.
 
 ```azurepowershell
 $vmssConfig = New-AzVmssConfig `
@@ -114,13 +117,13 @@ You can update your existing Spot Priority Mix in the Configuration tab of the V
 
 1. Navigate to the specific virtual machine scale set that you're adjusting the Spot Priority Mix on.
 1. In the left side bar, scroll down to and select **Configuration**.
-1. Your current Spot Priority Mix should be visible. Here you can change the **Base VM (uninterruptible) count** and **Instance distribution** of Spot and Standard VMs. 
+1. Your current Spot Priority Mix should be visible. Here you can change the **Base VM (uninterruptible) count** and **Instance distribution** of Spot and Standard VMs.
 1. Update your Spot Mix as needed.
-1. Press the **Save** button to apply your changes. 
+1. Press the **Save** button to apply your changes.
 
 ### [Azure CLI](#tab/cli)
 
-You can update your Spot Priority Mix using Azure CLI by updating the `regular-priority-count` and `regular-priority-percentage` parameters.  
+You can update your Spot Priority Mix using Azure CLI by updating the `regular-priority-count` and `regular-priority-percentage` parameters.
 
 ```azurecli
 az vmss update --resource-group myResourceGroup \
@@ -131,7 +134,7 @@ az vmss update --resource-group myResourceGroup \
 
 ### [Azure PowerShell](#tab/powershell)
 
-You can update your Spot Priority Mix using Azure PowerShell by updating the `BaseRegularPriorityCount` and `RegularPriorityPercentage` parameters.  
+You can update your Spot Priority Mix using Azure PowerShell by updating the `BaseRegularPriorityCount` and `RegularPriorityPercentage` parameters.
 
 ```azurepowershell
 $vmss = Get-AzVmss `
@@ -151,7 +154,7 @@ Update-AzVmss `
 
 ## Examples
 
-The following examples have scenario assumptions, a table of actions, and walk-through of results to help you understand how Spot Priority Mix configuration works. 
+The following examples have scenario assumptions, a table of actions, and walk-through of results to help you understand how Spot Priority Mix configuration works.
 
 Some important terminology to notice before referring to these examples:
 
@@ -188,7 +191,7 @@ Example walk-through:
     - Note, because there's a 50/50 split, in the fourth scale-out, there's one more Spot VM than standard VM. Once it's scaled out again (5th scale-out), the 50/50 balance is restored with another standard VM.
 1. You then scale in your scale set with the eviction policy being *evict-delete*, which deletes all the Spot VMs.
 1. With the scale-out operations mentioned in this scenario, you restore the 50/50 balance in your scale set by only creating Spot VMs.
-1. By the last scale-out, your scale set is already balanced, so one of each type of VM is created. 
+1. By the last scale-out, your scale set is already balanced, so one of each type of VM is created.
 
 ### Scenario 2
 
@@ -210,13 +213,13 @@ The following scenario assumptions apply to this example:
 
 Example walk-through:
 1. With the initial creation of the Virtual Machine Scale Set and Spot Priority Mix, you have 20 VMs.
-    - 10 of those VMs are the Base (standard) VMs, 2 extra standard VMs, and 8 Spot priority VMs for your 25% *regularPriorityPercentageAboveBase*. 
-    - Another way to look at this ratio is you have 1 standard VM for every 4 Spot VMs in the scale set. 
+    - 10 of those VMs are the Base (standard) VMs, 2 extra standard VMs, and 8 Spot priority VMs for your 25% *regularPriorityPercentageAboveBase*.
+    - Another way to look at this ratio is you have 1 standard VM for every 4 Spot VMs in the scale set.
 2. You then scale out twice to create 90 more VMs; 23 standard VMs and 67 Spot VMs.
 3. When you scale in by 10 VMs, 10 Spot VMs are *stop-deallocated*, creating an imbalance in your scale set.
 4. Your next scale out operation creates another 2 standard VMs and 8 Spot VMs, bringing you closer to your 25% above base ratio.
 
-## Troubleshooting 
+## Troubleshooting
 
 If Spot Priority Mix isn't available to you, be sure to configure the `priorityMixPolicy` to specify a *Spot* priority in the `virtualMachineProfile`. Without enabling the `priorityMixPolicy` setting, you won't be able to access this Spot feature.
 
@@ -229,7 +232,7 @@ Spot Priority Mix applies for scale actions on the scale set. Changing the perce
 Spot Priority Mix is only available on Virtual Machine Scale Sets with Flexible orchestration mode.
 
 ### Q: Which regions is Spot Priority Mix enabled in?
-Spot VMs, and therefore Spot Priority Mix, are available in all global Azure regions. 
+Spot VMs, and therefore Spot Priority Mix, are available in all global Azure regions.
 
 ## Next steps
 

articles/virtual-machine-scale-sets/tutorial-autoscale-cli.md

@@ -11,6 +11,10 @@ ms.reviewer: mimckitt
 ms.custom: avverma, devx-track-azurecli, linux-related-content
 ---
 # Tutorial: Automatically scale a Virtual Machine Scale Set with the Azure CLI
+
+> [!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 create a scale set, you define the number of VM instances that you wish to run. As your application demand changes, you can automatically increase or decrease the number of VM instances. The ability to autoscale lets you keep up with customer demand or respond to application performance changes throughout the lifecycle of your app. In this tutorial you learn how to:
 
 > [!div class="checklist"]