Lede
When you reschedule an interview in Zoho Recruit integrated with Microsoft Teams, the system sometimes creates new individual calendar events instead of updating the original meeting for all participants. That mismatch leaves duplicate invites and out-of-sync meeting links.
What it means — concrete explanation tied to the Zoho API surface
Zoho Recruit creates and manages Interview records and can push calendar events or meeting links to integrated calendar providers. With the Microsoft Teams integration (via Bookings or direct calendar sync), Zoho may create a fresh calendar event for each attendee instead of updating the single shared event tied to the original Interview record. This behavior appears in user reports inside Zoho community threads for Recruit rescheduling with Teams, where rescheduling produces new meetings rather than editing existing ones [1][2][6].
Common causes
- The Interview record lacks a persistent external event ID (the calendar event UID) so Recruit cannot locate and update the original Teams meeting [1].
- Using Zoho Bookings as an intermediary causes separate events per attendee if Bookings/Outlook sync settings are per-person instead of single-appointment mode [5][6].
- Calendar permissions or OAuth consent for the connected Microsoft account don’t allow event modification, so Zoho falls back to creating new events [1][6].
- Multiple calendar integrations (candidate uses Google, interviewer uses Outlook/Teams) create parallel events rather than a unified update [1].
How to fix it — priority steps
- Confirm integration path: check whether Recruit is calling Teams directly or through Zoho Bookings. In Recruit, open Settings > Integrations > Microsoft Teams / Zoho Bookings and note which connector is active [5][6].
- Verify stored external event ID: open the Interview record and look for a field like "Meeting ID" or "Calendar Event UID". If absent, the original event was not saved; delete duplicates and recreate the interview so Recruit can store the UID when creating the Teams event [1].
- Recheck OAuth scopes and account permissions in Azure/Outlook: ensure the service account/token granted to Zoho has event.ReadWrite and calendar consent so Zoho can update events rather than create new ones [1][6].
- Align calendar ownership: make the interviewer or a single service account the organizer of the Teams meeting so updates flow through one calendar instead of generating per-attendee events; update Bookings or Recruit organizer setting when creating the interview [5][6].
- Test with a single candidate and interviewer: reschedule and confirm the original Teams meeting receives an update (same event link and UID). If that works, apply the same pattern to live interviews.
- If you use Bookings, set Bookings > Services > "Calendar Sync" to create single meetings for all participants, and confirm Outlook/Teams sync is enabled for the Bookings account [5][6].
When to escalate
Open a Zoho Support ticket if, after verifying event UIDs, OAuth scopes, and Bookings settings, Recruit still creates separate meetings. Include a sample Interview record ID, timestamps, and any calendar event IDs so Support can trace API calls and server-side behavior [1][5].
[1]: Zoho Community posts reporting Interview rescheduling creating new meetings rather than updating existing events.
[5]: Zoho help article on automating interview scheduling using Zoho Bookings and how Bookings stores meeting URLs and syncs status.
[6]: Zoho Blog about Microsoft Teams and Zoho Bookings integration and calendar sync behavior.