We organize a Teams meeting with about twenty people, the session ends, and the question arises: who was actually connected? The stakes are not trivial. Validating a quorum in a meeting, justifying mandatory training, or simply following up with absentees requires knowing precisely who participated. Identifying participants in a Teams meeting relies on several complementary mechanisms, and not all are accessible in the same way depending on your role in the meeting.
Teams Attendance Report: What the Organizer Really Gets
The “Participants” sidebar displayed during the meeting provides a real-time overview, but it is the attendance report that constitutes the usable record. The organizer accesses this report directly from the meeting menu bar, via the dedicated icon in the participants panel.
Read also : How to Align and Organize Your Data Effectively in Excel
This file, downloadable in CSV format, contains the name of each participant, their email address, as well as their entry and exit times. It can be opened in Excel to filter, sort, or cross-reference with a list of registrants. Only the meeting organizer can download this report, which poses a concrete problem when the meeting was created by an assistant or a shared account.
A point often overlooked: according to the official documentation, it is currently only possible to download this list during the meeting itself. If the session is closed without retrieving it, the situation becomes complicated. The report can then be found in the Teams calendar, in the details of the past meeting, but feedback on this point varies depending on the versions of Teams used (classic or new app).
Read also : How to log in to your teacher account in the Créteil academy: steps and tips
For those who wish to delve deeper into the different methods of accessing this information, it is possible to learn more on Mobile Junky where the procedures are detailed step by step.
Cross-Referencing Outlook and Teams for a Reliable List of Participants
The live meeting panel only shows the people connected at that moment. For a complete view (invited, excused, actually present), we need to cross-reference two sources.
On the Outlook Side: Responses to Invitations
When scheduling a Teams meeting, the invitation goes through Outlook. Each recipient can respond: accepted, tentative, declined. These responses are displayed in the Outlook event tracking, distinguishing between mandatory and optional participants.
This first layer of information provides the list of people expected to be present. It does not prove that they connected, but it provides a starting reference.
On the Teams Side: Actual Presence
The CSV report downloaded during the meeting provides the actual attendance. By comparing the two lists, we obtain three clear categories:
- Participants who accepted the invitation and actually connected, with their precise timings
- People who accepted but never connected, whom we can follow up with specifically
- Uninvited participants who joined the meeting via a forwarded link or sharing, which frequently happens in large organizations
The combination of Outlook and Teams provides a much more reliable view than the live panel alone. For regulatory training or formal meetings, this cross-referencing becomes the standard method.
Display Restrictions and GDPR Compliance on Attendance Data
It is often assumed that the full name and email of each participant are always visible. This is not systematic. In certain organizations, particularly in healthcare, education, or the public sector, IT administrators restrict the display of certain information in Teams.
Specifically, a host may see partially masked names or removed photos in the participants panel. These anonymization policies, implemented in recent years by data protection officers, aim to limit the unnecessary dissemination of personal information.
The attendance report itself contains personal data under GDPR: name, email, connection times. Compliance specialists remind us that this data must be covered by a legal basis (legitimate interest, legal obligation, etc.) and that a retention period must be defined.
- Clearly define why we collect the attendance list (training obligation, statutory quorum, educational follow-up)
- Inform participants that their presence will be recorded, ideally in the body of the invitation
- Delete the CSV file once the objective is achieved, respecting the retention period set by your internal policy
Keeping an attendance report without a documented purpose poses a risk of non-compliance. This point is rarely addressed in technical tutorials, but it conditions the very legitimacy of identifying participants.
Practical Cases: General Assembly, Training, and Recurring Meeting
The usefulness of attendance tracking varies depending on the context. Here are three situations where the method differs.
Assembly with Mandatory Quorum
For a general assembly held via videoconference, the CSV report serves as proof of attendance. It extracts the number of participants connected at the time of the vote, with the exact time. The file can be attached to the minutes. In this case, downloading the report before the end of the meeting is a non-negotiable precaution.
Mandatory Training with Attendance Sheet
The Teams attendance report replaces the paper attendance sheet, provided it can be proven that the identified person is indeed the one who connected. Authentication via the professional Microsoft account offers this guarantee. A participant connected with a generic account (“meeting-room-3”) makes the report unusable for individual attendance tracking.
Weekly Recurring Meeting
For a meeting that occurs every week, each occurrence generates its own report. They can be consolidated in a spreadsheet to track attendance regularity over several weeks. This is a common practice among managers who want to objectify participation without monitoring in real-time.
Identifying participants in Teams relies on a combination of tools (live panel, CSV report, Outlook tracking) and not on a single button. Retrieving the report during the session remains the safest reflex, as options for recovery afterward depend on the version of the application and the organization’s settings. As for the retention of this data, it involves both technical and regulatory compliance aspects.