Viva Copilot Analytics Adds Bedrock, Vertex AI and Claude Agent Reporting in October 2026

The roadmap text is short. It doesn't name the third-party platforms, list the metrics, or say what admins have to set up. A related Message Center post, MC1486287, fills in much of that.

Which platforms are covered​

According to a republished copy of MC1486287, Microsoft Viva Copilot Analytics will expand Agent365 dashboard reporting to include agents from Amazon Bedrock, Google Vertex AI, and Anthropic Claude starting mid-October 2026. These agents come in through Agent 365. The notice says business leaders, adoption specialists, and administrators will gain additional observability insights for agents synchronized from Amazon Bedrock, Google Vertex AI, and Anthropic Claude through the Connected platforms capability in Agent365.

One detail is worth noticing. Microsoft's Agent 365 documentation on third-party agent observability, last updated September 29, 2026, lists four supported platforms:

Salesforce Agentforce shows up in the Agent 365 observability docs but not in the Viva dashboard notice as reported. If you run Agentforce agents, don't assume they will appear in the Viva dashboard at launch. They may show up in the Agent 365 admin views and still be missing from Viva. Check what your tenant actually displays after rollout. The Agent 365 docs also say plainly that observability availability and metric coverage vary by platform.

Section summary: Expect Bedrock, Vertex AI and Claude agents in the Viva dashboard from mid-October. Agentforce is supported in Agent 365 observability but isn't named for this Viva expansion.

The catch: no user-level numbers​

Third-party agents won't get the same metrics as Copilot agents. The notice says because supported third-party platforms do not provide Microsoft Entra user identities, user-based metrics such as Active users and Returning users will not be available for these agents.

The Agent 365 documentation explains the same limit. Third-party platforms use different identity systems and telemetry formats, so active-user information may be missing. Session, invocation, runtime, exception and tool-call metrics can still come through. Microsoft also says Agent 365 doesn't infer missing identity data. That's the right call. Guessing who used an agent from partial signals would be worse than showing a blank.

For metrics that do come through, the Agent 365 docs define them this way:

• Sessions: a conversational session starts with user interaction, and a new one begins after 30 minutes of inactivity. Autonomous sessions are started by a trigger, such as a schedule or another agent.
• Exceptions: sessions in the selected date range that hit an error.
• Runtime: total hours agents spent running during the reporting period.

Here's what that means in practice. A Claude agent that pulls invoice data overnight on a schedule can show up with healthy session and runtime numbers and an empty user count. A Copilot Studio agent with similar workload will show actual people. The dashboard puts them side by side, but a session from one platform isn't the same thing as a user from another. If leadership ranks agents by active users, every third-party agent will look like it has zero users, because the data was never available.

Section summary: Third-party agents will report sessions, runtime and exceptions. They won't report active or returning users, so be careful when comparing them with Microsoft agents.

What admins need to set up before mid-October​

The Viva roadmap item doesn't describe setup, but MC1486287 says administrators must enable observability data collection for reporting. Its pre-rollout checklist asks admins to confirm that administrators have enabled collection of agent observability data when creating or editing connections to supported third-party platforms.

Microsoft's Agent 365 docs explain how that setting works. Agent 365 itself is in the Frontier preview program there.

1. Check how old each connection is. Observability collection is on by default for new connections. For connections created before the feature existed, it's off by default.
2. Turn on collection for older connections. Edit the connection and select Collect agent observability data.
3. Set up telemetry on the source platform. Turning on collection in Microsoft 365 doesn't create telemetry at the source. Bedrock, Vertex AI or Claude has to be emitting it first.
4. Confirm data is arriving. In the Microsoft 365 admin center, open the Microsoft 365 agent registry, select a synchronized third-party agent, and open the Activity tab.
5. Allow for delay. Microsoft says activity can take time to appear, depending on the platform. Anthropic Claude activity can take 5 to 10 minutes after an interaction.

These steps come from the Agent 365 observability documentation. Microsoft hasn't published separate Viva-specific steps for this expansion. Still, if third-party agents show no activity in Agent 365, they almost certainly won't show anything useful in Viva either.

Common problems and fixes​

