diff --git a/doc/administration/geo/secondary_proxy/runners.md b/doc/administration/geo/secondary_proxy/runners.md
index befb880e8de463efcd63645e8004a7cb4742fe94..d6fba08b886d9b4c8cb8bb41bb3b3b1fc5e2bc7a 100644
--- a/doc/administration/geo/secondary_proxy/runners.md
+++ b/doc/administration/geo/secondary_proxy/runners.md
@@ -11,11 +11,11 @@ DETAILS:
 **Offering:** Self-managed
 **Status:** Experiment
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/415179) in GitLab 16.7 [with a flag](../../feature_flags.md) named `geo_proxy_check_pipeline_refs`. Disabled by default.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/415179) in GitLab 16.7 [with a flag](../../feature_flags.md) named `geo_proxy_check_pipeline_refs`. Enabled by default in 16.9
 
 FLAG:
-On self-managed GitLab, by default this feature is not available.
-To make it available, an administrator can [enable the feature flag](../../feature_flags.md) named `geo_proxy_check_pipeline_refs`. On GitLab.com, this feature is not available.  
+On self-managed GitLab, by default this feature is enabled.
+To disable it, an administrator can [disable the feature flag](../../feature_flags.md) named `geo_proxy_check_pipeline_refs`. On GitLab.com, this feature is not available.
 
 With [Geo proxying for secondary sites](index.md), it is possible to register a `gitlab-runner` with a secondary site. This offloads load from the primary instance.
 
diff --git a/ee/config/feature_flags/development/geo_proxy_check_pipeline_refs.yml b/ee/config/feature_flags/development/geo_proxy_check_pipeline_refs.yml
index 226814357b82d62aa2eb42de6b02ad191b04cb38..0457f14865ec4fae8eef5561daf1b2db9522e5f8 100644
--- a/ee/config/feature_flags/development/geo_proxy_check_pipeline_refs.yml
+++ b/ee/config/feature_flags/development/geo_proxy_check_pipeline_refs.yml
@@ -5,4 +5,4 @@ rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/434041
 milestone: '16.7'
 type: development
 group: group::geo
-default_enabled: false
+default_enabled: true