Merge pull request #297791 from hirenshah1/patch-62

Update overview.md

Author: ttorble

articles/cloud-services-extended-support/available-sizes.md

@@ -12,6 +12,9 @@ ms.date: 07/24/2024
 
 # Available sizes for Azure Cloud Services (extended support)
 
+> [!IMPORTANT]
+> As of March 31, 2025, cloud Services (classic) is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025).
+
 This article describes the available virtual machine sizes for Cloud Services (extended support) instances.   
 
 | SKU Family |  ACU/ Core | 

articles/cloud-services-extended-support/certificates-and-key-vault.md

@@ -12,6 +12,9 @@ ms.date: 07/24/2024
 
 # Use certificates with Azure Cloud Services (extended support)
 
+> [!IMPORTANT]
+> As of March 31, 2025, cloud Services (classic) is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025).
+
 Key Vault is used to store certificates that are associated to Cloud Services (extended support). Key Vaults can be created through the [Azure portal](/azure/key-vault/general/quick-create-portal) and [PowerShell](/azure/key-vault/general/quick-create-powershell). Add the certificates to Key Vault, then reference the certificate thumbprints in Service Configuration file. You also need to enable Key Vault for appropriate permissions so that Cloud Services (extended support) resource can retrieve certificate stored as secrets from Key Vault.
 
 ## Upload a certificate to Key Vault 

articles/cloud-services-extended-support/cloud-services-guestos-family-1-retirement.md

@@ -14,6 +14,9 @@ ms.custom: compute-evergreen
 
 # Guest OS Family 1 retirement notice
 
+> [!IMPORTANT]
+> As of March 31, 2025, cloud Services (classic) is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025).
+
 The retirement of OS Family 1 was first announced on June 1, 2013.
 
 **Sept 2, 2014** The Azure Guest operating system (Guest OS) Family 1.x, which is based on the Windows Server 2008 operating system, was officially retired. All attempts to deploy new services or upgrade existing services using Family 1 fail with an error message informing you that the Guest OS Family 1 is retired.

articles/cloud-services-extended-support/cloud-services-guestos-family-2-3-4-retirement.md

@@ -14,6 +14,9 @@ ms.custom: compute-evergreen
 
 # Guest OS Family 2, 3, and 4 retirement notice
 
+> [!IMPORTANT]
+> As of March 31, 2025, cloud Services (classic) is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025).
+
 The retirement of Azure Guest OS Families 2, 3, and 4 was announced in July 2024, with the following end-of-life dates: 
 - **Windows Server 2008 R2:** December 2024 
 - **Windows Server 2012 and Windows Server 2012 R2:** February 2025 

articles/cloud-services-extended-support/cloud-services-guestos-microsoft-security-response-center-releases.md

@@ -13,6 +13,10 @@ ms.custom: compute-evergreen
 ---
 
 # Azure Guest OS
+
+> [!IMPORTANT]
+> As of March 31, 2025, cloud Services (classic) is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025).
+
 The following tables show the Microsoft Security Response Center (MSRC) updates applied to the Azure Guest OS. Search this article to determine if a particular update applies to your Guest OS. Updates always carry forward for the particular [family][family-explain] they were introduced in.
 
 ## March 2025 Guest OS

articles/cloud-services-extended-support/cloud-services-guestos-retirement-policy.md

@@ -13,6 +13,10 @@ ms.author: ssundara
 ms.custom: compute-evergreen
 ---
 # Azure Guest OS supportability and retirement policy
+
+> [!IMPORTANT]
+> As of March 31, 2025, cloud Services (classic) is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025).
+
 The information on this page relates to the Azure Guest operating system ([Guest OS](cloud-services-guestos-update-matrix.md)) for Cloud Services worker and web roles (PaaS). It doesn't apply to Virtual Machines (IaaS).
 
 Microsoft has a published [support policy for the Guest OS](https://support.microsoft.com/gp/azure-cloud-lifecycle-faq). This page describes how the policy is implemented.

articles/cloud-services-extended-support/cloud-services-guestos-update-matrix.md

@@ -12,6 +12,10 @@ ms.author: ssundara
 ms.custom: compute-evergreen
 ---
 # Azure Guest OS releases and SDK compatibility matrix
+
+> [!IMPORTANT]
+> As of March 31, 2025, cloud Services (classic) is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025).
+
 Provides you with up-to-date information about the latest Azure Guest OS releases for Cloud Services. This information helps you plan your upgrade path before a Guest OS is disabled. If you configure your roles to use *automatic* Guest OS updates as described in [Azure Guest OS Update Settings][Azure Guest OS Update Settings], it isn't vital that you read this page.
 
 > [!IMPORTANT]

articles/cloud-services-extended-support/cloud-services-model-and-package.md

@@ -12,6 +12,9 @@ ms.date: 07/24/2024
 
 # What is the Azure Cloud Service model and how do I package it?
 
+> [!IMPORTANT]
+> As of March 31, 2025, cloud Services (classic) is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025).
+
 A cloud service is created from three components, the service definition *(.csdef)*, the service config *(.cscfg)*, and a service package *(.cspkg)*. Both the **ServiceDefinition.csdef** and **ServiceConfig.cscfg** files are XML-based and describe the structure of the cloud service and its configuration. We collectively call these files the model. The **ServicePackage.cspkg** is a zip file that is generated from the **ServiceDefinition.csdef** and among other things, contains all the required binary-based dependencies. Azure creates a cloud service from both the **ServicePackage.cspkg** and the **ServiceConfig.cscfg**.
 
 Once the cloud service is running in Azure, you can reconfigure it through the **ServiceConfig.cscfg** file, but you can't alter the definition.

articles/cloud-services-extended-support/configure-scaling.md

@@ -13,6 +13,9 @@ ms.date: 07/24/2024
 
 # Configure scaling options with Azure Cloud Services (extended support) 
 
+> [!IMPORTANT]
+> As of March 31, 2025, cloud Services (classic) is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025).
+
 Conditions can be configured to enable Cloud Services (extended support) deployments to scale in and out. These conditions can be based on CPU usage, disk load, and network load. 
 
 Consider the following information when configuring scaling of your Cloud Service deployments:

articles/cloud-services-extended-support/deploy-portal.md

@@ -12,6 +12,9 @@ ms.date: 07/24/2024
 
 # Deploy Cloud Services (extended support) by using the Azure portal
 
+> [!IMPORTANT]
+> As of March 31, 2025, cloud Services (classic) is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025).
+
 This article shows you how to use the Azure portal to create an Azure Cloud Services (extended support) deployment.
 
 ## Prerequisites