Skip to content

Commit 16b10f3

Browse files
committed
updated agent-connectors.md and whats-new.md
1 parent e79b2d4 commit 16b10f3

File tree

2 files changed

+22
-23
lines changed

2 files changed

+22
-23
lines changed

msteams-platform/m365-apps/agent-connectors.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -4,18 +4,18 @@ description: Register your MCP server in the Microsoft 365 app manifest to enabl
44
#customer intent: As a developer, I want to register my MCP server as an agent connector so that Microsoft 365 agents can access my external tools and services.
55
author: erikadoyle
66
ms.author: edoyle
7-
ms.date: 12/15/2025
7+
ms.date: 01/23/2026
88
ms.topic: how-to
99
ms.subservice: m365apps
1010
---
1111

12-
# Register MCP servers as agent connectors for Microsoft 365 (preview)
12+
# Register MCP servers as agent connectors for Microsoft 365
1313

1414
Agents in Microsoft 365, such as [Channel Agent](/microsoftteams/set-up-channel-agent-teams) in Microsoft Teams, can connect to external systems through *agent connectors* declared in the app manifest. This article shows you how to register your remote Model Context Protocol (MCP) server in the Microsoft 365 app manifest, enabling Microsoft 365 agents to securely discover, select, and invoke MCP tools that your server exposes.
1515

1616
> [!NOTE]
1717
>
18-
> Agent Connectors are available in [public developer preview](../resources/dev-preview/developer-preview-intro.md).
18+
> Support for registering MCP servers as agent connectors is now generally available.
1919
2020
Microsoft 365 agents use agent connectors to communicate with external systems. For MCP servers, the connector provides:
2121

@@ -30,7 +30,7 @@ Once registered, your MCP server becomes available to any Microsoft 365 agent ca
3030

3131
Before you begin, ensure you have:
3232

33-
- A test tenant [enabled with Teams public preview](/microsoftteams/public-preview-doc-updates) features (for testing your MCP integration with Teams Channel Agent)
33+
- A test tenant (for testing your MCP integration with Teams Channel Agent)
3434
- A working MCP server with a secure public endpoint
3535
- Authentication credentials (OAuth configuration or API key)
3636

@@ -42,12 +42,12 @@ First, declare your MCP server in the [agentConnectors](/microsoft-365/extensibi
4242

4343
2. Locate or create the root-level `agentConnectors` array.
4444

45-
3. Add a new connector object with a unique `id`, display name, and description:
45+
3. Add a new connector object with a unique `id`, `display name`, and `description`:
4646

4747
````json
4848
{
49-
"$schema": "https://developer.microsoft.com/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json",
50-
"manifestVersion": "devPreview",
49+
"$schema": "https://developer.microsoft.com/json-schemas/teams/v1.25/MicrosoftTeams.schema.json",
50+
"manifestVersion": "v1.25",
5151
...
5252
"agentConnectors": [
5353
{
@@ -75,13 +75,13 @@ Define how Microsoft 365 connects to your MCP server using the `remoteMcpServer`
7575

7676
1. Within your connector's [toolSource](/microsoft-365/extensibility/schema/root-agent-connectors-tool-source?view=m365-app-prev&preserve-view=true), specify the `remoteMcpServer` endpoint:
7777

78-
````json
79-
"toolSource": {
80-
"remoteMcpServer": {
81-
"endpoint": "https://mcp.mycompany.com"
82-
}
83-
}
84-
````
78+
````json
79+
"toolSource": {
80+
"remoteMcpServer": {
81+
"endpoint": "https://mcp.mycompany.com"
82+
}
83+
}
84+
````
8585

8686
2. Ensure your endpoint uses HTTPS (for HTTP connections) or WSS (for WebSocket connections).
8787

@@ -183,8 +183,8 @@ The following is an example of a complete agent connector configuration:
183183

184184
```json
185185
{
186-
"$schema": "https://developer.microsoft.com/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json",
187-
"manifestVersion": "devPreview",
186+
"$schema": "https://developer.microsoft.com/json-schemas/teams/v1.25/MicrosoftTeams.schema.json",
187+
"manifestVersion": "v1.25",
188188
...
189189
"agentConnectors": [
190190
{

msteams-platform/whats-new.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: What's New for Developers in Teams
33
description: Learn about new Microsoft Teams developer features and updates to existing features, deprecation notes, and changes. Subscribe to the RSS feed for latest updates.
44
ms.topic: reference
5-
ms.date: 10/15/2025
5+
ms.date: 01/23/2026
66
ms.localizationpriority: high
77
zone_pivot_groups: What-new-features
88
---
@@ -36,13 +36,9 @@ Discover Microsoft Teams platform features that are generally available (GA). Yo
3636

3737
Teams platform features that are available to all app developers.</br>
3838

39-
**2025 November**
39+
**2026 January**
4040

41-
* ***November 21, 2025***: [Use the Performance Report tool to evaluate the efficiency of your web and tab apps on mobile.](resources/teams-mobile-best-practices.md#calculate-performance-metrics-for-apps)
42-
43-
* ***November 19, 2025***: [Create and manage agent identities for your agent.](concepts/build-and-test/manage-your-apps-in-developer-portal.md#agent-identity-blueprint)
44-
45-
* ***November 19, 2025***: [Microsoft Entra ID authentication for bots is now available in group scope.](bots/how-to/authentication/bot-sso-overview.md)
41+
* ***January 27, 2026***: [You can now register MCP servers as agent connectors for Microsoft 365](m365-apps/agent-connectors.md)
4642

4743
:::column-end:::
4844
:::row-end:::
@@ -56,6 +52,9 @@ Teams platform features that are available to all app developers.</br>
5652

5753
| **Date** | **Update** | **Find here** |
5854
| -------- | --------- | ----------------|
55+
| 21/11/2025 | Use the Performance Report tool to evaluate the efficiency of your web and tab apps on mobile. | [Calculate performance metrics for apps](resources/teams-mobile-best-practices.md#calculate-performance-metrics-for-apps)
56+
| 19/11/2025 | Create and manage agent identities for your agent. | [Agent Identity Blueprint](concepts/build-and-test/manage-your-apps-in-developer-portal.md#agent-identity-blueprint)
57+
| 19/11/2025 | Microsoft Entra ID authentication for bots is now available in group scope | [Enable SSO for your app](bots/how-to/authentication/bot-sso-overview.md)
5958
|06/11/2025 | Teams AI library v2 has been renamed to *Teams SDK*. | [Teams SDK](/microsoftteams/platform/teams-ai-library/)
6059
|15/10/2025 | The Microsoft Teams JavaScript client library (TeamsJS) supports app suspension for Teams apps extended to run across other Microsoft 365 applications. | Build tabs > Tab features > [App suspension for your tab app](tabs/how-to/app-caching.md)
6160
| 18/09/2025 | Teams AI library is now generally available for JavaScript and C#. It provides a simplified SDK, support for Model Context Protocol (MCP), Agent-to-Agent communication (A2A), and streamlined tools to enable developers to build intelligent agents for Teams | [Overview of Teams AI Library](/microsoftteams/platform/teams-ai-library/welcome) |

0 commit comments

Comments
 (0)