diff --git a/website/docs/language/meta-arguments/lifecycle.html.md b/website/docs/language/meta-arguments/lifecycle.html.md
index 6671ff3b31e5..9dec5a5cc8d8 100644
--- a/website/docs/language/meta-arguments/lifecycle.html.md
+++ b/website/docs/language/meta-arguments/lifecycle.html.md
@@ -45,6 +45,9 @@ The following arguments can be used within a `lifecycle` block:
     such features, so you must understand the constraints for each resource
     type before using `create_before_destroy` with it.
 
+    Destroy provisioners of this resource will not run if `create_before_destroy`
+    is set to `true`. We may address this in the future, and this [GitHub issue](https://github.com/hashicorp/terraform/issues/13549) contains more details.
+
 * `prevent_destroy` (bool) - This meta-argument, when set to `true`, will
   cause Terraform to reject with an error any plan that would destroy the
   infrastructure object associated with the resource, as long as the argument
diff --git a/website/docs/language/resources/provisioners/syntax.html.md b/website/docs/language/resources/provisioners/syntax.html.md
index 3a8eb95eb290..9bbb75979695 100644
--- a/website/docs/language/resources/provisioners/syntax.html.md
+++ b/website/docs/language/resources/provisioners/syntax.html.md
@@ -237,6 +237,9 @@ fail, Terraform will error and rerun the provisioners again on the next
 `terraform apply`. Due to this behavior, care should be taken for destroy
 provisioners to be safe to run multiple times.
 
+    Destroy provisioners of this resource will not run if `create_before_destroy`
+    is set to `true`. We may address this in the future, and this [GitHub issue](https://github.com/hashicorp/terraform/issues/13549) contains more details.
+
 Destroy-time provisioners can only run if they remain in the configuration
 at the time a resource is destroyed. If a resource block with a destroy-time
 provisioner is removed entirely from the configuration, its provisioner