updated agent-connectors.md and whats-new.md

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

@@ -4,18 +4,18 @@ description: Register your MCP server in the Microsoft 365 app manifest to enabl
 #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.
 author: erikadoyle
 ms.author: edoyle
-ms.date: 12/15/2025
+ms.date: 01/27/2026
 ms.topic: how-to
 ms.subservice: m365apps
 ---
 
-# Register MCP servers as agent connectors for Microsoft 365 (preview)
+# Register MCP servers as agent connectors for Microsoft 365
 
 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.
 
 > [!NOTE]
 >
-> Agent Connectors are available in [public developer preview](../resources/dev-preview/developer-preview-intro.md).
+> Support for registering MCP servers as agent connectors is now generally available.
 
 Microsoft 365 agents use agent connectors to communicate with external systems. For MCP servers, the connector provides:
 
@@ -30,7 +30,7 @@ Once registered, your MCP server becomes available to any Microsoft 365 agent ca
 
 Before you begin, ensure you have:
 
-- A test tenant [enabled with Teams public preview](/microsoftteams/public-preview-doc-updates) features (for testing your MCP integration with Teams Channel Agent)
+- A test tenant (for testing your MCP integration with Teams Channel Agent)
 - A working MCP server with a secure public endpoint
 - Authentication credentials (OAuth configuration or API key)
 
@@ -42,12 +42,12 @@ First, declare your MCP server in the [agentConnectors](/microsoft-365/extensibi
 
 2. Locate or create the root-level `agentConnectors` array.
 
-3. Add a new connector object with a unique `id`, display name, and description:
+3. Add a new connector object with a unique `id`, `display name`, and `description`:
 
 ````json
 {
-  "$schema": "https://developer.microsoft.com/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json",
-  "manifestVersion": "devPreview",
+  "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.25/MicrosoftTeams.schema.json",
+  "manifestVersion": "v1.25",
   ...
     "agentConnectors": [
       {
@@ -67,21 +67,21 @@ First, declare your MCP server in the [agentConnectors](/microsoft-365/extensibi
 
 Each connector must have a unique `id` that distinguishes it from other connectors in your manifest. The `toolSource` object must include exactly one of `remoteMcpServer`, `localMcpServer`, or `plugin`.
 
-For MCP servers, use **remoteMcpServer** unless your server runs locally within the Teams client environment (advanced scenarios).
+For MCP servers, use `remoteMcpServer` unless your server runs locally within the Teams client environment (advanced scenarios).
 
 ## Configure the remote MCP server endpoint
 
 Define how Microsoft 365 connects to your MCP server using the `remoteMcpServer` object.
 
 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:
 
-````json
-"toolSource": {
-  "remoteMcpServer": {
-    "endpoint": "https://mcp.mycompany.com"
-  }
-}
-````
+    ````json
+    "toolSource": {
+      "remoteMcpServer": {
+        "endpoint": "https://mcp.mycompany.com"
+      }
+    }
+    ````
 
 2. Ensure your endpoint uses HTTPS (for HTTP connections) or WSS (for WebSocket connections).
 
@@ -183,8 +183,8 @@ The following is an example of a complete agent connector configuration:
 
 ```json
 {
-  "$schema": "https://developer.microsoft.com/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json",
-  "manifestVersion": "devPreview",
+  "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.25/MicrosoftTeams.schema.json",
+  "manifestVersion": "v1.25",
   ...
   "agentConnectors": [
     {

msteams-platform/whats-new.md

@@ -2,7 +2,7 @@
 title: What's New for Developers in Teams
 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.
 ms.topic: reference
-ms.date: 10/15/2025
+ms.date: 01/27/2026
 ms.localizationpriority: high
 zone_pivot_groups: What-new-features
 ---
@@ -36,13 +36,9 @@ Discover Microsoft Teams platform features that are generally available (GA). Yo
 
 Teams platform features that are available to all app developers.</br>
 
-**2025 November**
+**2026 January**
 
-* ***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)
-
-* ***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)
-
-* ***November 19, 2025***: [Microsoft Entra ID authentication for bots is now available in group scope.](bots/how-to/authentication/bot-sso-overview.md)
+* ***January 27, 2026***: [You can now register MCP servers as agent connectors for Microsoft 365](m365-apps/agent-connectors.md).
 
 :::column-end:::
 :::row-end:::
@@ -56,6 +52,9 @@ Teams platform features that are available to all app developers.</br>
 
 | **Date** | **Update** | **Find here** |
 | -------- | --------- | ----------------|
+| 21/11/2025 | Use the Performance Report tool to evaluate the efficiency of your web and tab apps on mobile. | Add Teams app capabilities > Resources > Best practices for Teams mobile app > [Calculate performance metrics for apps](resources/teams-mobile-best-practices.md#calculate-performance-metrics-for-apps)
+| 19/11/2025 | Create and manage agent identities for your agent. | Tools and SDKs > Tools > Developer Portal for Teams > Manage your apps in Developer Portal > Use tools to create app features > [Agent Identity Blueprint](concepts/build-and-test/manage-your-apps-in-developer-portal.md#agent-identity-blueprint)
+| 19/11/2025 | Microsoft Entra ID authentication for bots is now available in group scope | Add Authentication > Enable SSO for bot and message extension app using Entra ID > [Overview](bots/how-to/authentication/bot-sso-overview.md)
 |06/11/2025 | Teams AI library v2 has been renamed to *Teams SDK*. | [Teams SDK](/microsoftteams/platform/teams-ai-library/)
 |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)
 | 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) |