Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 270/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 09:12 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Channel Agent feature updates

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
557555

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 7 Apr 2026 late March 2026 → mid-April 2026

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured
Updated April 7, 2026: We have updated the timeline. Thank you for your patience.  Introduction We’re introducing new capabilities for Channel Agent in Microsoft Teams to improve how agents support collaboration within channels. These updates enhance agent welcome messages, give users more control over agent creation, and expand agent actions within channels to help teams work more efficiently. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android and is associated with Roadmap ID 557555. When this will happen: Targeted Release: Rolling out early March 2026 and completing by mid-April 2026 (previously late March). How this affects your organization: Who is affected: Microsoft Teams users who create or interact with Channel Agents Admins managing Teams preview features A Microsoft 365 Copilot license is required to use this feature. What will happen: New Channel Agents generate customized welcome messages based on channel context. Users can disable automatic Channel Agent creation during team or channel setup. Improved scheduling suggestions using updated calendar logic. Users can ask the agent to add members to a channel with a simple prompt such as “@agent add John Doe to this channel.” Channel Agents can post messages directly to a channel. What you can do to prepare: No action is required if your organization is not opted into Targeted Release. Ensure your tenant is opted into Targeted Release if you want to receive this update earlier. Confirm Channel Agent is enabled for your tenant. Notify helpdesk staff of the new behaviors. Learn more: Get started with Channel Agent for Teams channels | Microsoft Support Set up a Channel Agent for Microsoft Teams - Microsoft Teams | Microsoft Learn Compliance considerations: Channel Agent can access channel roster data to support member management actions. No other compliance impacts have been identified.

What changed

Between archive captures, newest first
    • Tags Feature update, User impact, Admin impact → Updated message, Feature update, User impact, Admin impact

    Updated April 7, 2026: We have updated the timeline. Thank you for your patience.  Introduction We’re introducing new capabilities for Channel Agent in Microsoft Teams to … will happen: Targeted Release: Rolling out early March 2026 and completing by mid-April 2026 (previously late March 2026.March). How this affects your organization: Who is affected: Microsoft Teams users who …

  1. · first version seen

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 2 linked pages have not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 09:12 UTC · 270 of 272 readable · 269 fully read · documentation 469/469 current