Build26-DEM341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentel
Demo walkthrough and sample code for standardized multi-agent observability across clouds using Azure AI Foundry and OpenTelemetry GenAI semantic conventions. From Microsoft Build 2026.
Teams are shipping agents across clouds and frameworks, but telemetry is fragmented. In this demo, see how Microsoft Foundry and OpenTelemetry GenAI semantic conventions bring consistent observability to agents built with different frameworks and hosted on different clouds. We will walk through a multi-agent travel concierge, diagnose routing and latency with unified traces, and close the loop with trace-based evaluation in Microsoft Foundry.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/microsoft-build26-dem341-any-agent-any-cloud-standardized-tracing-with-foundry-a — read its card at https://meshkore.com/agent/microsoft-build26-dem341-any-agent-any-cloud-standardized-tracing-with-foundry-a/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/microsoft-build26-dem341-any-agent-any-cloud-standardized-tracing-with-foundry-aFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/microsoft-build26-dem341-any-agent-any-cloud-standardized-tracing-with-foundry-a/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own Build26-DEM341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentel?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.