diff --git a/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx b/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
index c8079444e..56f9fcc06 100644
--- a/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
@@ -213,6 +213,21 @@ The preceding code exposes:
 - The `public` endpoint of the `api` project with anonymous access
 - The `admin` endpoint of the `api` project that requires authentication
 
+### Show tunnel URLs
+
+While the dev tunnel is running, the Aspire dashboard publishes the public tunnel URL, the inspect URL, and the local endpoint URL as highlighted properties on the tunnel port resource's property pane so they're discoverable at a glance.
+
+You can also select the highlighted **Show tunnel URLs** command from the tunnel port resource's command menu in the dashboard. This opens a message box listing:
+
+- **Tunnel URL** — the public dev tunnel URL for the port
+- **Inspect URL** — the [Dev Tunnels inspection URL](https://learn.microsoft.com/azure/developer/dev-tunnels/get-started#host) for viewing tunneled HTTP traffic
+- **Local endpoint URL** — the local address the tunnel forwards to, once allocated
+
+<Aside type="note">
+  The **Show tunnel URLs** command is only enabled once the tunnel port is
+  running and its public URL has been allocated.
+</Aside>
+
 ### Service discovery integration
 
 When another resource references a dev tunnel, environment variables are injected using the Aspire service discovery configuration format: