The “Meeting Link Migration Task" can be misleading and could use some expansion on what it does.
n/a
The Meeting Link Migration Task is a specialized process in On Demand Migration for Exchange (ODME) that automatically detects, updates, and rewrites Teams and Skype meeting links embedded in users’ calendar items when migrating mailboxes between Microsoft 365 tenants.
In short:
It ensures migrated calendar meetings in the target tenant link to the correct Teams environment — not the old (source) tenant.
When users are migrated from one Microsoft 365 tenant to another, existing meeting invites often contain Teams or Skype meeting URLs that point to the source tenant (e.g., https://teams.microsoft.com/l/meetup-join/...sourceTenantID...).
If not corrected, these links will:
Stop working post-migration
Redirect to the old tenant (where the user no longer exists)
Cause confusion for attendees who join meetings via those links
The Meeting Link Migration Task fixes that automatically.
Calendar Scan:
The task scans calendar items in each mailbox during or after migration.
Link Detection:
It identifies URLs associated with:
Microsoft Teams meetings
Skype for Business meetings (legacy)
Rewriting:
Each detected meeting link is replaced with a new link generated in the target tenant, preserving:
Meeting date/time
Attendees
Subject and notes
Organizer
Synchronization:
Updated calendar items are synced back to the target mailbox, ensuring users and invitees receive valid links.
Seamless continuity for end users — no broken meeting links
Prevents users from needing to manually recreate recurring meetings
Reduces post-migration support tickets
Supports both Teams and Skype link structures
The task requires calendar migration to be included in the migration plan.
Modern authentication consent must be granted so ODM can access and modify calendar data.
Only meetings organized by the migrated user can have links rewritten; meetings organized by others are not modified.
The rewritten meetings will appear as if created in the new tenant’s Teams environment.
It can be run manually after mailbox migration or automatically as part of a workflow.