diff --git a/content/departments/data-analytics/how-to-airgap-disable-telemetry.md b/content/departments/data-analytics/how-to-airgap-disable-telemetry.md
index ed9b54c9bc89..14e1c6cd51e7 100644
--- a/content/departments/data-analytics/how-to-airgap-disable-telemetry.md
+++ b/content/departments/data-analytics/how-to-airgap-disable-telemetry.md
@@ -11,7 +11,7 @@ There are two primary ways that we collect usage data from self-hosted Sourcegra
 
 For recent versions of Sourcegraph, disabling either form of usage data collection requires a license key tag that permits it.
 
-1. First, the customer must receive a [license key that has the appropriate tag(s) that permit "air gapped" usage](departments/technical-success/ce/process/license_key.md). Currently, the options that permit portions of this are "Allow air gapped", "Allow disable telemetry export", and any enterprise plans that explicitly permit "air gapped" usage.
+1. First, the customer must receive a [license key that has the appropriate tag(s) that permit "air gapped" usage](../technical-success/ce/process/license_keys.md). Currently, the options that permit portions of this are "Allow air gapped", "Allow disable telemetry export", and any enterprise plans that explicitly permit "air gapped" usage.
 
 - When this license key tag is applied to the customer instance, event-level telemetry exports (#2 in the [list above](#types-of-usage-data-we-collect)) will be automatically stopped.