Teams co-organizers can’t access meeting engagement data: a gap for centrally managed meetings

Hi everyone,

We’ve run into what seems to be a gap in the Microsoft Teams co-organizer model while working on moving our enterprise virtual learning delivery from a dedicated virtual-classroom platform to Teams.

Our requirement is fairly straightforward: we run a large number of centrally administered learning sessions, with multiple facilitators who need to be able to step in and deliver a session when required.

The model we’d ideally use is:

• A shared calendar/mailbox for central visibility and administration.
• The relevant facilitator group automatically added as co-organizers.
• Facilitators can run the session, manage participants, breakout rooms, recordings, etc.
• Co-organizers can access the standard attendance report after the session.

This gets us almost everything we need.

The gap is the richer meeting engagement data.

Teams provides engagement information such as reactions, raised hands, camera usage and other engagement measures, but this appears to remain restricted to the meeting organizer, rather than being available to co-organizers.

That creates an awkward problem for centrally administered meeting scenarios. A co-organizer can be trusted to run the meeting and access its attendance reporting, but not access all of the post-meeting engagement reporting.

It becomes particularly problematic if a shared mailbox is the meeting organizer, because there may be no actual person able to retrieve that organizer-only data.

What I’d love to see

I’d like Microsoft to allow explicitly assigned co-organizers to access the same post-meeting engagement data as the organizer.

I’ve submitted this as a feature request here, which I'd love for you to vote for at the link below please if you think it would help you too:

https://feedbackportal.microsoft.com/feedback/idea/28182268-f7d9-f111-bda3-6045bd78a526

I’d be really interested to hear:

1. Is anyone else running centrally managed Teams meetings at scale and hitting this same limitation?
2. Have you found another supported way of retrieving this engagement data?
3. If this would be useful for your organization too, would you consider voting/commenting on the feature request?

It feels like a relatively small permissions gap in an otherwise very capable co-organizer model, but closing it would make a big difference for centrally managed training, events and similar enterprise scenarios.

Thanks!