MC1388719: Microsoft Teams Adds Granular Channel Notification Controls

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
38
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

Teams AdminsMicrosoft 365 AdminsIT ManagersService OwnersEnd Users
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The rollout timeline for Teams granular channel notification settings has shifted by roughly a month. The change remains enabled by default with no required admin actions, but admins may need to update helpdesk and training materials. User impact is moderate as notification presets and customisation options change the experience, although defaults remain unchanged.
35
🛡️ Admin Impact
45
👥 User Impact
40
⚡ Urgency
30
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams now includes preset channel notification options so users can manage alerts more precisely and reduce unnecessary noise.
👥

END USERS

Users will see new notification presets and can customise how channel messages trigger alerts.
🛡️

IT ADMINS

Inform support teams and update any internal documentation covering Teams notifications.
📅

ROLLOUT TIMELINE

Upcoming:
November 2026

📢 Official Microsoft Message Center Announcement


(Updated) Microsoft Teams: Granular channel notification settings
Message ID: MC1388719 (Updated)

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

[What and why]

Users will now be able to control their channel notification settings using three presets: All new messages, Mentions and replies, and Mute. Users can further customize the selected preset to manage notifications for unfollowed threads, tag mentions, channel mentions, and team mentions within each channel, as well as control banner notifications for the channel

This gives users more control over what is important in each channel, leading to an improved triaging experience and reduced noise.

This message is associated with Microsoft 365 Roadmap ID 565132.

[Rollout schedule]

  • General Availability
    • Targeted release: Rollout will begin in early October 2026 (previously late September) and is expected to complete in early October 2026 (previously mid-August).
    • Worldwide: Rollout will begin in early November 2026 (previously early October) and is expected to complete in mid-November 2026 (previously mid-October).
    • GCC and GCC High: Rollout will begin in mid-November 2026 (previously mid-October) and is expected to complete in late November 2026 (previously late October).
    • DoD: Rollout will begin in late November 2026 (previously late October) and is expected to complete by mid-December 2026 (previously mid-November).

[Impact on your organization]

Who is affected

  •  Users in GCC, GCC High, and DoD environments using Microsoft Teams channels

Platforms and services

  • Microsoft Teams across desktop, web, and mobile
  • Windows, Mac, iOS, Android

What will happen

  • Users will see new preset channel notification options:
    • All new messages
    • Mentions and replies
    • Mute
  • Users can customize each preset to manage:
    • Unfollowed threads
    • Tag mentions
    • Channel mentions
    • Team mentions
  • Existing notification behavior remains unchanged unless users modify their settings.
  • The feature is enabled by default for all users.
  • No changes are required to existing admin settings or policies.

[Action required]

No action is required.

Recommendations:

  • Inform helpdesk teams about this change, as users may have questions about updated notification behavior.
  • Update internal documentation or training materials if you reference Teams notifications.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Source: Microsoft Message Center • Analysed by MWPro

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

Share This Update