Teams Participant was removed from the conversation by another participant.

Szunomár Péter 46 Reputation points

Hi All,

we are supporting the Teams in several educational environment. It often occurs, that a student removes an other from the meeting. As on the page [Dashboard\Users\<username>\Meeting\Session\Debug] seen in this situation: [Skype_ResultDetail=Participant was removed from the conversation by another participant.] Ok. But who is this "another participant"? Is it a log anywhere to find it?

Another game is to muting others. Is it logged anywhere, who muted the other?


Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
9,573 questions
0 comments No comments
{count} votes

Accepted answer
  1. JimmyYang-MSFT 50,361 Reputation points Microsoft Vendor

    @Szunomár Péter

    Currently, it is not feasible to find out who removes or mutes others in Teams meeting.

    As you know, attendees have no permission to remove or mute other participants. So, to prevent this situation, it recommends you make students as attendees in Teams meeting.

    As michev said, log files to monitor participants activities during Teams meeting is not supported.

    I found a feedback in Teams UserVoice about this feature. You could vote for it here:

    Microsoft will always focus on customer’s feedback and experience. Some new features would be added to the services based on customers' feedback in the future, and your good ideas will be very helpful for them to improve the service.

    Your time, understanding and cooperation will be highly appreciated.

    If the response is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Vasil Michev 99,941 Reputation points MVP

    Audit log improvements are coming, which should address such scenarios. But you can actually prevent this from happening right now by adjusting the roles within a given meeting: