Conversations involving multiple participants, allowing collaboration and information sharing in Teams
Thank you for checking on my ticket.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I manage a Teams group chat (business tenant, 64 members across ~37 external domains) that's experienced repeated, unexplained removals of the same handful of external members over nearly two months — July 1, 13, 14, 16, 20, 22, 23, and 24.
Key details that rule out the usual explanations:
ChatMemberRemoved returns zero results for these events, despite MemberAdded logging correctly for the same chat.I have an active Microsoft support ticket open on this, but it's been slow-moving. Posting here in case anyone's seen this specific pattern — a consistent small group getting silently ejected regardless of Guest/External status, chat-wide federation otherwise stable — rather than the more commonly reported "guest access breaks broadly" issue.
Happy to share screenshots of the activity log showing the unattributed removal pattern if useful.
Conversations involving multiple participants, allowing collaboration and information sharing in Teams
Thank you for checking on my ticket.
Dear @Claudia Catlett,
To ensure I understand your request correctly and to support you as effectively as possible, I need more specific information from you:
Could you share your ID ticket in private message?
Since this is a domain level, none of moderators could help you with this, I could only help you to check and push it faster.
As a moderator, I do not have the tools to investigate your specific account directly, as this is a support forum between users. Moderators and collaborators, including external Microsoft employees, may not directly intervene in the functionality of Microsoft products or access internal systems. Our role is limited to providing technical guidance on reported problems, requests, or ideas. However, I will do my best to guide you as clearly as possible.