microsoft-foundry / microsoft-foundry/foundry-samples
Remote invocations return no data when running `azd ai agent invoke`
@brandom-msft is already working on this.
Since Aug 13, 2026.
- Dominant language
- Bicep
- Stars
- 445
- Forks
- 494
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 38
Description
Description:
When testing Scenario 3: LangGraph Toolbox (Responses), remote invocations do not return response data when running azd ai agent invoke --protocol invocations '{"input": "What can you help me with?"}' or azd ai agent invoke --protocol invocations '{"input": "Give me a short code example."}'. The command starts successfully and prints the invocation metadata (agent, session, conversation, and trace ID), but no actual response is returned.
Running azd ai agent monitor --tail 20 shows that the request is received and processed by the service, and the logs contain backend errors such as openai.NotFoundError / DeploymentNotFound.
Steps to Reproduce:
mkdir github-copilot-invocationsandcd github-copilot-invocations- Run
azd ai agent init --manifest "https://github.com/microsoft-foundry/foundry-samples/blob/main/samples/python/hosted-agents/bring-your-own/invocations/github-copilot/agent.manifest.yaml"and select locationnorthcentralus. - Run
azd up. - Run
azd ai agent invoke --protocol invocations '{"input": "What can you help me with?"}'orazd ai agent invoke --protocol invocations '{"input": "Give me a short code example."}'. - Run
azd ai agent monitor --tail 20.
Environment:
- Azd version: azd version 1.25.3-daily.6367899 (commit 5415d38ec116421c280491764d5ff559e6cd0f7f) (daily).
- AI Agent Extension version: 0.1.34-preview
- Manifest URL: https://github.com/microsoft-foundry/foundry-samples/blob/main/samples/python/hosted-agents/bring-your-own/responses/langgraph-toolbox/agent.manifest.yaml
- OS: Windows
- Location:
northcentralus.
Expected Behavior:
Remote invoke should succeed.
@JeffreyCA and @RickWinter for notification.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.