You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/azure/cloud-services-extended-support.md
+1-9Lines changed: 1 addition & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,8 +22,6 @@ This article shows you how to publish an existing instance of Azure Cloud Servic
22
22
23
23
## Publish to Cloud Services (extended support)
24
24
25
-
When you publish your existing Azure Cloud Services (classic) project to Azure Cloud Services (extended support), you still retain the capability to publish to an instance of Cloud Services (classic).
26
-
27
25
In Visual Studio 2019 version 16.9 and later, Cloud Services (classic) projects have a special version of the **Publish** command: **Publish (extended support)**. This command appears on the shortcut menu in Solution Explorer in Visual Studio.
28
26
29
27
There are some differences when you publish to Cloud Services (extended support). For example, you don't select whether to publish to **Staging** or to **Production**, because these deployment slots aren't part of the extended support publishing model. Instead, with Cloud Services (extended support), you can set up multiple deployments, and you can swap deployments in the Azure portal. Although it's possible to use this setting in Visual Studio version 16.9, the swap feature isn't available until a later release of Cloud Services (extended support).
@@ -57,7 +55,7 @@ Also be sure to check the storage account that Azure Diagnostics uses. To check
57
55
58
56
1. On **Common Settings**, in the dropdown list, either select an existing instance of Cloud Services (extended support) or select **Create new**, and then create a new instance. The datacenter displays in parentheses for each instance of Cloud Services (extended support). We recommend that the datacenter location for Cloud Services (extended support) be the same as the datacenter location of your storage account.
59
57
60
-
If you choose to create a new service, the **Create Cloud Service (extended support)** dialog appears. Specify the name, location, and resource group to use for your Cloud Services (extended support) deployment.
58
+
If you choose to create a new service, the **Create Cloud Service (extended support)** dialog appears. Specify the service name, DNS name if different from the service name, location, and resource group to use for your Cloud Services (extended support) deployment.
61
59
62
60

63
61
@@ -75,12 +73,6 @@ Also be sure to check the storage account that Azure Diagnostics uses. To check
75
73
76
74

77
75
78
-
1. Select **Next** to move to the **Diagnostics Settings** pane.
79
-
80
-

81
-
82
-
You can use Azure Diagnostics to troubleshoot an instance of Cloud Services (extended support). For information about using Diagnostics, see [Set up diagnostics for Azure Cloud Services and virtual machines](./vs-azure-tools-diagnostics-for-cloud-services-and-virtual-machines.md). For information about Application Insights, see [What is Application Insights?](/azure/application-insights/app-insights-overview).
83
-
84
76
1. Select **Next** to move to the **Summary** pane.
85
77
86
78

Copy file name to clipboardExpand all lines: docs/azure/includes/cloud-services-legacy.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: ghogen
5
5
ms.subservice: azure-development
6
6
ms.author: ghogen
7
7
ms.topic: include
8
-
ms.date: 9/5/2024
8
+
ms.date: 10/4/2024
9
9
---
10
10
> [!NOTE]
11
-
> This article applies to Azure Cloud Services (classic), which is retired as of August 31, 2024. Existing services built with this technology are still supported through [Azure Cloud Services (extended support)](../cloud-services-extended-support.md). For new development, we recommend that you use a newer service type designed for your specific purpose, such as [Azure App Service](/azure/app-service/overview), [Azure Functions](/azure/azure-functions/functions-overview?pivots=programming-language-csharp), or [Azure Container Apps](/azure/container-apps/overview). For the latest list of available services, see [Directory of Azure products](https://azure.microsoft.com/products/).
11
+
> This article applies to Azure [Azure Cloud Services (extended support)](../cloud-services-extended-support.md). Cloud Services (classic) is retired as of August 31, 2024. For more information, see [Cloud services (classic) deployment model is retiring on August 31, 2024](https://azure.microsoft.com/updates/cloud-services-retirement-announcement). For new development, we recommend that you use a newer service type designed for your specific purpose, such as [Azure App Service](/azure/app-service/overview), [Azure Functions](/azure/azure-functions/functions-overview?pivots=programming-language-csharp), or [Azure Container Apps](/azure/container-apps/overview). For the latest list of available services, see [Directory of Azure products](https://azure.microsoft.com/products/).
0 commit comments