diff --git a/changelog/16950.txt b/changelog/16950.txt
new file mode 100644
index 0000000000..0ee2d5bdc6
--- /dev/null
+++ b/changelog/16950.txt
@@ -0,0 +1,3 @@
+```release-note:improvement
+website/docs: Add documentation around the expensiveness of making lots of lease count quotas in a short period
+```
diff --git a/website/content/api-docs/system/lease-count-quotas.mdx b/website/content/api-docs/system/lease-count-quotas.mdx
index 0f28cc9368..66d588f7f1 100644
--- a/website/content/api-docs/system/lease-count-quotas.mdx
+++ b/website/content/api-docs/system/lease-count-quotas.mdx
@@ -17,6 +17,14 @@ A lease count quota must include a `max_leases` value with an optional `path`
 that can either be a namespace or mount, and can optionally include a path suffix following
 the mount to restrict more specific API paths.
 
+Upon creating a lease count quota, it will be populated with the current count of leases from this path. If there are
+more leases present than the specified `max_leases`, this will cause the lease count to go over the specified
+`max_leases`.
+
+The initial population process can cause a lot of work for Vault - and while creating one lease count quota
+is always fine, if you're planning to create — for example — thousands of lease count quotas for paths with
+millions of leases in an automated way, it is recommended to space out the creation requests.
+
 | Method | Path                            |
 | :----- | :------------------------------ |
 | `POST` | `/sys/quotas/lease-count/:name` |