Merge pull request #2624 from OctopusDeploy/tk/broken-links

tonykelly-octopus · web-flow · commit 66a371e942de · 2025-02-11T14:51:19.000Z
Fixing broken links
diff --git a/dictionary-octopus.txt b/dictionary-octopus.txt
@@ -15,6 +15,7 @@ appsettings
 Appstep
 Appsteps
 argparse
+asax
 ASPNET
 aspnetcore
 astro
@@ -194,6 +195,7 @@ Kubelet
 kubelogin
 kustomization
 kustomize
+lanman
 lastmod
 latestdeployments
 lbvserver
@@ -370,6 +372,7 @@ runtimes
 SAMEORIGIN
 Schannel
 scopeduserroles
+secpol
 secureclientcertificate
 securestring
 SEIM
@@ -414,6 +417,7 @@ tabindex
 tabpanel
 tagset
 tagsets
+TCPIP
 templateid
 templating
 tenanttag
@@ -431,6 +435,7 @@ timespan
 tlsv1
 tmpfs
 Toolsets
+Topshelf
 toptags
 Traefik
 Trivy
@@ -483,4 +488,4 @@ xmark
 xvzf
 xxlarge
 youtu
-Zuora
+Zuora
diff --git a/src/pages/docs/administration/data/index.md b/src/pages/docs/administration/data/index.md
@@ -54,5 +54,5 @@ If you feel an index would benefit everyone using Octopus, please contact our [s
 
 :::div{.hint}
 **Azure SQL Database automatic index management**
-To ensure that you are aware of which indexes exist, we suggest turning off the Azure SQL feature to [automatically apply performance recommendations](https://azure.microsoft.com/en-us/documentation/articles/sql-database-advisor-portal/#enable-automatic-index-management) and apply the recommendations manually instead.
+To ensure that you are aware of which indexes exist, we suggest turning off the Azure SQL feature to [automatically apply performance recommendations](https://learn.microsoft.com/en-us/azure/azure-sql/database/database-advisor-implement-performance-recommendations?view=azuresql) and apply the recommendations manually instead.
 :::
diff --git a/src/pages/docs/deployments/aws/ecs/index.md b/src/pages/docs/deployments/aws/ecs/index.md
@@ -112,7 +112,7 @@ Specify the Security Groups and Subnets in the clusters VPC that will be attache
 Specify whether to enable Amazon ECS managed tags. Changing this value will force the service to be re-created.
 
 :::div{.hint}
-Octopus automatically adds stack-level tags that propagate to the task definition and the service. The full list of these auto-generated tags can be found in our [Architecture repository](https://github.com/OctopusDeploy/Architecture/blob/main/Steps/StepDesignGuidelines.md#tags-and-labels).
+Octopus automatically adds stack-level tags that propagate to the task definition and the service. The full list of these auto-generated tags can be found in our [Architecture repository](https://github.com/OctopusDeploy/Architecture/blob/main/Steps/StepDesignGuidelines.md).
 :::
 
 No more than 20 additional tags can be provided.
diff --git a/src/pages/docs/deployments/azure/deploying-a-package-to-an-azure-web-app/deploying-web-jobs.md b/src/pages/docs/deployments/azure/deploying-a-package-to-an-azure-web-app/deploying-web-jobs.md
@@ -6,13 +6,13 @@ title: Deploying Web Jobs
 description: Octopus Deploy can help you perform repeatable and controlled deployments of your applications into Azure Web Jobs.
 ---
 
-[Azure Web Jobs](https://azure.microsoft.com/en-us/documentation/articles/web-sites-create-web-jobs/) can either be packaged and deployed along with the Web App that they live under, or packaged and deployed independently.
+Azure Web Jobs can either be packaged and deployed along with the Web App that they live under, or packaged and deployed independently.
 
 ## Location {#DeployingWebJobs-Location}
 
 Web jobs are deployed to either `app_data/jobs/triggered/{job_name}` or `app_data/jobs/continuous/{job_name}`, depending on whether the job is *triggered* or *continuous*.
 
-## Packaged with the web app {#DeployingWebJobs-PackagedwiththeWebApp}
+## Packaged with the web app {#DeployingWebJobs-PackagedWithTheWebApp}
 
 If you are packaging and deploying your Web App and Web Job together, the Web Job must be packaged in it's location under the App\_Data directory.
 
diff --git a/src/pages/docs/deployments/azure/deploying-a-package-to-an-azure-web-app/index.md b/src/pages/docs/deployments/azure/deploying-a-package-to-an-azure-web-app/index.md
@@ -11,7 +11,7 @@ Octopus Deploy supports automated deployment of [Azure Web Apps](http://azure.mi
 
 ## Understanding Azure web apps {#understand-azure-web-apps}
 
-The Azure web apps you build, and how you might want to deploy them, are becoming increasingly complex as the Azure team provide more features to the platform. The best place to stay abreast of changes, and how they might affect your deployments is the [Azure Web App Documentation](https://azure.microsoft.com/en-us/documentation/services/app-service/web/), the [many and varied ways you can deploy Web Apps (including Octopus Deploy)](https://azure.microsoft.com/en-us/documentation/articles/web-sites-deploy/). There is also the hidden gem of the [Project Kudu GitHub repository](https://github.com/projectkudu/kudu/wiki) where you will find many of the hard to find facts about Web Jobs (like the `settings.job` file, configuring a Continuous Web Job as a Singleton, configuring the Schedule for Scheduled Jobs, how shadow copying enables in-place deployments, and how to shut down gracefully).
+The Azure web apps you build, and how you might want to deploy them, are becoming increasingly complex as the Azure team provide more features to the platform. The best place to stay abreast of changes, and how they might affect your deployments is the [Azure Web App Documentation](https://learn.microsoft.com/en-us/azure/app-service/), the [many and varied ways you can deploy Web Apps (including Octopus Deploy)](https://learn.microsoft.com/en-us/azure/static-web-apps/). There is also the hidden gem of the [Project Kudu GitHub repository](https://github.com/projectkudu/kudu/wiki) where you will find many of the hard to find facts about Web Jobs (like the `settings.job` file, configuring a Continuous Web Job as a Singleton, configuring the Schedule for Scheduled Jobs, how shadow copying enables in-place deployments, and how to shut down gracefully).
 
 ### Web apps are deployed using web deploy {#web-app-deployed-with-web-deploy}
 
diff --git a/src/pages/docs/deployments/azure/deploying-a-package-to-an-azure-web-app/using-deployment-slots-with-azure-web-apps.md b/src/pages/docs/deployments/azure/deploying-a-package-to-an-azure-web-app/using-deployment-slots-with-azure-web-apps.md
@@ -6,7 +6,7 @@ title: Using Deployment Slots with Azure Web Apps
 description: Deploying Slots provide a nice way to implement Blue-Green deployments for Azure Web Apps.
 ---
 
-[Deployment Slots](https://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/) provide a nice way to implement [Blue-Green deployments](http://martinfowler.com/bliki/BlueGreenDeployment.html) for Azure Web Apps.
+Deployment Slots provide a nice way to implement [Blue-Green deployments](http://martinfowler.com/bliki/BlueGreenDeployment.html) for Azure Web Apps.
 
 This provides many benefits, including:
 
@@ -18,7 +18,7 @@ This provides many benefits, including:
 Deployment Slots are only available to Azure Web Apps running in Standard or Premium [App Service plans](https://azure.microsoft.com/en-us/pricing/details/app-service/plans/)
 :::
 
-## Walk-Through {#UsingDeploymentSlotswithAzureWebApps-Walk-Through}
+## Walk-Through {#UsingDeploymentSlotsWithAzureWebApps-Walk-Through}
 
 Here we will give an example of how to setup a Blue-Green deployment for an Azure Web App using Deployment Slots.
 The scripts below assume you have a variable named 'WebSite' that contains the name of your Azure Web Site and 'ResourceGroup' that contains the Azure Resource Group Name.
@@ -27,7 +27,7 @@ The scripts below assume you have a variable named 'WebSite' that contains the n
 
 Follow the steps for [Azure Web App targets](/docs/infrastructure/deployment-targets/azure/web-app-targets).
 
-### Step 2: Create a staging slot {#UsingDeploymentSlotswithAzureWebApps-Step1-CreateStagingSlot}
+### Step 2: Create a staging slot {#UsingDeploymentSlotsWithAzureWebApps-Step1-CreateStagingSlot}
 
 Create a [Run an Azure PowerShell Script](/docs/deployments/azure/running-azure-powershell) step.
 
@@ -67,7 +67,7 @@ So your step should look like:
 ![](/docs/deployments/azure/deploying-a-package-to-an-azure-web-app/azure-remove-staging-slot-script.png)
 :::
 
-### Step 3: Deploy your package {#UsingDeploymentSlotswithAzureWebApps-Step2-DeployyourPackage}
+### Step 3: Deploy your package {#UsingDeploymentSlotsWithAzureWebApps-Step2-DeployYourPackage}
 
 The next step is to deploy your package to the Staging slot.  We do this by creating a [Deploy an Azure Web App](/docs/deployments/azure/deploying-a-package-to-an-azure-web-app) step.
 
@@ -94,7 +94,7 @@ As shown below:
 You can choose to specify the slot directly on the deployment target, or directly on the step (if you wish to deploy to multiple different slots on the same Web App Service, for example), however, the slot on the target will take priority.
 :::
 
-### Step 4: Swap the Staging and Production slots {#UsingDeploymentSlotswithAzureWebApps-Step3-SwaptheStagingandProductionSlots}
+### Step 4: Swap the Staging and Production slots {#UsingDeploymentSlotsWithAzureWebApps-Step3-SwapTheStagingAndProductionSlots}
 
 The final step is to create another Azure PowerShell step to swap the Staging and Production slots.
 
diff --git a/src/pages/docs/deployments/windows/windows-services.md b/src/pages/docs/deployments/windows/windows-services.md
@@ -14,17 +14,17 @@ When deploying, `sc.exe` is used to create a Windows Service using the configure
 To deploy a Windows Service, add a *Deploy a Windows Service* step. For information about adding a step to the deployment process, see the [add step](/docs/projects/steps) section.
 
 
-## Configuring the step {#WindowsServices-ConfiguringtheStep}
+## Configuring the step {#WindowsServices-ConfiguringTheStep}
 
 :::figure
 ![Windows service configuration](/docs/deployments/windows/images/windows-service-configuration.png)
 :::
 
-### Step 1: Select a package {#WindowsServices-Step1-SelectaPackage}
+### Step 1: Select a package {#WindowsServices-Step1-SelectAPackage}
 
 Use the Package Feed and Package ID fields to select the [package](/docs/packaging-applications) containing the executable (.exe) to be installed as a Windows Service.
 
-### Step 2: Configure Windows Service options {#WindowsServices-Step2-ConfigureWindowsServiceoptions}
+### Step 2: Configure Windows Service options {#WindowsServices-Step2-ConfigureWindowsServiceOptions}
 
 | Field               | Meaning                                  |
 | ------------------- | ---------------------------------------- |
@@ -38,7 +38,7 @@ Use the Package Feed and Package ID fields to select the [package](/docs/packagi
 | **State**           | The state of the service after the deployment has completed |
 | **Dependencies**    | Any dependencies that the service has. Separate the names using forward slashes (/). For example: `LanmanWorkstation/TCPIP` |
 
-## How does Octopus actually deploy my Windows Service? {#WindowsServices-HowdoesOctopusactuallydeploymyWindowsService?}
+## How does Octopus actually deploy my Windows Service? {#WindowsServices-HowDoesOctopusActuallyDeployMyWindowsService?}
 
 Out of the box, Octopus will do the right thing to deploy your Windows Service, and the conventions we have chosen will eliminate a lot of problems with file locks, and leaving stale files behind. By default Octopus will follow the conventions described in [Deploying packages](/docs/deployments/packages/) and apply the different features you select in the order described in [Package deployment feature ordering](/docs/deployments/packages/package-deployment-feature-ordering).
 
@@ -91,7 +91,7 @@ This table shows how the combination of the `Start Mode`, `State` and the state
 | Manual | Default | n/a | n/a | Stopped |
 | Unchanged | Default | n/a | n/a | Stopped |
 
-## Setting advanced configuration options {#WindowsServices-Settingadvancedconfigurationoptions}
+## Setting advanced configuration options {#WindowsServices-SettingAdvancedConfigurationOptions}
 
 Windows Services support some advanced settings not exposed by this feature. You can customize your Windows Service by including a `PostDeploy.ps1` [custom script](/docs/deployments/custom-scripts).
 
@@ -113,7 +113,7 @@ This script will run after the Windows Service has been created (or reconfigured
 This Microsoft TechNet [article](https://technet.microsoft.com/en-us/library/cc754599.aspx) is a great reference on the sc.exe utility including the failure action above.
 :::
 
-## Deploying Services built with Topshelf {#WindowsServices-DeployingServicesbuiltwithTopshelf}
+## Deploying Services built with Topshelf {#WindowsServices-DeployingServicesBuiltWithTopshelf}
 
 [Topshelf](http://topshelf-project.com/) is a library to build and work with Windows Services easily by allowing your code to run (and be debugged) inside a Console Application, but giving you the option to install and run as a Windows Service.
 
@@ -166,7 +166,6 @@ Test-Privilege -Identity #{ServiceAccountName} -Privilege SeBatchLogonRight
 > Managed Service Accounts (MSA) allow you to eliminate those never-expire-service-accounts. An MSA is a special domain account that can be managed by the computer that uses it. That computer will change its password periodically without the need of an administrator.
 >
 >
-> *[http://www.zeda.nl/index.php/en/en-managed-service-accounts](http://www.zeda.nl/index.php/en/en-managed-service-accounts)*
 
 To configure the Windows Service to use a Managed Service Account:
 
diff --git a/src/pages/docs/infrastructure/accounts/azure/index.md b/src/pages/docs/infrastructure/accounts/azure/index.md
@@ -18,7 +18,7 @@ When you add an Azure account to Octopus, there are two ways to authenticate wit
 - [Service Principal](#azure-service-principal) (default) is used with resource manager mode (ARM), along with the `az` command line interface.
 - [Management certificate](#azure-management-certificate) is used with service management mode (ASM) or legacy mode.
 
-You can read about the differences in [this document](https://azure.microsoft.com/en-us/documentation/articles/resource-manager-deployment-model/).
+You can read about the differences in [this document](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/deployment-models).
 
 Microsoft Entra ID Service Principal accounts are for use with the **Azure Resource Management (ARM) API** only. Configuring your Octopus Server to authenticate with the service principal you create in Microsoft Entra ID will let you configure finely grained authorization for your Octopus Server.
 
diff --git a/src/pages/docs/infrastructure/workers/kubernetes-worker/storage.md b/src/pages/docs/infrastructure/workers/kubernetes-worker/storage.md
@@ -10,4 +10,4 @@ navOrder: 20
 The Kubernetes worker requires a common filesystem to share packages with its spawned operation pods. This filesystem
 stores binary packages received from the Octopus Server, which are used by the operation being executed.
 
-The Kubernetes worker's storage setup and constraints are identical to the [Kubernetes Agent storage](docs/kubernetes/targets/kubernetes-agent/storage.md).
+The Kubernetes worker's storage setup and constraints are identical to the [Kubernetes Agent storage](/docs/kubernetes/targets/kubernetes-agent/storage).
diff --git a/src/pages/docs/installation/octopus-server-linux-container/troubleshooting-octopus-server-in-a-container.md b/src/pages/docs/installation/octopus-server-linux-container/troubleshooting-octopus-server-in-a-container.md
@@ -13,7 +13,7 @@ The Octopus Server Windows container is deprecated, and no longer maintained. We
 
 ## Ensure you've accepted the EULA
 
-When you create an Octopus Server container, you must agree with the [Octopus Deploy EULA](https://octopus.com/company/legal).
+When you create an Octopus Server container, you must agree with the [Octopus Deploy EULA](https://octopus.com/company/trust).
 
 If you get an error similar to:
 
diff --git a/src/pages/docs/kubernetes/targets/index.md b/src/pages/docs/kubernetes/targets/index.md
@@ -9,7 +9,7 @@ description: Kubernetes deployment targets
 navOrder: 50
 ---
 
-To deploy your application to a Kubernetes cluster, you need Octopus Deploy to know that the cluster exists and how to access it. The cluster is your deployment destination. To represent deployment destinations, Octopus uses [deployment targets](docs/infrastructure/deployment-targets) (a virtual entity). 
+To deploy your application to a Kubernetes cluster, you need Octopus Deploy to know that the cluster exists and how to access it. The cluster is your deployment destination. To represent deployment destinations, Octopus uses [deployment targets](/docs/infrastructure/deployment-targets) (a virtual entity). 
 
 There are two different deployment targets for deploying to Kubernetes, the [Kubernetes Agent](/docs/kubernetes/targets/kubernetes-agent) and the [Kubernetes API](/docs/kubernetes/targets/kubernetes-api) targets.
 
diff --git a/src/pages/docs/packaging-applications/create-packages/versioning.md b/src/pages/docs/packaging-applications/create-packages/versioning.md
@@ -76,7 +76,7 @@ Octopus uses a string-based approach to version numbers. These are the decisions
 
 Maven versions are used by Octopus when an artifact is sourced from an external [Maven feed](/docs/packaging-applications/package-repositories/maven-feeds/). SemVer is still required when versioning any artifact to be deployed to the [built-in](/docs/packaging-applications/package-repositories/built-in-repository) library or an external [NuGet feeds](https://docs.nuget.org/create/hosting-your-own-nuget-feeds), and the only time to use the Maven versioning scheme over SemVer is when you are deploying artifacts to a Maven repository.
 
-The Maven versioning scheme is implemented as a copy of the [ComparableVersion](https://github.com/apache/maven/blob/master/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/ComparableVersion.java) class from the Maven library itself.
+The Maven versioning scheme is implemented as a copy of the [ComparableVersion](https://github.com/sonatype/maven-demo/blob/master/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/ComparableVersion.java) class from the Maven library itself.
 
 Maven version strings have 5 parts:
 
diff --git a/src/pages/docs/releases/deployment-timeline.md b/src/pages/docs/releases/deployment-timeline.md
@@ -7,7 +7,7 @@ description: View and interact with the Deployment Timeline
 navOrder: 132
 ---
 
-The Deployment Timeline provides visual representation of all deployments made to an [Environment](docs/infrastructure/environments) for a [Project](/docs/projects) within a [Tenant](docs/projects/tenants). In additional to providing an easy to understand view of deployment data, the Deployment Timeline allows easy access to perform common workflows, such as deploying the last successful/stable deployment into your environment.
+The Deployment Timeline provides visual representation of all deployments made to an [Environment](/docs/infrastructure/environments) for a [Project](/docs/projects) within a [Tenant](docs/tenants). In additional to providing an easy to understand view of deployment data, the Deployment Timeline allows easy access to perform common workflows, such as deploying the last successful/stable deployment into your environment.
 
 It can be access by clicking the **Timeline** button within the deployment details page.
 
@@ -21,7 +21,7 @@ A drawer opens showing all deployments for the current Environment, Project and
 ![The deployment Timeline with overflow menu for last successful deployment](/docs/releases/timeline/timeline.png)
 :::
 
-For releases that have not been deleted, either manually or via [Retention policies](docs/administration/retention-policies), an overflow menu provides actions that can be triggered:
+For releases that have not been deleted, either manually or via [Retention policies](/docs/administration/retention-policies), an overflow menu provides actions that can be triggered:
 
 1. **Redeploy...** - Redeploys the release
 2. **Deploy to...** - Allows deployment of the release into another environment
diff --git a/src/pages/docs/runbooks/runbook-examples/azure/resource-groups/index.md b/src/pages/docs/runbooks/runbook-examples/azure/resource-groups/index.md
diff --git a/src/pages/docs/security/authentication/azure-ad-authentication.mdx b/src/pages/docs/security/authentication/azure-ad-authentication.mdx
