หมายเหตุ
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลอง ลงชื่อเข้าใช้หรือเปลี่ยนไดเรกทอรีได้
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลองเปลี่ยนไดเรกทอรีได้
Important
This feature is part of Frontier preview program. Frontier connects you directly with Microsoft’s latest AI innovations. Frontier previews are subject to the existing preview terms of your customer agreements. As these features are still in development, their availability and capabilities may change over time.
After you connect a supported third-party platform and synchronize its agents into the Microsoft 365 agent registry, Microsoft Agent 365 can collect available activity telemetry and present it in a common monitoring experience.
Use this capability to:
- View third-party agents alongside Microsoft agents.
- Review sessions and executions.
- Investigate exceptions and runtime behavior.
- Analyze operational trends.
- Review available tool and execution activity.
For platform-specific permissions and telemetry setup, see the relevant Connected platforms configuration guide.
Supported observability platforms
| Platform | Environment |
|---|---|
| Amazon Bedrock | Agents Classic and AgentCore |
| Google Vertex AI | Vertex AI agents |
| Anthropic Claude | Managed Agents |
Observability availability and metric coverage vary by platform.
Configure data collection
Agent observability data collection is enabled by default for new connections. To disable collection, edit the connection and clear Collect agent observability data.
For connections created before this capability was introduced, collection is disabled by default. Edit the connection and select Collect agent observability data to enable it.
Enabling collection doesn't create source telemetry. Configure the source platform first:
View activity
- Open the Microsoft 365 admin center.
- Open the Microsoft 365 agent registry.
- Select a synchronized third-party agent.
- Select the Activity tab.
Activity can take time to appear after an agent runs. The delay depends on the source platform. Anthropic Claude activity can take 5 to 10 minutes after an interaction.
Activity metrics
| Metric | Description |
|---|---|
| Sessions | Number of agent sessions in the reporting period. A conversational session begins after user interaction and a new session begins after 30 minutes of inactivity. An autonomous session is initiated by a trigger such as a schedule or another agent. |
| Exceptions | Number of sessions in the selected date range that had an error. |
| Runtime | Total time, in hours, that agents spend running during the reporting period. |
| Users | Not available for third-party agents when the source platform doesn't provide Microsoft Entra user identities. |
Understand platform differences
Third-party platforms use different identity systems and telemetry schemas. Consequently:
- Active user information might not be available.
- Session, invocation, runtime, exception, and tool-call metrics can remain available.
- Identity-based metrics are displayed as unavailable when the source platform doesn't provide the required identity signal.
Agent 365 doesn't infer missing identity information.
Data and privacy
The telemetry fields, retention period, residency, ingestion delay, and deletion behavior depend on the source platform and the Agent 365 experience. Confirm these values for each supported platform before communicating them to administrators.
Troubleshoot observability
| Symptom | Likely cause | Resolution |
|---|---|---|
| Agent appears but no activity is shown | Source telemetry isn't enabled or collection is disabled | Enable source telemetry and Collect agent observability data, then run the agent. |
| Activity is delayed | Source processing or ingestion is still running | Wait for the platform-specific processing interval and check again. |
| Users are unavailable | The source platform doesn't provide Microsoft Entra user identities | Use sessions, exceptions, runtime, and other available metrics instead. |
| Agent imports but telemetry is consistently empty | Connection scope doesn't match the deployed source environment | Verify the provider account, project, workspace, compartment, or region. |
For other connection and synchronization issues, see Troubleshoot connected platforms.