12 files changed, 25 insertions, 39 deletions
diff --git a/doc/topics/autodevops/cicd_variables.md b/doc/topics/autodevops/cicd_variables.md
index dff36727bf2..a5897e0b233 100644
--- a/doc/topics/autodevops/cicd_variables.md
+++ b/doc/topics/autodevops/cicd_variables.md
@@ -255,7 +255,7 @@ production, GitLab creates a `production_manual` job.
 
 You can also enable manual deployment in your [project settings](requirements.md#auto-devops-deployment-strategy).
 
-## Deploy policy for canary environments **(PREMIUM)**
+## Deploy policy for canary environments **(PREMIUM ALL)**
 
 You can use a [canary environment](../../user/project/canary_deployments.md) before
 deploying any changes to production.
@@ -265,7 +265,7 @@ If you set `CANARY_ENABLED`, GitLab creates two [manual jobs](../../ci/pipelines
 - `canary` - Deploys the application to the canary environment.
 - `production_manual` - Deploys the application to production.
 
-## Incremental rollout to production **(PREMIUM)**
+## Incremental rollout to production **(PREMIUM ALL)**
 
 Use an incremental rollout to continuously deploy your application,
 starting with only a few pods. You can increase the number of pods
@@ -310,7 +310,7 @@ With `INCREMENTAL_ROLLOUT_MODE` set to `manual` and with `STAGING_ENABLED`:
 
 ![Rollout and staging enabled](img/rollout_staging_enabled.png)
 
-## Timed incremental rollout to production **(PREMIUM)**
+## Timed incremental rollout to production **(PREMIUM ALL)**
 
 Use a timed incremental rollout to continuously deploy your application, starting with
 only a few pods.
diff --git a/doc/topics/autodevops/cloud_deployments/auto_devops_with_eks.md b/doc/topics/autodevops/cloud_deployments/auto_devops_with_eks.md
index b85b99d1874..d8544f3f382 100644
--- a/doc/topics/autodevops/cloud_deployments/auto_devops_with_eks.md
+++ b/doc/topics/autodevops/cloud_deployments/auto_devops_with_eks.md
@@ -178,9 +178,6 @@ The jobs are separated into stages:
   - Jobs suffixed with `-sast` run static analysis on the current code to check for potential
     security issues, and are allowed to fail ([Auto SAST](../stages.md#auto-sast))
   - The `secret-detection` job checks for leaked secrets and is allowed to fail ([Auto Secret Detection](../stages.md#auto-secret-detection))
-  - The `license_scanning` job searches the application's dependencies to determine each of their
-    licenses and is allowed to fail
-    ([Auto License Compliance](../stages.md#auto-license-compliance))
 
 - **Review** - Pipelines on the default branch include this stage with a `dast_environment_deploy` job.
   To learn more, see [Dynamic Application Security Testing (DAST)](../../../user/application_security/dast/index.md).
@@ -230,8 +227,7 @@ in **Settings > CI/CD > Variables**.
 
 ### Work with branches
 
-Following the [GitLab flow](../../gitlab_flow.md#working-with-feature-branches),
-you should next create a feature branch to add content to your application:
+Next, create a feature branch to add content to your application:
 
 1. In your project's repository, go to the following file: `app/views/welcome/index.html.erb`.
    This file should only contain a paragraph: `<p>You're on Rails!</p>`.
diff --git a/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md b/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md
index f6a6c16e010..26902fa1168 100644
--- a/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md
+++ b/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md
@@ -4,7 +4,7 @@ group: Environments
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Use Auto DevOps to deploy an application to Google Kubernetes Engine **(FREE)**
+# Use Auto DevOps to deploy an application to Google Kubernetes Engine **(FREE ALL)**
 
 In this tutorial, we'll help you to get started with [Auto DevOps](../index.md)
 through an example of how to deploy an application to Google Kubernetes Engine (GKE).
@@ -182,9 +182,6 @@ The jobs are separated into stages:
   - Jobs suffixed with `-sast` run static analysis on the current code to check for potential
     security issues, and are allowed to fail ([Auto SAST](../stages.md#auto-sast))
   - The `secret-detection` job checks for leaked secrets and is allowed to fail ([Auto Secret Detection](../stages.md#auto-secret-detection))
-  - The `license_scanning` job searches the application's dependencies to determine each of their
-    licenses and is allowed to fail
-    ([Auto License Compliance](../stages.md#auto-license-compliance))
 
 - **Review** - Pipelines on the default branch include this stage with a `dast_environment_deploy` job.
   For more information, see [Dynamic Application Security Testing (DAST)](../../../user/application_security/dast/index.md).
@@ -235,8 +232,7 @@ in **Settings > CI/CD > Variables**.
 
 ### Work with branches
 
-Following the [GitLab flow](../../gitlab_flow.md#working-with-feature-branches),
-you should next create a feature branch to add content to your application:
+Next, create a feature branch to add content to your application:
 
 1. In your project's repository, go to the following file: `app/views/welcome/index.html.erb`.
    This file should only contain a paragraph: `<p>You're on Rails!</p>`.
diff --git a/doc/topics/autodevops/customize.md b/doc/topics/autodevops/customize.md
index e7fe4ce6e0b..e920ae5e5e1 100644
--- a/doc/topics/autodevops/customize.md
+++ b/doc/topics/autodevops/customize.md
@@ -4,7 +4,7 @@ group: Environments
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Customize Auto DevOps **(FREE)**
+# Customize Auto DevOps **(FREE ALL)**
 
 You can customize components of Auto DevOps to fit your needs. For example, you can:
 
diff --git a/doc/topics/autodevops/index.md b/doc/topics/autodevops/index.md
index d5ebd4e9fcb..18b7c825066 100644
--- a/doc/topics/autodevops/index.md
+++ b/doc/topics/autodevops/index.md
@@ -4,7 +4,7 @@ group: Environments
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Auto DevOps **(FREE)**
+# Auto DevOps **(FREE ALL)**
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/38366) in GitLab 11.0.
 > - Support for the GitLab agent was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/299350) in GitLab 14.5.
@@ -37,7 +37,6 @@ Auto DevOps supports development during each of the [DevOps stages](stages.md).
 | Test | [Auto Code Intelligence](stages.md#auto-code-intelligence) |
 | Test | [Auto Code Quality](stages.md#auto-code-quality) |
 | Test | [Auto Container Scanning](stages.md#auto-container-scanning) |
-| Test | [Auto License Compliance](stages.md#auto-license-compliance) |
 | Deploy | [Auto Review Apps](stages.md#auto-review-apps) |
 | Deploy | [Auto Deploy](stages.md#auto-deploy) |
 | Secure | [Auto Dynamic Application Security Testing (DAST)](stages.md#auto-dast) |
diff --git a/doc/topics/autodevops/multiple_clusters_auto_devops.md b/doc/topics/autodevops/multiple_clusters_auto_devops.md
index 1b6b5bc33c0..2cb748ab2e9 100644
--- a/doc/topics/autodevops/multiple_clusters_auto_devops.md
+++ b/doc/topics/autodevops/multiple_clusters_auto_devops.md
@@ -4,7 +4,7 @@ group: Environments
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Multiple Kubernetes clusters for Auto DevOps **(FREE)**
+# Multiple Kubernetes clusters for Auto DevOps **(FREE ALL)**
 
 When using Auto DevOps, you can deploy different environments to different Kubernetes clusters.
 
diff --git a/doc/topics/autodevops/prepare_deployment.md b/doc/topics/autodevops/prepare_deployment.md
index e69c0ca0909..c5a758e5d70 100644
--- a/doc/topics/autodevops/prepare_deployment.md
+++ b/doc/topics/autodevops/prepare_deployment.md
@@ -4,7 +4,7 @@ group: Environments
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Prepare Auto DevOps for deployment **(FREE)**
+# Prepare Auto DevOps for deployment **(FREE ALL)**
 
 If you enable Auto DevOps without setting the base domain and deployment
 strategy, GitLab can't deploy your application directly. Therefore, we
diff --git a/doc/topics/autodevops/requirements.md b/doc/topics/autodevops/requirements.md
index bfb88cf0dc4..47d79fcfc6b 100644
--- a/doc/topics/autodevops/requirements.md
+++ b/doc/topics/autodevops/requirements.md
@@ -4,7 +4,7 @@ group: Environments
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Requirements for Auto DevOps **(FREE)**
+# Requirements for Auto DevOps **(FREE ALL)**
 
 Before enabling [Auto DevOps](index.md), we recommend you to prepare it for
 deployment. If you don't, you can use it to build and test your apps, and
diff --git a/doc/topics/autodevops/stages.md b/doc/topics/autodevops/stages.md
index 6be8a71cdbc..8d89736b56d 100644
--- a/doc/topics/autodevops/stages.md
+++ b/doc/topics/autodevops/stages.md
@@ -4,7 +4,7 @@ group: Environments
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Stages of Auto DevOps **(FREE)**
+# Stages of Auto DevOps **(FREE ALL)**
 
 The following sections describe the stages of [Auto DevOps](index.md).
 Read them carefully to understand how each one works.
@@ -227,7 +227,7 @@ warnings on [Ultimate](https://about.gitlab.com/pricing/) licenses.
 
 For more information, see [Secret Detection](../../user/application_security/secret_detection/index.md).
 
-## Auto Dependency Scanning **(ULTIMATE)**
+## Auto Dependency Scanning **(ULTIMATE ALL)**
 
 Dependency Scanning runs analysis on the project's dependencies and checks for potential security issues.
 The Auto Dependency Scanning stage is skipped on licenses other than
@@ -240,20 +240,15 @@ check out. The merge request widget displays any security warnings detected,
 For more information, see
 [Dependency Scanning](../../user/application_security/dependency_scanning/index.md).
 
-## Auto License Compliance **(ULTIMATE)**
+<!--- start_remove The following content will be removed on remove_date: '2023-11-22' -->
 
-> Introduced in GitLab 11.0.
+## Auto License Compliance (removed) **(ULTIMATE ALL)**
 
-License Compliance uses the
-[License Compliance Docker image](https://gitlab.com/gitlab-org/security-products/analyzers/license-finder)
-to search the project dependencies for their license. The Auto License Compliance stage
-is skipped on licenses other than [Ultimate](https://about.gitlab.com/pricing/).
+This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/387561) in GitLab 15.9
+and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/421363) in 16.3.
+Use Auto Dependency Scanning instead.
 
-After creating the report, it's uploaded as an artifact which you can later download and
-check out. The merge request displays any detected licenses.
-
-For more information, see
-[License Compliance](../../user/compliance/license_compliance/index.md).
+<!--- end_remove -->
 
 ## Auto Container Scanning
 
@@ -304,7 +299,7 @@ deploys with Auto DevOps can undo your changes. Also, if you change something
 and want to undo it by deploying again, Helm may not detect that anything changed
 in the first place, and thus not realize that it needs to re-apply the old configuration.
 
-## Auto DAST **(ULTIMATE)**
+## Auto DAST **(ULTIMATE ALL)**
 
 Dynamic Application Security Testing (DAST) uses the popular open source tool
 [OWASP ZAProxy](https://github.com/zaproxy/zaproxy) to analyze the current code
@@ -345,7 +340,7 @@ You can disable DAST:
 - Only on feature branches by setting `REVIEW_DISABLED` variable to
   `"true"`. This also disables the Review App.
 
-## Auto Browser Performance Testing **(PREMIUM)**
+## Auto Browser Performance Testing **(PREMIUM ALL)**
 
 > Introduced in GitLab 10.4.
 
@@ -366,7 +361,7 @@ file named `.gitlab-urls.txt` in the root directory, one file per line. For exam
 Any browser performance differences between the source and target branches are also
 [shown in the merge request widget](../../ci/testing/browser_performance_testing.md).
 
-## Auto Load Performance Testing **(PREMIUM)**
+## Auto Load Performance Testing **(PREMIUM ALL)**
 
 > Introduced in GitLab 13.2.
 
diff --git a/doc/topics/autodevops/troubleshooting.md b/doc/topics/autodevops/troubleshooting.md
index 21a74cca07a..11b5265b9a3 100644
--- a/doc/topics/autodevops/troubleshooting.md
+++ b/doc/topics/autodevops/troubleshooting.md
@@ -4,7 +4,7 @@ group: Environments
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Troubleshooting Auto DevOps **(FREE)**
+# Troubleshooting Auto DevOps **(FREE ALL)**
 
 The information in this documentation page describes common errors when using
 Auto DevOps, and any available workarounds.
diff --git a/doc/topics/autodevops/upgrading_auto_deploy_dependencies.md b/doc/topics/autodevops/upgrading_auto_deploy_dependencies.md
index 3426f8dad42..dc18f863844 100644
--- a/doc/topics/autodevops/upgrading_auto_deploy_dependencies.md
+++ b/doc/topics/autodevops/upgrading_auto_deploy_dependencies.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference
 ---
 
-# Upgrading deployments for newer Auto Deploy dependencies **(FREE)**
+# Upgrading deployments for newer Auto Deploy dependencies **(FREE ALL)**
 
 [Auto Deploy](stages.md#auto-deploy) is a feature that deploys your application to a Kubernetes cluster.
 It consists of several dependencies:
diff --git a/doc/topics/autodevops/upgrading_postgresql.md b/doc/topics/autodevops/upgrading_postgresql.md
index ffb72b802f7..d2410da76aa 100644
--- a/doc/topics/autodevops/upgrading_postgresql.md
+++ b/doc/topics/autodevops/upgrading_postgresql.md
@@ -4,7 +4,7 @@ group: Environments
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Upgrading PostgreSQL for Auto DevOps **(FREE)**
+# Upgrading PostgreSQL for Auto DevOps **(FREE ALL)**
 
 When `POSTGRES_ENABLED` is `true`, Auto DevOps provides an
 [in-cluster PostgreSQL database](customize.md#postgresql-database-support) for your application.