diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host.mdx
index 371340207..18e9eab24 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host.mdx
@@ -460,7 +460,7 @@ In run mode, Aspire also adds dashboard URLs for `/responses`, `/liveness`, and
 
 For .NET hosted agents, add your Service Defaults project reference and call `builder.AddServiceDefaults()` in the hosted-agent app so logs, metrics, traces, HTTP instrumentation, and OTLP export flow into the Aspire dashboard. Then enable telemetry on the Foundry Responses chat client that backs the Microsoft Agent Framework (MAF) agent.
 
-In publish mode, Aspire creates an `AzureHostedAgentResource` and publishes the container to the project-associated registry.
+In publish mode, Aspire creates an `AzureHostedAgentResource` and publishes the container to the project-associated registry. Aspire also automatically injects the Foundry project connection environment variables — including `ConnectionStrings__<project-name>` and the project endpoint — into the deployment container so the hosted agent has access to the Foundry project at runtime. This publish-time injection is part of the hosted-agent publishing step, so it still applies even if the hosted-agent resource doesn't otherwise reference the Foundry project.
 
 If you omit the `project` argument, Aspire uses an existing Foundry project from the app model or creates one automatically.