Microsoft's Agent 365 troubleshooting guidance covers the usual failures:

• The agent appears but shows no activity: source telemetry isn't enabled, or collection is turned off. Enable both, then run the agent.
• Activity is late: the source platform is still processing. Wait for its usual interval.
• Users show as unavailable: this is expected when the platform doesn't supply Entra identities. Use sessions, runtime and exceptions instead.
• The agent imports but telemetry stays empty: the connection scope probably doesn't match where the agent is deployed. Check the provider account, project, workspace, compartment or region.

Section summary: Older connections need collection turned on by hand. Source-side telemetry must be configured separately. Confirm activity in the agent registry before you expect it in Viva.

Who sees the data, and the controls you already have​

This expansion builds on dashboard features Microsoft has added over the past year. Customers can now access their Agent 365 data through the Agent Dashboard in Copilot Analytics (Insights), enabling leaders to understand activity across all agents registered through Agent 365. Microsoft then gave managers access through MC1431365. This update gives managers the same core Agent 365 visibility that is being made available to leaders and delegates, scoped to the teams they can view. A separate roadmap item, 570847, adds value insights showing the estimated assisted hours agents provide and the types of work contributing to that value. Microsoft hasn't said whether those value estimates will cover third-party agents.

So more people may see third-party agent data than you expect, including managers who've never logged into an AWS console. Microsoft's Viva Insights admin documentation describes the controls you have now:

• Turning the dashboard on or off: the Agent Dashboard is on by default within the Viva Insights web app. AI Administrators can turn it on or off at tenant, group or user level using Viva Feature Access Management (VFAM). The Viva Insights web app control and the Agent Dashboard control must both be enabled.
• Which agent types are included: By default, the Agent 365 Dashboard includes all agents. Admins can limit reporting to agents available to everyone in the organization. Public agents include those created by Microsoft and third parties. The PowerShell feature ID is Agent365DashboardNonPublicAgentsVisibility.
• Privacy thresholds: group-level metrics require a minimum group size, which defaults to 10 employees and can be lowered to no fewer than five. A unified exclusion list can also hide specific users from aggregate insights.

Microsoft hasn't confirmed whether the public/non-public filter or the group-size threshold will work the same way for agents brought in from Bedrock or Vertex AI. Check after rollout instead of assuming.

Eligibility still applies. Microsoft's Copilot Analytics overview says the Agent Dashboard is available to customers with at least 50 Microsoft Copilot licenses and some agent activity. The admin docs also still describe the Agent Dashboard as a public preview feature that allows personal data processing under the preview terms.

Why this matters​

Few large organizations run every agent on one vendor's platform. Data science teams may build on Vertex AI, operations may run Bedrock agents, and developers may use Claude. Until now, Viva's dashboard only showed Microsoft agents. Third-party agents were real, but leaders and adoption teams couldn't see them in Viva.

Microsoft's competitors have their own agent dashboards. Microsoft is betting that the place you already govern Microsoft 365 is the right place to view everything else. That pitch is credible, but only as good as the telemetry other platforms send. Without Entra identities, Microsoft can count sessions but can't say who ran them. "Expanded coverage" really means expanded operational visibility, not one consistent view of every user and agent.

There's a governance angle too. Agents that run on outside clouds still touch company data. Getting even session counts and error rates in front of business leaders helps reduce shadow AI, the agents nobody in IT knows about.

Bottom line for IT​

• Dates: the roadmap says preview and GA in October 2026. The related notice says rollout starts mid-October. Treat both as planned dates, and remember the roadmap item is still "In development."
• Platforms: Amazon Bedrock, Google Vertex AI and Anthropic Claude are named. Salesforce Agentforce is supported in Agent 365 observability but isn't named for this Viva expansion.
• Before rollout: turn on Collect agent observability data on older connections, configure telemetry at the source, and confirm the Activity tab shows data.
• Brief your stakeholders: third-party agents won't show active or returning users. A zero there means the data isn't available, not that nobody uses the agent.
• Review access: check VFAM settings now, since managers as well as leaders can see Agent 365 data.

When third-party agents start appearing next to your Copilot agents, compare them on sessions, runtime and errors, not on user counts.