Merge pull request #298103 from MicrosoftDocs/main

Publish to live, Friday 4 AM PST, 4/11

Author: ttorble

articles/backup/backup-azure-database-postgresql-flex-support-matrix.md

@@ -2,7 +2,7 @@
 title: Azure Database for PostgreSQL- Flexible server support matrix
 description: Provides a summary of support settings and limitations of Azure Database for PostgreSQL- Flexible server backup.
 ms.topic: reference
-ms.date: 02/28/2025
+ms.date: 04/11/2025
 ms.custom: references_regions, ignite-2024
 ms.service: azure-backup
 author: jyothisuri
@@ -24,7 +24,7 @@ Consider the following support scenarios when you back up Azure Database for Pos
 - Vaulted backup restores are only available as **Restore to Files** in user specified storage containers. You can restore this data as a new PostgreSQL - flexible server with the database native tools.
 - Backups for the PostgreSQL server are supported when the Backup Vault is in the same or a different subscription as the database, provided they are within the same tenant and region. Restores are supported across regions (Azure Paired) and across subscriptions within the same tenant.
 - For vaulted backups, entire server is backed up with all databases. Backup of specific databases isn't supported.
-- Recommended limit for the maximum server size is **1 TB**. While backups can be attempted on server size exceeding 1 TB, which aren't officially supported, and the success of vaulted backups for such server can't be guaranteed.
+- Vaulted backups are supported for server size **<= 1 TB**. If backup is configured on server size larger than 1 TB, the backup operation fails.
 - PostgreSQL - Flexible servers encrypted by Customer Managed Key are supported.
 - Private endpoint-enabled Azure Database for PostgreSQL - Flexible servers can be backed up by allowing trusted Microsoft services in the network settings.
 - Backups for PostgreSQL Flexible servers exclude databases owned by `azuresu` or `azure_pg_admin`, including the native PostgreSQL database. So, databases with these owners can't be backed up or restored.
@@ -36,11 +36,12 @@ Azure Database for PostgreSQL – Flexible Server backups include the following
 - Vaulted backup doesn't support storage in archive tier.
 - Vaulted backup isn't supported on replicas; backup can be configured only on primary servers.
 - For restore operation, item level recovery (recovery of specific databases) isn't supported.
-- Weekly backups are supported for only one day in the week on which backup is initiated.
+- Only one weekly backup is currently supported. If multiple vaulted backups are scheduled in a week, only the first backup operation of the week is executed, and the subsequent backup jobs in the same week fail.”
 - Vaulted backups don't support tables containing a row with **BYTEA length exceeding 500 MB**.
+- Vaulted backups support full backups only; incremental or differential backups aren't supported.
 
 
 
 ## Next steps
 
-- [Back up Azure Database for PostgreSQL -Flexible Server using Azure portal](tutorial-create-first-backup-azure-database-postgresql-flex.md).
+- [Back up Azure Database for PostgreSQL -Flexible Server using Azure portal](tutorial-create-first-backup-azure-database-postgresql-flex.md).

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

@@ -13,7 +13,7 @@ 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).
+> As of March 31, 2025, cloud Services (extended support) 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.   
 

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

@@ -13,7 +13,7 @@ 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).
+> As of March 31, 2025, cloud Services (extended support) 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.
 

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

@@ -15,7 +15,7 @@ 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).
+> As of March 31, 2025, cloud Services (extended support) 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.
 

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

@@ -15,7 +15,7 @@ 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).
+> As of March 31, 2025, cloud Services (extended support) 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 

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

@@ -15,7 +15,7 @@ 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).
+> As of March 31, 2025, cloud Services (extended support) 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.
 

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

@@ -15,7 +15,7 @@ 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).
+> As of March 31, 2025, cloud Services (extended support) 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).
 

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

@@ -14,7 +14,7 @@ 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).
+> As of March 31, 2025, cloud Services (extended support) 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.
 

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

@@ -13,7 +13,7 @@ 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).
+> As of March 31, 2025, cloud Services (extended support) 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**.
 

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

@@ -14,7 +14,7 @@ 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).
+> As of March 31, 2025, cloud Services (extended support)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.