Skip to content

Forwarded recurring meeting occurrences don't grant transcript access via onlineMeetings API #1035

@prekshivyas

Description

@prekshivyas

Documentation page - https://learn.microsoft.com/en-us/graph/api/resources/onlinemeeting?view=graph-rest-1.0

Issue

The documentation for onlineMeetings and meeting transcripts does not mention a behavioral difference between single meetings and recurring meeting occurrences when attendees are added via forwarding.

Observed behavior:

Scenario Forward + Accept Calendar shows attendee? onlineMeetings API access? Transcript access?
Single meeting ✅ 200 OK ✅ Works
Recurring occurrence ❌ 403 Forbidden ❌ Blocked
Scenario Forward + Accept Calendar shows attendee? onlineMeetings API access? Transcript access?
Single meeting ✅ 200 OK ✅ Works
Recurring occurrence ❌ 403 Forbidden ❌ Blocked

When a single occurrence of a recurring meeting is forwarded to a new attendee:

  • The attendee appears on the calendar event for that occurrence
  • But the onlineMeetings resource does not reflect them as a participant
  • GET /me/onlineMeetings?$filter=JoinWebUrl eq '...' returns 403 with code 3003
  • This blocks all downstream operations (transcript retrieval, meeting metadata, etc.)

Request

Please either:

  1. Document this limitation in the onlineMeetings and/or callTranscript documentation, so developers can inform users about the constraint
  2. Or confirm this is unintended behavior so it can be tracked as a bug

Impact: This affects enterprise applications that access meeting transcripts programmatically. Forwarding individual occurrences of recurring meetings is a very common pattern in organizations.

Reproduction steps: See Microsoft Q&A post (to be linked after filing).

API version: v1.0 Permissions: OnlineMeetings.Read, OnlineMeetingTranscript.Read.All (delegated)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions