Your organisation is deploying an AI agent on Microsoft Foundry and wants end-to-end observability of token consumption, latency, error rates, and quality scores aligned to WAF Performance Efficiency. Which design path should you recommend?
- AWire Foundry traces directly to a Log Analytics workspace and skip Application Insights entirely.
- BStart tracing in Foundry, then add Azure Monitor OpenTelemetry Distro with the Foundry SDK. Correct
- CUse the JavaScript SDK alongside the Foundry SDK to capture agent traces in the browser layer.
- DRun a self-hosted Microsoft Agent Framework instance for tracing instead of using Application Insights.
Why A is wrong: Application Insights is the documented unified experience for AI-agent observability across Foundry, Copilot Studio, and third-party frameworks; bypassing it forfeits the prebuilt agent dashboards.
Why B is correct: Correct. The Application Insights documentation describes the managed-hosting (Azure AI Foundry) path as starting with tracing setup in Foundry, then using the Azure Monitor OpenTelemetry Distro with the Foundry SDK for app-side instrumentation.
Why C is wrong: The JavaScript SDK is a browser path that does not capture server-side agent traces or Foundry SDK signals.
Why D is wrong: The Microsoft Agent Framework is the documented self-hosting path; for Foundry-hosted agents, the unified APM experience lives in Application Insights.