Skip to content

Commit 0316fc5

Browse files
authored
Update swap-cloud-service.md
1 parent 5e269f5 commit 0316fc5

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/cloud-services-extended-support/swap-cloud-service.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.date: 11/21/2024
1313

1414
# Swap or switch deployments in Azure Cloud Services (extended support)
1515

16+
> [!IMPORTANT]
17+
> 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).
18+
1619
You can swap between two independent cloud service deployments in Azure Cloud Services (extended support). Unlike in Azure Cloud Services (classic), the Azure Resource Manager model in Azure Cloud Services (extended support) doesn't use deployment slots. In Azure Cloud Services (extended support), when you deploy a new release of a cloud service, you can make the cloud service "swappable" with an existing cloud service in Azure Cloud Services (extended support).
1720

1821
After you swap the deployments, you can stage and test your new release by using the new cloud service deployment. In effect, swapping promotes a new cloud service staged to production release.

0 commit comments

Comments
 (0)