diff --git a/doc/administration/auth/ldap/ldap-troubleshooting.md b/doc/administration/auth/ldap/ldap-troubleshooting.md
index 7617db1186d79f0924a96e8f6a60233979cf56ad..2e0ffb417330b0a9c700166b92048e677ca75872 100644
--- a/doc/administration/auth/ldap/ldap-troubleshooting.md
+++ b/doc/administration/auth/ldap/ldap-troubleshooting.md
@@ -908,7 +908,7 @@ For more information, see the [official `ldapsearch` documentation](https://linu
 
 ### Using **AdFind** (Windows)
 
-You can use the [`AdFind`](https://social.technet.microsoft.com/wiki/contents/articles/7535.adfind-command-examples.aspx) utility (on Windows based systems) to test that your LDAP server is accessible and authentication is working correctly. AdFind is a freeware utility built by [Joe Richards](https://www.joeware.net/freetools/tools/adfind/index.htm).
+You can use the [`AdFind`](https://learn.microsoft.com/en-us/archive/technet-wiki/7535.adfind-command-examples) utility (on Windows based systems) to test that your LDAP server is accessible and authentication is working correctly. AdFind is a freeware utility built by [Joe Richards](https://www.joeware.net/freetools/tools/adfind/index.htm).
 
 **Return all objects**
 
diff --git a/doc/administration/auth/oidc.md b/doc/administration/auth/oidc.md
index 1e9ebbb5ddc3221fa8c847602bd50f77faccd9c7..90c45b0e0d5131267517a07b8bdb65e60915d299 100644
--- a/doc/administration/auth/oidc.md
+++ b/doc/administration/auth/oidc.md
@@ -233,14 +233,14 @@ gitlab_rails['omniauth_providers'] = [
 
 ### Configure Microsoft Azure
 
-The OpenID Connect (OIDC) protocol for Microsoft Azure uses the [Microsoft identity platform (v2) endpoints](https://learn.microsoft.com/en-us/azure/active-directory/azuread-dev/azure-ad-endpoint-comparison).
+The OpenID Connect (OIDC) protocol for Microsoft Azure uses the [Microsoft identity platform (v2) endpoints](https://learn.microsoft.com/en-us/previous-versions/azure/active-directory/azuread-dev/azure-ad-endpoint-comparison).
 To get started, sign in to the [Azure Portal](https://portal.azure.com). For your app,
 you need the following information:
 
 - A tenant ID. You may already have one. For more information, see the
   [Microsoft Azure Tenant](https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-create-new-tenant) documentation.
 - A client ID and a client secret. Follow the instructions in the
-  [Microsoft Quickstart Register an Application](https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app) documentation
+  [Microsoft Quickstart Register an Application](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) documentation
   to obtain the tenant ID, client ID, and client secret for your app.
 
 Example configuration block for Linux package installations:
@@ -269,7 +269,7 @@ gitlab_rails['omniauth_providers'] = [
 ]
 ```
 
-Microsoft has documented how its platform works with [the OIDC protocol](https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-protocols-oidc).
+Microsoft has documented how its platform works with [the OIDC protocol](https://learn.microsoft.com/en-us/entra/identity-platform/v2-protocols-oidc).
 
 ### Configure Microsoft Azure Active Directory B2C
 
@@ -278,7 +278,7 @@ configuration to work with [Azure Active Directory B2C](https://learn.microsoft.
 For your app, you need the following information from Azure:
 
 - A tenant ID. You may already have one. For more information, review the
-  [Microsoft Azure Tenant](https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-create-new-tenant) documentation.
+  [Microsoft Azure Tenant](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-create-new-tenant) documentation.
 - A client ID and a client secret. Follow the instructions in the
   [Microsoft tutorial](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tutorial-register-applications?tabs=app-reg-ga) documentation to obtain the
   client ID and client secret for your app.
diff --git a/doc/administration/dedicated/configure_instance.md b/doc/administration/dedicated/configure_instance.md
index 6f8980142ab3d5615251538f577dee1ea120abc8..e37666fb4ea7ad378ea35b234cc177b15809b8d8 100644
--- a/doc/administration/dedicated/configure_instance.md
+++ b/doc/administration/dedicated/configure_instance.md
@@ -280,4 +280,4 @@ You can use the [AWS CLI](https://aws.amazon.com/cli/) to verify that access to
 
 The S3 bucket contains a combination of **infrastructure logs** and **application logs** from the GitLab [log system](../../administration/logs/index.md). The logs in the bucket are encrypted using an AWS KMS key that is managed by GitLab. If you choose to enable [BYOK](../../administration/dedicated/create_instance.md#encrypted-data-at-rest-byok), the application logs are not encrypted with the key you provide.
 
-The logs in the S3 bucket are organized by date in `YYYY/MM/DD/HH` format. For example, there would be a directory like `2023/10/12/13`. That directory would contain the logs from October 12, 2023 at 1300 UTC. The logs are streamed into the bucket with [Amazon Kinesis Data Firehose](https://aws.amazon.com/kinesis/data-firehose/).
+The logs in the S3 bucket are organized by date in `YYYY/MM/DD/HH` format. For example, there would be a directory like `2023/10/12/13`. That directory would contain the logs from October 12, 2023 at 1300 UTC. The logs are streamed into the bucket with [Amazon Kinesis Data Firehose](https://aws.amazon.com/firehose/).
diff --git a/doc/administration/dedicated/create_instance.md b/doc/administration/dedicated/create_instance.md
index 3936e39ccb57f59cd0c16af97f0c8ba24da70ddb..b89d4beca87018bdc5b7b87bd8dbfb185ef7c89d 100644
--- a/doc/administration/dedicated/create_instance.md
+++ b/doc/administration/dedicated/create_instance.md
@@ -221,7 +221,7 @@ Consider the following notes:
 
 - The Dedicated instance is not expected to be down the entire duration of the maintenance window. Occasionally, a small period of downtime (on the order of a few tens of seconds) can occur while compute resources restart after they are upgraded. If it occurs, this small period of downtime typically happens during the first half of the maintenance window. Long-running connections may be interrupted during this period. To mitigate this, clients should implement strategies like automatic recovery and retry. Longer periods of downtime during the maintenance window are rare, and GitLab provides notice if longer downtime is anticipated.
 - In case of a performance degradation or downtime during the scheduled maintenance window,
-  the impact to [the system SLA](https://about.gitlab.com/handbook/engineering/infrastructure/team/gitlab-dedicated/slas/) is not counted.
+  the impact to [the system SLA](https://handbook.gitlab.com/handbook/engineering/infrastructure/team/gitlab-dedicated/slas/) is not counted.
 - The weekly scheduled maintenance window can be postponed into another window within the same week.
   This option needs to be agreed with the assigned Customer Success Manager at least one week in advance.
 - The scheduled weekly maintenance window is different from
@@ -243,7 +243,7 @@ For example, GitLab 16.9 released on 2024-02-15. Therefore, tenant instances in
 
 In an event of a platform outage, degradation or a security event requiring urgent action,
 emergency maintenance will be carried out per
-[the emergency change processes](https://about.gitlab.com/handbook/engineering/infrastructure/emergency-change-processes/).
+[the emergency change processes](https://handbook.gitlab.com/handbook/engineering/infrastructure/emergency-change-processes/).
 
 The emergency maintenance is initiated when urgent actions need to be executed by GitLab on a
 Dedicated tenant instance. Communication with the customer will be provided on best effort basis
diff --git a/doc/administration/geo/replication/container_registry.md b/doc/administration/geo/replication/container_registry.md
index 4629ef7b07a6b58979405f0b8dde717abc5bfdf9..f60a8b7bd3565c4a9f6a5877357e6508b228b90e 100644
--- a/doc/administration/geo/replication/container_registry.md
+++ b/doc/administration/geo/replication/container_registry.md
@@ -39,7 +39,7 @@ In addition, Geo also supports [BuildKit cache images](https://github.com/moby/b
 ### Docker
 
 For more information on supported registry storage drivers see
-[Docker registry storage drivers](https://docs.docker.com/registry/storage-drivers/)
+[Docker registry storage drivers](https://docs.docker.com/registry/)
 
 Read the [Load balancing considerations](https://docs.docker.com/registry/deploying/#load-balancing-considerations)
 when deploying the Registry, and how to set up the storage driver for the GitLab integrated
diff --git a/doc/administration/geo/replication/single_sign_on.md b/doc/administration/geo/replication/single_sign_on.md
index 305cb4d872582be022f79b2879189c389433f2a4..6ff8b2fbd8adda9c34758d73df7683d41907fe6a 100644
--- a/doc/administration/geo/replication/single_sign_on.md
+++ b/doc/administration/geo/replication/single_sign_on.md
@@ -40,7 +40,7 @@ application to have multiple callback URLs configured. Check with your IdP provi
 
 If a secondary site uses a different `external_url` to the primary site, then configure your SAML Identity Provider (IdP) to allow the secondary site's SAML callback URL. For example, to configure Okta:
 
-1. [Sign in to Okta](https://www.okta.com/login/).
+1. [Sign in to Okta](https://login.okta.com/).
 1. Go to **Okta Admin Dashboard** > **Applications** > **Your App Name** > **General**.
 1. In **SAML Settings**, select **Edit**.
 1. In **General Settings**, select **Next** to go to **SAML Settings**.
diff --git a/doc/administration/incoming_email.md b/doc/administration/incoming_email.md
index c4ab130b11587f9379b7d4d944dbe48f9d610184..06d902e638becce912f2bb837a70af04f2772e20 100644
--- a/doc/administration/incoming_email.md
+++ b/doc/administration/incoming_email.md
@@ -810,7 +810,7 @@ IMAP. Because [Microsoft is deprecating IMAP usage with Basic Authentication](ht
 To configure GitLab for Microsoft Graph, you need to register an
 OAuth 2.0 application in your Azure Active Directory that has the
 `Mail.ReadWrite` permission for all mailboxes. See the [MailRoom step-by-step guide](https://github.com/tpitale/mail_room/#microsoft-graph-configuration)
-and [Microsoft instructions](https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app)
+and [Microsoft instructions](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app)
 for more details.
 
 Record the following when you configure your OAuth 2.0 application:
diff --git a/doc/administration/integration/diagrams_net.md b/doc/administration/integration/diagrams_net.md
index 9fb9e3eb1d159d3865cd541a9ddccc1566b9461e..6a12809643a6836b2eb46887d97d0828b72dcc66 100644
--- a/doc/administration/integration/diagrams_net.md
+++ b/doc/administration/integration/diagrams_net.md
@@ -44,7 +44,7 @@ docker run -it --rm --name="draw" -p 8080:8080 -p 8443:8443 jgraph/drawio
 Make note of the hostname of the server running the container, to be used as the diagrams.net URL
 when you enable the integration.
 
-For more information, see [Run your own diagrams.net server with Docker](https://www.diagrams.net/blog/diagrams-docker-app).
+For more information, see [Run your own diagrams.net server with Docker](https://www.drawio.com/blog/diagrams-docker-app).
 
 ## Enable Diagrams.net integration
 
diff --git a/doc/administration/logs/index.md b/doc/administration/logs/index.md
index ff55229c2966543c394e7833337f1e42093e09e9..5c4f07b966431712c10a1f88056497dda6c1143c 100644
--- a/doc/administration/logs/index.md
+++ b/doc/administration/logs/index.md
@@ -655,10 +655,10 @@ Example log entries for `/var/log/gitlab/gitaly/current`:
 
 ## Gitaly logs
 
-This file is in `/var/log/gitlab/gitaly/current` and is produced by [runit](http://smarden.org/runit/).
+This file is in `/var/log/gitlab/gitaly/current` and is produced by [runit](https://smarden.org/runit/).
 `runit` is packaged with the Linux package and a brief explanation of its purpose
 is available [in the Linux package documentation](https://docs.gitlab.com/omnibus/architecture/#runit).
-[Log files are rotated](http://smarden.org/runit/svlogd.8.html), renamed in
+[Log files are rotated](https://smarden.org/runit/svlogd.8.html), renamed in
 Unix timestamp format, and `gzip`-compressed (like `@1584057562.s`).
 
 ### `grpc.log`
diff --git a/doc/administration/monitoring/performance/performance_bar.md b/doc/administration/monitoring/performance/performance_bar.md
index e9a209f7d399f5d2beb8f09c73909ccec849e882..2856ccfacf96f936be3f7d20e08c93c8543dbb0f 100644
--- a/doc/administration/monitoring/performance/performance_bar.md
+++ b/doc/administration/monitoring/performance/performance_bar.md
@@ -57,7 +57,7 @@ From left to right, the performance bar displays:
   - [**First Contentful Paint**](https://developer.chrome.com/docs/lighthouse/performance/first-contentful-paint/):
     Time until something was visible to the user. Displays `NaN` if your browser does not
     support this feature.
-  - [**DomContentLoaded**](https://web.dev/critical-rendering-path-measure-crp/) Event.
+  - [**DomContentLoaded**](https://web.dev/articles/critical-rendering-path/measure-crp) Event.
   - **Total number of requests** the page loaded.
 - **Memory**: the amount of memory consumed and objects allocated during the selected request.
   Select it to display a window with more details.
diff --git a/doc/administration/nfs.md b/doc/administration/nfs.md
index 4a669f84d603789830c6bc02145130f98aec4936..1400d8d9b0b2394af962bbb78f9cf3c383fb294e 100644
--- a/doc/administration/nfs.md
+++ b/doc/administration/nfs.md
@@ -169,7 +169,7 @@ use the `hard` option, because (from the man page):
 > use the soft option only when client responsiveness is more important than data integrity
 
 Other vendors make similar recommendations, including
-[System Applications and Products in Data Processing (SAP)](https://wiki.scn.sap.com/wiki/display/Basis/Recommended+mount+options+for+read-write+directories) and NetApp's
+[Recommended mount options for read-write directories](https://help.sap.com/docs/SUPPORT_CONTENT/basis/3354611703.html) and NetApp's
 [knowledge base](https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/What_are_the_differences_between_hard_mount_and_soft_mount),
 they highlight that if the NFS client driver caches data, `soft` means there is no certainty if
 writes by GitLab are actually on disk.
diff --git a/doc/ci/yaml/index.md b/doc/ci/yaml/index.md
index 8a2971c58827d09647d00437bfde3e5eb204d63e..227e5263e36feb0e956588c5b673ae73990bbc1b 100644
--- a/doc/ci/yaml/index.md
+++ b/doc/ci/yaml/index.md
@@ -2630,7 +2630,7 @@ test-job:
 Command or script to execute as the container's entry point.
 
 When the Docker container is created, the `entrypoint` is translated to the Docker `--entrypoint` option.
-The syntax is similar to the [Dockerfile `ENTRYPOINT` directive](https://docs.docker.com/engine/reference/builder/#entrypoint),
+The syntax is similar to the [Dockerfile `ENTRYPOINT` directive](https://docs.docker.com/reference/dockerfile/#entrypoint),
 where each shell token is a separate string in the array.
 
 **Keyword type**: Job keyword. You can use it only as part of a job or in the
@@ -2686,8 +2686,8 @@ arm-sql-job:
 
 **Additional details**:
 
-- `image:docker:platform` maps to the [`docker pull --platform` option](https://docs.docker.com/engine/reference/commandline/pull/#options).
-- `image:docker:user` maps to the [`docker run --user` option](https://docs.docker.com/engine/reference/commandline/run/#options).
+- `image:docker:platform` maps to the [`docker pull --platform` option](https://docs.docker.com/reference/cli/docker/image/pull/#options).
+- `image:docker:user` maps to the [`docker run --user` option](https://docs.docker.com/reference/cli/docker/container/run/#options).
 
 #### `image:pull_policy`
 
diff --git a/doc/editor_extensions/jetbrains_ide/index.md b/doc/editor_extensions/jetbrains_ide/index.md
index 47b25bbf75969fb992b1c473fb9e5498289705d0..2cd0258bad91359d5b09c26793900282c498f956 100644
--- a/doc/editor_extensions/jetbrains_ide/index.md
+++ b/doc/editor_extensions/jetbrains_ide/index.md
@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # GitLab plugin for JetBrains IDEs
 
-The [GitLab plugin](https://plugins.jetbrains.com/plugin/22325-gitlab)
+The [GitLab plugin](https://plugins.jetbrains.com/plugin/22325-gitlab-duo)
 integrates GitLab with JetBrains IDEs. The following JetBrains IDEs are supported:
 
 - IntelliJ IDEA Ultimate — 2023.2
@@ -34,7 +34,7 @@ GitLab for JetBrains supports [GitLab Duo Code Suggestions](../../user/project/r
 
 ## Download the extension
 
-Download the extension from the [JetBrains Plugin Marketplace](https://plugins.jetbrains.com/plugin/22325-gitlab).
+Download the extension from the [JetBrains Plugin Marketplace](https://plugins.jetbrains.com/plugin/22325-gitlab-duo).
 
 ## Configure the extension
 
@@ -47,6 +47,6 @@ Report any issues, bugs, or feature requests in the
 
 ## Related topics
 
-- [Download the plugin](https://plugins.jetbrains.com/plugin/22325-gitlab)
+- [Download the plugin](https://plugins.jetbrains.com/plugin/22325-gitlab-duo)
 - [Plugin documentation](https://gitlab.com/gitlab-org/editor-extensions/gitlab-jetbrains-plugin/-/blob/main/README.md)
 - [View source code](https://gitlab.com/gitlab-org/editor-extensions/gitlab-jetbrains-plugin)
diff --git a/doc/gitlab-basics/start-using-git.md b/doc/gitlab-basics/start-using-git.md
index 18b9d03864338b1f465ff77f64290019a5b758f7..5323b3e32e62a7611455b145002b0cf301261b5c 100644
--- a/doc/gitlab-basics/start-using-git.md
+++ b/doc/gitlab-basics/start-using-git.md
@@ -36,7 +36,7 @@ prompt, command shell, and command line). Here are some options:
   - [iTerm2](https://iterm2.com/). You can integrate it with [Zsh](https://git-scm.com/book/id/v2/Appendix-A%3A-Git-in-Other-Environments-Git-in-Zsh) and [Oh My Zsh](https://ohmyz.sh/) for color highlighting and other advanced features.
 - For Windows users:
   - Built-in command line. On the Windows taskbar, select the search icon and type `cmd`.
-  - [PowerShell](https://learn.microsoft.com/en-us/powershell/scripting/windows-powershell/install/installing-windows-powershell?view=powershell-7.3&viewFallbackFrom=powershell-7).
+  - [PowerShell](https://learn.microsoft.com/en-us/powershell/scripting/windows-powershell/overview).
   - Git Bash. It is built into [Git for Windows](https://gitforwindows.org/).
 - For Linux users:
   - Built-in [Linux Terminal](https://ubuntu.com/tutorials/command-line-for-beginners#3-opening-a-terminal).
diff --git a/doc/install/google_cloud_platform/index.md b/doc/install/google_cloud_platform/index.md
index 3874b9d9c316172380f8242e5347fd08ea41a0f5..2933c76adab2810486d5bb58f3ca2658cee3bfcf 100644
--- a/doc/install/google_cloud_platform/index.md
+++ b/doc/install/google_cloud_platform/index.md
@@ -93,7 +93,7 @@ here's how you configure GitLab to be aware of the change:
 
    ![SSH button](img/vm_created.png)
 
-   In the future you might want to set up [connecting with an SSH key](https://cloud.google.com/compute/docs/instances/connecting-to-instance)
+   In the future you might want to set up [connecting with an SSH key](https://cloud.google.com/compute/docs/connect/standard-ssh)
    instead.
 
 1. Edit the configuration file of the Linux package using your favorite text editor:
diff --git a/doc/install/postgresql_extensions.md b/doc/install/postgresql_extensions.md
index 080f73e35c1c2e834dbcde2e5f11b69174266a44..68ef249236163dcc0e222dd97ed37c9601f22269 100644
--- a/doc/install/postgresql_extensions.md
+++ b/doc/install/postgresql_extensions.md
@@ -21,7 +21,7 @@ You must load the following extensions into the main GitLab database (defaults t
 | `btree_gist` | 13.1                   |
 | `plpgsql`    | 11.7                   |
 
-If you are using [GitLab Geo](https://about.gitlab.com/solutions/geo/), you must load the following
+If you are using [GitLab Geo](../administration/geo/index.md), you must load the following
 extensions into all secondary tracking databases (defaults to `gitlabhq_geo_production`):
 
 | Extension    | Minimum GitLab version |