diff --git a/website/pages/docs/integrations/consul-connect.mdx b/website/pages/docs/integrations/consul-connect.mdx
index b28c10dd8..7e4583b2b 100644
--- a/website/pages/docs/integrations/consul-connect.mdx
+++ b/website/pages/docs/integrations/consul-connect.mdx
@@ -38,6 +38,10 @@ manage TLS certificates. This is transparent to job specification authors as
 security features in Connect continue to work even as the application scales up
 or down or gets rescheduled by Nomad.
 
+For using the Consul Connect integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/nomad/consul-integration/nomad-connect-acl)
+guide.
+
 # Nomad Consul Connect Example
 
 The following section walks through an example to enable secure communication
@@ -325,8 +329,6 @@ dashes (`-`) are converted to underscores (`_`) in environment variables so
 - The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
   proxy sidecar on client nodes.
 - Consul Connect Native is not yet supported ([#6083][gh6083]).
-- Consul Connect HTTP and gRPC checks are not yet supported ([#6120][gh6120]).
-- Consul ACLs are not yet supported ([#6701][gh6701]).
 - Only the Docker, `exec`, `raw_exec`, and `java` drivers support network namespaces
   and Connect.
 - Changes to the `connect` stanza may not properly trigger a job update