Posted inMicrosoft 365 suite

MC1480873: Microsoft Agent 365 Adds Observability for Third‑Party Agents via Connected Platforms

5 minutesPosted inMicrosoft 365 suite
MWPRO IMPACT SCORE
OPERATIONAL IMPACT
49
0 25 50 75 100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsTenant AdminsSecurity TeamsIT ManagersService OwnersDevelopers
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The update shifts preview and GA dates by roughly one month and clarifies that the change enables unified observability for third-party AI agents in Agent 365. Admins need to review connected platform configurations, validate credentials, and understand new data collection options, but no immediate action is mandatory. End users will not see notable changes, as this concerns admin‑facing monitoring and control settings.
65
🛡️ Admin Impact
HIGH
20
👥 User Impact
LOW
45
⚡ Urgency
MEDIUM
55
🔧 Effort
HIGH
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Agent 365 will soon let you monitor agents from Amazon, Google, and Anthropic alongside Microsoft agents. It gives a single view of activity and errors across supported platforms.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Admins can enable the new observability setting on existing connections and should review platform permissions and telemetry setup.
📅

ROLLOUT TIMELINE

Upcoming:
Late Nov 2026

📢 Official Microsoft Message Center Announcement

(Updated) Connected Platforms – Agent 365 extends observability to third-party agents
Message ID: MC1480873 (Updated)

Updated October 6, 2026: We have updated the timeline and content. Thank you for your patience. 

[What and Why:]

Microsoft will roll out third-party agent observability in Microsoft Agent 365 to tenants. This lets you monitor the agents you sync from Amazon Bedrock, Google Vertex AI, and Anthropic Claude through Connected platforms in the same place as your 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:]

Public Preview (Worldwide): We will begin rolling out on late October 2026 (previously late September) and expect to complete by late October 2026 (previously late September).

General Availability (Worldwide): We will begin rolling out late November 2026 (previously late October) and expect to complete by late November 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.

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1480873] Archive
Tooltip: View earlier revisions of this post

Share This Update
Tags: