Azure App Insights: Copilot Agents Guide

Key insights

• Application Insights, a part of Azure Monitor, must be created in your Azure subscription before you enable agent telemetry.
  Copy the connection string from that resource and paste it into your agent’s Settings → Advanced section, then save and republish the agent.
• Use App Insights when built-in analytics fall short: it gives telemetry for real-time monitoring, conversation tracing, and deeper diagnostics.
  This lets you diagnose issues and measure agent behavior beyond summary engagement metrics.
• Microsoft now formalizes support via the Copilot Studio Kit, with a structured setup path that replaces ad-hoc methods.
  This includes guidance for Azure app registration and delegated permission patterns for secure telemetry access.
• High-level integration flow: create Application Insights → copy the connection string → configure in Copilot Studio’s Advanced settings → republish the agent.
  Telemetry then flows into Azure where you can analyze it with workbooks or queries.
• Permission and security steps matter: record the client ID and tenant ID, create a client secret if required, grant delegated API permissions (Data.Read), and assign the Reader role on the App Insights resource.
  This ensures tooling can read telemetry without over-permissioning resources.
• Expect these telemetry types: logged messages, topics triggered, custom telemetry events, and performance patterns for troubleshooting.
  Use KQL queries in Azure to filter events, analyze patterns, and build observability dashboards; note some community reports mention integration limits to watch for during rollout.

Keywords

Azure App Insights for Copilot Studio, App Insights Copilot Studio agents, Monitor Copilot Studio agents with Application Insights, Instrumentation Copilot Studio agents, Telemetry for Copilot agents Azure, Setup Application Insights for Copilot, Logging and tracing Copilot Studio, Observability Azure Copilot agents