cloudflared version

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/private-net/cloudflared/connect-private-hostname.mdx

@@ -57,12 +57,12 @@ End users can connect to private hostnames using the following traffic on-ramps:
 
 Private hostname routing only works for applications connected with `cloudflared`. Other traffic off-ramps require IP-based routes.
 
-| Connector                                                                             | Compatibility |
-| ------------------------------------------------------------------------------------------ | ------------- |
-| [cloudflared](/cloudflare-one/connections/connect-networks/private-net/cloudflared/)                       | ✅           |
-| [WARP-to-WARP](/cloudflare-one/connections/connect-networks/private-net/warp-to-warp/)             | ❌            |
-| [WARP Connector](/cloudflare-one/connections/connect-networks/private-net/warp-connector/) | ❌            |
-| [Magic WAN](/magic-wan/zero-trust/cloudflare-gateway/)                                     | ❌            |
+| Connector                                                                             | Compatibility | Minimum version |
+| ------------------------------------------------------------------------------------------ | ------------- | -- |
+| [cloudflared](/cloudflare-one/connections/connect-networks/private-net/cloudflared/)                       | ✅           | 2025.7.0 |
+| [WARP-to-WARP](/cloudflare-one/connections/connect-networks/private-net/warp-to-warp/)             | ❌            | |
+| [WARP Connector](/cloudflare-one/connections/connect-networks/private-net/warp-connector/) | ❌            | |
+| [Magic WAN](/magic-wan/zero-trust/cloudflare-gateway/)                                     | ❌            | |
 
 ## Connect a private hostname
 

src/content/docs/cloudflare-one/policies/gateway/egress-policies/egress-cloudflared.mdx

@@ -40,11 +40,6 @@ To learn more about how Gateway applies hostname-based egress policies, refer to
 
 ## Prerequisites
 
-::::note[Cloudflare Tunnel version requirement]
-If you're aiming to use Cloudflare Tunnel for source IP anchoring and DNS resolution, you must use `cloudflared` version 2025.7.0 or later.
-::::
-
-
 User traffic is on-ramped to Gateway using one of the following methods:
 
 <Render
@@ -56,6 +51,10 @@ User traffic is on-ramped to Gateway using one of the following methods:
 
 [Connect your private network](/cloudflare-one/connections/connect-networks/private-net/cloudflared/connect-cidr/) to Cloudflare using `cloudflared`. For example, if you want traffic to egress from AWS, connect the private CIDR block of your AWS VPC.
 
+::::note
+Requires `cloudflared` version 2025.7.0 or later.
+::::
+
 ## 2. Add a public hostname route
 
 To route a public hostname through Cloudflare Tunnel: