Starting today, the preview of Feedback for Microsoft Teams, a new community feedback experience from Microsoft, is available. Built on Dynamics 365 Customer Service, Feedback continues our dedicatio...
Updated Oct 28, 2021
Version 5.0
Blog Post
Title:
Increase Microsoft Teams Group Chat member limit from 250 to 400 (with performance guardrails)
Summary
Please increase the maximum number of participants in a Teams Group Chat from 250 to 400 for our organization.
Organization & Context
- Tenant/Organization: [D.T.C. Enterprise PCL./IT Division]
- Contact person: Anuchyd Srithip, Network & Information Technology Division Manager ([email address removed for privacy reasons/E-Mail])
- Audience size: [400] participants in a single Group Chat
- Message volume: ~[1000] messages/day, with peaks during [8hours/workday เช่น incidents, maintenance windows, shift handover]
Current Constraints & Impact
- The 250-person hard cap in Group Chat forces us to split conversations into multiple rooms.
- This creates duplicated posts, missed messages, and complicates compliance/audit trails when decisions span multiple chats.
- Teams Channels are not a full substitute in our scenario: notification defaults and threaded UX don’t meet our real-time, linear chat needs.
Proposal
1) Raise the Group Chat cap to **400** participants.
2) Keep/extend large-chat guardrails to protect performance at scale:
- Continue disabling high-churn signals (typing indicators, read receipts) beyond a threshold.
- Suppress join/leave toasts; apply burst rate-limiting and priority delivery for critical posts.
- Optional “moderated/announcement” mode for owner-only posts when needed.
3) Provide admin policy controls:
- Tenant-level setting to choose the limit (250/300/400).
- Per-chat toggle to enable stricter guardrails for very large chats.
4) Allow starting a chat from DL/Mail-enabled Security/O365 Groups up to the new cap (today this respects the 250 cap).
Business Value & Success Criteria
- A single 400-person room with delivery latency and notification reliability comparable to today’s 250-person performance.
- Reduced duplicate posts and improved acknowledgment/traceability in time-critical operations.
We’re willing to pilot this with Microsoft, share telemetry (non-sensitive), and provide structured feedback from our users.
Thank you for considering this request.