Additional features, settings, or issues not covered by specific Microsoft Teams categories
The message can occur even when the meeting organizer can still open the meeting and select the attendance link. Based on the available guidance, the most likely causes are these:
- The report was never generated for that meeting Attendance reports depend on the meeting’s attendance-report setting and the organizer’s meeting policy. If Allow attendance report was off for the meeting, or the organizer’s Teams meeting policy had attendance and engagement reports turned Off, the report would not be available.
- The report is being accessed long after the meeting date A similar reported case for older meetings showed the same message for meetings that were a month or more old. In that case, the report later became accessible again without user action, which points to a possible service-side issue rather than a user permission problem.
- Meeting type limitations Attendance reports aren’t supported for instant channel meetings. There are also known limitations for some channel-meeting scenarios, such as only the second meeting in the same channel conversation having a report, and co-organizers not being able to access attendance reports for channel meetings.
- System-side delay or issue Official guidance confirms that attendance data can take time to appear after a meeting ends. Although that normally applies shortly after the meeting, the older-meeting example indicates that backend or service issues can also produce the same message.
What to check:
- In the meeting’s Meeting options, confirm Allow attendance report was enabled.
- In Teams admin center > Meetings > Meeting policies > assigned policy for the organizer, verify Attendance and engagement report is not set to Off.
- Confirm the meeting was a scheduled meeting or event, not an unsupported instant channel meeting.
- Try opening the report from both places supported for organizers after a meeting ends:
- the meeting Attendance tab in the invite
- the meeting chat
- If the meeting is part of a recurring series, be aware that some reported behavior for older meetings and series instances has been inconsistent.
What the available evidence suggests for this case:
- Since the meeting organizer can access the meeting and click the attendance link, this is less likely to be a basic permission issue.
- Because the meeting occurred in November 2025 and the error is still shown, this is more consistent with either:
- the report not having been generated because of meeting/policy configuration at the time of the meeting, or
- a service-side issue affecting older attendance reports.
If the policy and meeting option were enabled and the meeting type was supported, the remaining explanation from the available guidance is a system issue rather than an organizer action problem.
References: