Merge branch 'MicrosoftDocs:main' into 17.12

Author: tinaschrepfer

.openpublishing.redirection.json

@@ -1,5 +1,75 @@
 {
   "redirections": [
+    {
+      "source_path": "docs/azure/vs-azure-tools-migrate-publish-web-app-to-cloud-service.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-migrate-publish-web-app-to-cloud-service",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-access-private-azure-clouds-with-visual-studio.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-access-private-azure-clouds-with-visual-studio",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-cloud-service-publish-set-up-required-services-in-visual-studio.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-cloud-service-publish-set-up-required-services-in-visual-studio",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-cloud-service-retain-a-constant-virtual-ip-address.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-cloud-service-retain-a-constant-virtual-ip-address",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-debugging-cloud-services-overview.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-debugging-cloud-services-overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-intellitrace-debug-published-cloud-services.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-intellitrace-debug-published-cloud-services",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-performance-profiling-cloud-services.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-performance-profiling-cloud-services",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-publish-azure-application-wizard.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-publish-azure-application-wizard",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-publish-webapplicationvm.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-publish-webapplicationvm",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-publish-webapplicationwebsite-windows-powershell-script.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-publish-webapplicationwebsite-windows-powershell-script",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools--publishing-using-powershell-scripts.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools--publishing-using-powershell-scripts",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-resources-managing-with-cloud-explorer.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-resources-managing-with-cloud-explorer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-setting-up-named-authentication-credentials.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-setting-up-named-authentication-credentials",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/azure/vs-azure-tools-upgrade-projects-to-the-current-version-of-the-azure-tools.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-upgrade-projects-to-the-current-version-of-the-azure-tools",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/extensibility/internals/microsoft-help-viewer-sdk.md",
       "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/extensibility/internals/microsoft-help-viewer-sdk",

bridge/articles/bridge-to-kubernetes-aks.md

@@ -11,6 +11,8 @@ description: Use Bridge to Kubernetes to run and debug locally in a single pod w
 
 # Use Bridge to Kubernetes with AKS
 
+[!INCLUDE [Bridge to Kubernetes deprecation note](./includes/deprecation.md)]
+
 In this tutorial, you use a specific AKS sample microservices web app to learn how to use Bridge to Kubernetes to debug locally in a single pod that's part of an Azure Kubernetes Service (AKS) cluster.
 
 ## Before you begin

bridge/articles/bridge-to-kubernetes-sample.md

@@ -10,6 +10,8 @@ description: Try a sample application that uses Bridge to Kubernetes to develop,
 ---
 # Use Bridge to Kubernetes with a sample
 
+[!INCLUDE [Bridge to Kubernetes deprecation note](./includes/deprecation.md)]
+
 This sample illustrates how Bridge to Kubernetes can be used to develop a microservice version of a simple TODO application on any Kubernetes cluster. This sample, using Visual Studio Code, has been adapted from code provided by [TodoMVC](https://todomvc.com). In this example, we use MiniKube to host the application, but these steps should work with any Kubernetes cluster.
 
 The TODO application sample is composed of a frontend and a backend that provides persistent storage. This extended sample adds a statistics component and breaks the application into a number of microservices, specifically:

bridge/articles/bridge-to-kubernetes-vs-code.md

@@ -11,6 +11,8 @@ description: Use Bridge to Kubernetes to redirect traffic between your Kubernete
 
 # Use Bridge to Kubernetes (VS Code)
 
+[!INCLUDE [Bridge to Kubernetes deprecation note](./includes/deprecation.md)]
+
 Bridge to Kubernetes allows you to run and debug code on your development computer, while still connected to your Kubernetes cluster with the rest of your application or services. In this guide, you will learn how to use Bridge to Kubernetes to redirect traffic between your Kubernetes cluster and code running on your development computer.
 
 ## Before you begin

bridge/articles/bridge-to-kubernetes-vs.md

@@ -12,6 +12,8 @@ ms.date: 06/20/2024
 
 # Tutorial: Run and debug locally with Bridge to Kubernetes on Visual Studio
 
+[!INCLUDE [Bridge to Kubernetes deprecation note](./includes/deprecation.md)]
+
 In this tutorial, you'll learn how to redirect traffic between your Kubernetes cluster and your development computer.
 This tutorial uses Bridge to Kubernetes and Visual Studio for debugging a service.
 To use Visual Studio Code, see [Run and debug locally with Bridge to Kubernetes with VS Code](bridge-to-kubernetes-vs-code.md).

bridge/articles/configure-bridge-to-kubernetes.md

@@ -12,6 +12,8 @@ ms.subservice: bridge
 
 # Configure Bridge to Kubernetes
 
+[!INCLUDE [Bridge to Kubernetes deprecation note](./includes/deprecation.md)]
+
 You can configure the local Bridge to Kubernetes process using two methods. You can annotate services on your cluster and you can supply local configuration.
 
 ## Kubernetes configuration

bridge/articles/includes/deprecation.md

@@ -0,0 +1,9 @@
+---
+author: ghogen
+ms.topic: include
+ms.date: 10/23/2024
+ms.author: ghogen
+---
+
+> [!NOTE]
+> Microsoft plans to no longer actively maintain the Bridge to Kubernetes project. Over the next few months, we will transition the project to an archival state. In the meantime, the project is still available to use and [download](https://github.com/Azure/Bridge-To-Kubernetes?tab=readme-ov-file#documentation). During this period, we hope to explore and recommend community projects that provide similar benefits to Bridge to Kubernetes for your future use. If you have questions, please contact us on our [issues board at GitHub](https://github.com/Azure/Bridge-To-Kubernetes/issues).

bridge/articles/kubernetes-environment-variables.md

@@ -10,6 +10,8 @@ ms.subservice: bridge
 ---
 # Kubernetes service environment variables
 
+[!INCLUDE [Bridge to Kubernetes deprecation note](./includes/deprecation.md)]
+
 When you communicate with another service in the same Kubernetes cluster, for example with an HTTP request, you typically use the hardcoded service name in the URL for the request, but that won't work in some scenarios with Bridge to Kubernetes. This article describes how to use the Kubernetes service environment variables to specify the connection URL.
 
 ## Avoid redirection failures

bridge/articles/managed-identity.md

@@ -10,6 +10,8 @@ ms.author: ghogen
 ---
 # Use managed identity with Bridge to Kubernetes
 
+[!INCLUDE [Bridge to Kubernetes deprecation note](./includes/deprecation.md)]
+
 If your AKS cluster uses [managed identity](/azure/active-directory/managed-identities-azure-resources/overview) security features to secure access to secrets and resources, Bridge to Kubernetes needs some special configuration to ensure it can work with these features. A Microsoft Entra token needs to be downloaded to the local machine to ensure that local execution and debugging is properly secured, and this requires some special configuration in Bridge to Kubernetes. This article shows how to configure Bridge to Kubernetes to work with services that use managed identity.
 
 ## How to configure your service to use managed identity

bridge/articles/overview-bridge-to-kubernetes.md

@@ -11,6 +11,8 @@ ms.author: ghogen
 ---
 # How Bridge to Kubernetes works
 
+[!INCLUDE [Bridge to Kubernetes deprecation note](./includes/deprecation.md)]
+
 *Bridge to Kubernetes* is an iterative development tool for authoring microservice applications that target Kubernetes. The Bridge to Kubernetes extension is available for Visual Studio and Visual Studio Code (VS Code).
 
 Bridge to Kubernetes allows you to run and debug code on your development computer. That computer is still connected to your Kubernetes cluster with the rest of your application or services. If you have a large microservices architecture with many interdependent services and databases, replicating those dependencies on your development computer can be difficult. Building and deploying code to your Kubernetes cluster for each code change can be slow, time-consuming, and difficult.

bridge/articles/parallel-services.md

@@ -10,6 +10,8 @@ ms.topic: how-to
 ---
 # Debug multiple services (VS Code)
 
+[!INCLUDE [Bridge to Kubernetes deprecation note](./includes/deprecation.md)]
+
 Bridge to Kubernetes provides the ability to debug your Kubernetes services in a local environment, as described in [Use Bridge to Kubernetes (VS Code)](bridge-to-kubernetes-vs-code.md). With Bridge to Kubernetes, you redirect traffic to a locally running instance of a service and can debug using VS Code's debugger. However, in some scenarios, you want to work with more than one service and debug into them all at the same time. You can debug multiple services in parallel by following these steps.
 
 ## To debug multiple services at the same time

docs/azure/cloud-services-extended-support.md

@@ -22,8 +22,6 @@ This article shows you how to publish an existing instance of Azure Cloud Servic
 
 ## Publish to Cloud Services (extended support)
 
-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).
-
 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.
 
 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
 
 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.
 
-   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.
+   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.
 
    ![Screenshot that shows the Create a Cloud Services (extended support) deployment pane.](./media/cloud-services-extended-support/extended-support-dialog.png)
 
@@ -75,12 +73,6 @@ Also be sure to check the storage account that Azure Diagnostics uses. To check
 
    ![Screenshot that shows remote desktop settings.](./media/cloud-services-extended-support/remote-desktop-configuration.png)
 
-1. Select **Next** to move to the **Diagnostics Settings** pane.
-
-   ![Screenshot that shows the Diagnostics Settings pane.](./media/cloud-services-extended-support/diagnostics-settings.png)
-
-   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).
-
 1. Select **Next** to move to the **Summary** pane.
 
    ![Screenshot that shows the Microsoft Azure Publish Summary pane.](./media/cloud-services-extended-support/publish-summary.png)

docs/azure/includes/cloud-services-legacy.md

@@ -5,7 +5,7 @@ author: ghogen
 ms.subservice: azure-development
 ms.author: ghogen
 ms.topic: include
-ms.date: 9/5/2024
+ms.date: 10/4/2024
 ---
 > [!NOTE]
-> 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/).
+> 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/).