Azure Deploy Targets refresh

src/pages/docs/deployments/azure/cloud-services/getting-started-with-azure-cloud-services.md

@@ -1,9 +1,9 @@
 ---
 layout: src/layouts/Redirect.astro
 title: Redirect
-redirect: https://octopus.com/docs/deployments/azure/cloud-services
+redirect: https://octopus.com/docs/infrastructure/deployment-targets/azure
 pubDate:  2023-01-01
 navSearch: false
 navSitemap: false
 navMenu: false
----
+---

src/pages/docs/deployments/azure/cloud-services/index.md

@@ -0,0 +1,10 @@
+---
+layout: src/layouts/Redirect.astro
+title: Redirect
+redirect: https://octopus.com/docs/infrastructure/deployment-targets/azure
+pubDate:  2023-01-01
+navSearch: false
+navSitemap: false
+navMenu: false
+hideInThisSectionHeader: true
+---

src/pages/docs/deployments/azure/cloud-services/vip-swap.md

@@ -0,0 +1,9 @@
+---
+layout: src/layouts/Redirect.astro
+title: Redirect
+redirect: https://octopus.com/docs/infrastructure/deployment-targets/azure
+pubDate:  2023-01-01
+navSearch: false
+navSitemap: false
+navMenu: false
+---

src/pages/docs/deployments/azure/deploying-a-package-to-an-azure-cloud-service/index.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Redirect.astro
 title: Redirect
-redirect: https://octopus.com/docs/deployments/azure/cloud-services
+redirect: https://octopus.com/docs/infrastructure/deployment-targets/azure
 pubDate:  2023-01-01
 navSearch: false
 navSitemap: false

src/pages/docs/infrastructure/azure-cloud-service-target.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Redirect.astro
 title: Redirect
-redirect: https://octopus.com/docs/infrastructure/deployment-targets/azure/cloud-service-targets
+redirect: https://octopus.com/docs/infrastructure/deployment-targets/azure
 pubDate:  2023-01-01
 navSearch: false
 navSitemap: false

src/pages/docs/infrastructure/azure/cloud-service-targets/index.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Redirect.astro
 title: Redirect
-redirect: https://octopus.com/docs/infrastructure/deployment-targets/azure/cloud-service-targets
+redirect: https://octopus.com/docs/infrastructure/deployment-targets/azure
 pubDate:  2023-01-01
 navSearch: false
 navSitemap: false

src/pages/docs/infrastructure/deployment-targets/azure/cloud-service-targets/index.md

@@ -1,55 +1,9 @@
 ---
