diff --git a/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx
index 4827785d87..826a52bf4a 100644
--- a/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx
+++ b/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx
@@ -221,6 +221,11 @@ associations cannot be deleted unless they are also purged.
 - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination
 before it is deleted.
 
+- `force_delete` `(bool: false)` - When true, Vault deletes a destination even
+  if its associations cannot be unsynced. Only use `force-delete` as a 
+  last-resort deletion mechanism as it orphans any secrets already synced to the
+  external provider, which requires manual cleanup.
+
 ### Sample request
 
 ```shell-session
diff --git a/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx
index f50aa72fc4..d604751c3b 100644
--- a/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx
+++ b/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx
@@ -223,6 +223,11 @@ associations cannot be deleted unless they are also purged.
 - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination
 before it is deleted.
 
+- `force_delete` `(bool: false)` - When true, Vault deletes a destination even
+  if its associations cannot be unsynced. Only use `force-delete` as a 
+  last-resort deletion mechanism as it orphans any secrets already synced to the
+  external provider, which requires manual cleanup.
+
 ### Sample request
 
 ```shell-session
diff --git a/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx
index d1a2183fa3..06fcd5a7bc 100644
--- a/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx
+++ b/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx
@@ -223,6 +223,11 @@ associations cannot be deleted unless they are also purged.
 - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination
 before it is deleted.
 
+- `force_delete` `(bool: false)` - When true, Vault deletes a destination even
+  if its associations cannot be unsynced. Only use `force-delete` as a 
+  last-resort deletion mechanism as it orphans any secrets already synced to the
+  external provider, which requires manual cleanup.
+
 ### Sample request
 
 ```shell-session
diff --git a/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx
index 40a1a01e44..55f34e1f88 100644
--- a/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx
+++ b/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx
@@ -223,6 +223,11 @@ associations cannot be deleted unless they are also purged.
 - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination
 before it is deleted.
 
+- `force_delete` `(bool: false)` - When true, Vault deletes a destination even
+  if its associations cannot be unsynced. Only use `force-delete` as a 
+  last-resort deletion mechanism as it orphans any secrets already synced to the
+  external provider, which requires manual cleanup.
+
 ### Sample request
 
 ```shell-session