.NET: Python: Add Activity Protocol support to azure-ai-agentserver-agentframework

[saigandhi-pai]

Summary

The Python azure-ai-agentserver-agentframework package (v1.0.0b17) only supports the Responses API protocol. There is no support for the Activity Protocol needed for Teams/Bot Service/M365 integration.

This means Python hosted agents deployed to Azure AI Foundry cannot be published as A365 Digital Workers or respond to Teams messages — only the C# SDK (Microsoft.Agents.Builder) supports Activity Protocol today.

Current State

• Every Python hosted agent sample in microsoft-foundry/foundry-samples uses protocol: responses only
• The from_agent_framework() wrapper only exposes the Responses API endpoint
• The only sample with activity_protocol is the C# FoundryA365 sample
• The agent.yaml schema accepts activity_protocol but the Python server doesn't handle it

Impact

To deploy a Python-based Claude Agent SDK agent as an A365 Digital Worker with Teams messaging, we currently need a C# wrapper that handles Activity Protocol and forwards to the Python agent — adding unnecessary complexity.

Requested Feature

Add Activity Protocol support to from_agent_framework() or provide a Python equivalent of the C# IAgentHttpAdapter that handles:

• Bot Framework Activity payloads at /api/messages
• Typing indicators
• Conversation state
• Integration with agent.yaml activity_protocol declaration

Workaround

Currently using a hybrid approach:

• C# Microsoft.Agents.Builder handles Activity Protocol (port 8088)
• Python Claude Agent SDK runs as sidecar HTTP service (port 8089)
• C# forwards messages to Python for processing

This works but is not ideal for Python-first teams.

Environment

• azure-ai-agentserver-agentframework v1.0.0b17
• agent-framework-claude v1.0.0b260304
• Azure AI Foundry hosted agents
• North Central US region