Hosted Agent to Hosted Agent A2A delegation returns HOSTED_AGENT_NOT_SUPPORTED

Manivannan Sudha 0 Reputation points
2026-09-25T10:07:40.04+00:00

We have a multi-agent solution in Azure AI Foundry where an orchestrator and multiple business specialists are independently deployed as kind: hosted agents.

Architecture:
Agent A (Hosted)

├── Agent B (Hosted)

├── Agent C (Hosted)

├── Agent D (Hosted)

└── other specialist agents (Hosted)

The specialist agents need to remain independently hosted because they contain custom Python logic, MCP tools, security/RBAC handling, and separate deployment lifecycles.

We followed Microsoft's current GA A2A v1.0 / A2AToolboxTool / RemoteA2A pattern.

We verified:

  • The RemoteA2A connection is configured correctly.
  • A2AToolboxTool is created successfully.
  • The target Hosted Agent has an agent card and incoming A2A configuration.
  • The agent card is accessible.
  • The correct project identity has the required Foundry Agent Consumer role.
  • Authentication and connection resolution succeed.
  • The failure occurs when the actual A2A message is sent.

The platform returns:
-32099
HOSTED_AGENT_NOT_SUPPORTED
The requested A2A operation is not supported for hosted-agent target.
Use a prompt agent as the A2A target.

We also tested direct A2A previously and received the same result. As another workaround, we tried calling the specialist's Responses endpoint directly. The request reaches the Hosted Agent, but its hosting framework requires a trusted Foundry platform user identity in the request context. Forwarding the user ID from the calling Hosted Agent does not populate the trusted context, resulting in an HTTP 500.

Question

Is Hosted → Hosted agent-to-agent delegation currently supported in Azure AI Foundry?

If not, what is the officially supported architecture for keeping multiple custom-code Hosted Agents as independently deployed agents while allowing one Hosted Agent to delegate work to another?

Is there another Foundry-managed mechanism, such as Workflows or another agent/tool composition mechanism, that supports:

Hosted Agent A -> independently deployed Hosted Agent B

without converting Agent B to a Prompt Agent or moving its code inside Agent A?

We want to confirm whether this is a platform limitation or whether there is a supported configuration/transport we are missing.

Azure AI Bot Service
Azure AI Bot Service

An Azure service that provides an integrated environment for bot development.

0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest
  1. Taz 10,046 Reputation points MVP Volunteer Moderator
    2026-09-25T14:12:28.7533333+00:00

    Hi Manivannan,

    Based on Microsoft's current documentation, Hosted Agent → Hosted Agent delegation is not supported as an incoming A2A target in Foundry Agent Service. The documented incoming A2A setup currently requires a Prompt Agent as the target.

    The HOSTED_AGENT_NOT_SUPPORTED error is therefore consistent with the current platform limitation, rather than a missing RBAC or connection setting.

    For independently deployed Hosted Agents with custom Python code, the documented Hosted Agent A2A sample uses an A2A toolbox, but this is for the calling Hosted Agent to access a remote A2A endpoint. It does not make a separately deployed Foundry Hosted Agent a supported incoming A2A target.

    For your requirement, the practical options are to expose the specialist as an external A2A-compatible service that the orchestrator can call, or keep the agents together in the same Agent Framework

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.