Skip to content

[docs] Clarify Foundry project connection injection in hosted-agent publish mode #1133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aspire-repo-bot wants to merge 2 commits into
base: release/13.4
Choose a base branch
from
Open

[docs] Clarify Foundry project connection injection in hosted-agent publish mode #1133

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b720c3c
docs: clarify Foundry project connection injection in publish mode fo…
aspire-repo-bot[bot] May 30, 2026
3511f28
Address review feedback (1 thread)
IEvangelist May 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...ontent/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
Loading