Message Center

MC1480873Connected Platforms - Agent 365 extends observability to third-party agents

Summary

Microsoft Agent 365 now integrates observability for third-party agents from Amazon Bedrock Classic, AgentCore, Google Vertex AI, and Anthropic Claude Managed Agents into a unified experience. Administrators can monitor runs, sessions, tool calls, and exceptions across platforms. Rollout begins September 2026, with no action needed for existing connections unless observability is desired.

More information

What and Why:

With this Frontier launch, Microsoft Agent 365 brings activity from Amazon Bedrock Classic and AgentCore, Google Vertex AI, and Anthropic Claude Managed Agents (preview) into the same observability experience as Microsoft agents.

Administrators can see runs, sessions, tool calls, and exceptions on each agent’s Activity tab. The result: a more consistent way to understand agent usage and investigate issues across supported platforms without treating every environment as a separate monitoring exercise.

Rollout Schedule:

Targeted Release (Worldwide): We will begin rolling out on late September 2026 and expect to complete by late September 2026.

General Availability (Worldwide): We will begin rolling out on late October 2026 and expect to complete by Ignite 2026.

Impact on Your Organization:

Who is affected

Administrators using Microsoft Agent 365 and Connected platforms
Organizations synchronizing agents from Amazon Bedrock Classic, Amazon Bedrock AgentCore, Google Vertex AI, or Anthropic Claude Managed Agents (preview)

Platforms/Services

Microsoft Agent 365
Connected platforms
Amazon Bedrock Classic
Amazon Bedrock AgentCore
Google Vertex AI
Anthropic Claude Managed Agents (preview)

What will happen

Agent 365 can collect observability data from supported third-party agent platforms.
Collected activity appears on each synchronized agent's Activity tab.
Runs, sessions, tool calls, and exceptions are mapped to the Agent 365 observability model.
Existing connections continue syncing agents as they do today.
Collection remains disabled for existing connections until an administrator enables it.
A new Collect agent observability data setting is available when creating or editing a supported connection.
The setting is enabled by default for new connections.
Agent 365 reads activity using existing connection credentials and does not execute agents.
Third-party providers may charge for tracing, storage, logging, or query services.
The Users metric is unavailable for synchronized third-party agents because Microsoft Entra identities are not provided by supported platforms.

Action Required/Recommendations:

No action is required for existing connections.
Enable Collect agent observability data on existing connections if observability is desired.
Validate source platform permissions and telemetry configuration.
Clear the Collect agent observability data option during setup if collection is not desired for a new connection.

Platform Requirements

Amazon Bedrock Classic: Enable trace capture to Amazon S3 and grant read access to the activity bucket.
Amazon Bedrock AgentCore: Enable CloudWatch Transaction Search and grant access to query CloudWatch log groups.
Google Vertex AI: Assign required BigQuery, Monitoring, and Cloud Trace roles; enable APIs; enable telemetry collection and Trace Analytics BigQuery export.
Anthropic Claude Managed Agents (preview): No additional setup required.

Compliance considerations:

Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?	Yes. The feature uses AI/ML or agent capabilities with Microsoft 365 content, prompts, or service data as described in this message.
Does the change introduce or significantly modify any capability that enables users to automate workflows through AI or bot agents?	Yes. The feature introduces or updates agent-related AI capabilities as described in this message.
Does the change include an admin control and, can it be controlled through Entra ID group membership?	Yes. The feature includes or affects admin controls, policies, permissions, roles, authentication, or management settings as described in this message. Review the linked documentation or admin center controls for group-based configuration support.