-layout: src/layouts/Default.astro
-pubDate: 2023-01-01
-modDate: 2024-06-27
-title: Azure Cloud Service targets
-description: Azure Cloud Service deployment targets allow you to reference existing classic Cloud Services in your Azure subscription, that you can then reference by target tag during deployments.
-navOrder: 100
----
-
-Azure Cloud Service deployment targets allow you to reference existing classic Cloud Services in your Azure subscription, that you can then reference by [target tag](/docs/infrastructure/deployment-targets/target-tags) during deployments.
-
-:::div{.warning}
-Microsoft [announced](https://blogs.msdn.microsoft.com/appserviceteam/2018/03/12/deprecating-service-management-apis-support-for-azure-app-services/) that from June 30th 2018 they are retiring support for Azure Service Management API (which indicates Cloud Services). Microsoft stated that _"Cloud Services is similar to Service Fabric in degree of control versus ease of use, but it's now a legacy service and Service Fabric is recommended for new development"_ ([source](https://docs.microsoft.com/en-us/azure/app-service/choose-web-site-cloud-service-vm)).
-
-Support for this feature will be deprecated in Octopus Server from the `2024.1` release.
-:::
-
-## Requirements
-
-You can read more about all the PaaS targets [in our blog](https://octopus.com/blog/paas-targets).
-
-- You will need an [Azure Management Certificate account](/docs/infrastructure/accounts/azure/#azure-management-certificate) that references your Azure subscription.
-
-- Once your Azure account is setup, you will then need an existing Azure Cloud Service (classic) setup within your Azure subscription. To learn more about App Services, the Azure team provide [useful documentation on App Services](https://docs.microsoft.com/en-us/azure/cloud-services/) that can help you get started. If you are dynamically creating the cloud services during your deployment, check our section about [creating Cloud Service targets by scripts using service messages](#creating-cloud-service-targets-by-scripts).
-
-## Creating Cloud Service targets
-
-Once you have a Cloud Service setup within your Azure subscription, you are then ready to map that to an Octopus deployment target.
-
-To create an Azure Cloud Service target within Octopus:
-
-- Go to **Infrastructure ➜ Deployment Targets ➜ Add Deployment Target**.
-- Select **Azure Cloud Service** from the list of available targets and click _Next_.
-- Fill out the necessary fields, being sure to provide a unique target tag that clearly identifies your Azure Cloud Service target.
-
-:::figure
-![](/docs/infrastructure/deployment-targets/azure/cloud-service-targets/create-azure-cloud-service-target.png)
-:::
-
-- After clicking _Save_, your deployment target will be added and go through a health check to ensure Octopus can connect to it.
-- If all goes well, you should see your newly created target in your **Deployment Targets** list, with a status of _Healthy_.
-
-### Creating Cloud Service targets by scripts
-
-Azure Cloud Service targets can also be created via a PowerShell cmdlet within a Deployment Process, this can be especially handy if you are also creating the Azure Cloud Service via a script.
-
-See [Creating Resources by script](/docs/infrastructure/deployment-targets/dynamic-infrastructure) for more information on creating Azure Cloud Services via a script.
-
-## Deploying to Cloud Service targets
-
-See our [documentation about this topic](/docs/deployments/azure/cloud-services)
-
-## Troubleshooting
-
-If your Azure Cloud Service target is not completing a health check successfully, you may need to check that your Octopus Server can communicate with Azure. It may be worth checking that your Azure Account is able to complete a _Save and Test_ to ensure Octopus can communicate with Azure and the management certificate referenced by the account is valid. If your Octopus Server is behind a proxy or firewall, you will need to consult with your Systems Administrator to ensure it is able to communicate with Azure.
+layout: src/layouts/Redirect.astro
+title: Redirect
+redirect: https://octopus.com/docs/infrastructure/deployment-targets/azure
+pubDate:  2023-01-01
+navSearch: false
+navSitemap: false
+navMenu: false
+---

src/pages/docs/infrastructure/deployment-targets/azure/index.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2024-06-27
+modDate: 2024-12-12
 title: Azure targets
 description: Configure your Azure infrastructure
 navOrder: 40
@@ -16,8 +16,9 @@ The currently supported Azure targets are:
 
 - [Azure Service Fabric Clusters](/docs/infrastructure/deployment-targets/azure/service-fabric-cluster-targets).
 - [Azure Web Apps](/docs/infrastructure/deployment-targets/azure/web-app-targets) (also works for Azure Functions).
-- [Azure Cloud Services](/docs/infrastructure/deployment-targets/azure/cloud-service-targets).
+- Azure Kubernetes Service via the [Kubernetes Agent](/docs/kubernetes/targets/kubernetes-agent) and [Kubernetes API](/docs/kubernetes/targets/kubernetes-api) deployment targets.
+- Azure VM via [Tentacle using Desired State Configuration (DSC)](/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-an-arm-template-with-dsc).
 
 :::div{.warning}
-Regarding Azure Cloud Services, Microsoft [announced](https://blogs.msdn.microsoft.com/appserviceteam/2018/03/12/deprecating-service-management-apis-support-for-azure-app-services/) that from June 30th 2018 they are retiring support for Azure Service Management API (which indicates Cloud Services). Microsoft stated that _"Cloud Services is similar to Service Fabric in degree of control versus ease of use, but it's now a legacy service and Service Fabric is recommended for new development"_ ([source](https://docs.microsoft.com/en-us/azure/app-service/choose-web-site-cloud-service-vm)).
+Octopus Deploy versions prior to `2024.1` deploying to Azure Cloud Services was supported([See deprecation notice for more details](/docs/deprecations#azure-cloud-services-classic)) but as of September 1st 2024 Azure Cloud Services(Classic) Microsoft has deprecated these services and as of October 1st 2024 Microsoft is shutting down any existing running Cloud Service deployments. ([Source](https://learn.microsoft.com/en-us/azure/cloud-services/cloud-services-choose-me))
 :::

src/pages/docs/infrastructure/deployment-targets/azure/web-app-targets/index.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2024-06-27
+modDate: 2024-12-12
 title: Azure Web App targets
 description: Azure Web App deployment targets allow you to reference existing Web Apps in your Azure subscription, that you can then reference by target tag during deployments.
 navOrder: 20
@@ -17,7 +17,7 @@ From version 2022.1 Octopus can discover Azure Web App targets using tags on you
 
 - You need an [Azure Service Principal account](/docs/infrastructure/accounts/azure/#azure-service-principal) that references your Azure subscription.
 
-- Once your Azure account is setup, you need an existing Azure Web App / App Service setup within your Azure subscription. To learn more about App Services, see the [Azure App Services documentation](https://docs.microsoft.com/en-us/azure/app-service/) that can help you get started. If you are dynamically creating the web app during your deployment, check our section about [creating Web App targets by scripts using service messages](#creating-web-app-targets-by-scripts).
+- Once your Azure account is setup, you need an existing Azure Web App / App Service setup within your Azure subscription. To learn more about App Services, see the [Azure App Services documentation](https://docs.microsoft.com/en-us/azure/app-service/) that can help you get started. If you are dynamically creating the web app during your deployment, check our section about [discovering web app targets](#discovering-web-app-targets) or [creating Web App targets by scripts using service messages](#creating-web-app-targets-by-scripts).
 
 ## Discovering web app targets
 
@@ -47,8 +47,8 @@ Once you have an App Service configured within your Azure subscription, you are
 
 To create an Azure Web App target within Octopus:
 
-- Navigate to **Infrastructure ➜ Deployment Target ➜ Add Deployment Target**.
-- Select **Azure Web App** from the list of available targets and click _Next_.
+- Navigate to **Deploy ➜ Infrastructure ➜ Deployment Targets ➜ Add Deployment Target**.
+- Select **Azure tab** and then select **Azure Web App** from the list of available targets and click _Next_.
 - Fill out the necessary fields, being sure to provide a unique target tag (formerly target role) that clearly identifies your Azure Web App target.
 
 :::figure

src/pages/docs/infrastructure/deployment-targets/dynamic-infrastructure/azure-cloud-service-target.md

@@ -0,0 +1,9 @@
+---
+layout: src/layouts/Redirect.astro
+title: Redirect
+redirect: https://octopus.com/docs/infrastructure/deployment-targets/azure
+pubDate:  2023-01-01
+navSearch: false
+navSitemap: false
+navMenu: false
+---