How to Delete a Meeting Created by a Deleted User

When someone leaves an organization and their account gets deleted, the meetings they scheduled don't automatically disappear. Calendar entries, recurring sessions, and video conference links can linger — cluttering shared calendars, confusing attendees, and sometimes still sending reminders. Here's what's actually happening under the hood, and how administrators and users can clean things up.

Why Meetings Orphan After Account Deletion

Most scheduling and productivity platforms tie meetings to the organizer's account. When that account is deleted, the meeting becomes an orphaned event — it still exists in the system's database, but the owner no longer does.

The platform's behavior at that point depends heavily on how the deletion was handled:

  • Immediate hard delete — The account and its data are permanently removed. Orphaned meetings may still appear on attendees' calendars but can no longer be modified through normal channels.
  • Soft delete or deactivation — The account is disabled but data is retained for a grace period. Admins typically retain edit access during this window.
  • License reassignment — Some platforms allow an admin to transfer ownership of events before or after deletion.

Understanding which scenario applies to your environment determines which fix is actually available to you.

Platform-by-Platform Differences 🗓️

Different tools handle orphaned meetings very differently. There's no universal fix — your approach depends entirely on which platform you're working in.

Microsoft 365 / Outlook / Teams

In Microsoft 365 environments, an Exchange Online mailbox is tied to each user. When the account is deleted, the mailbox enters a soft-deleted state for a configurable retention period (often 30 days by default).

During this window, an administrator can:

  • Restore the mailbox temporarily, log in, and delete the meetings manually
  • Use Exchange Admin Center (EAC) or PowerShell to access and manage the mailbox contents
  • Use the Remove-CalendarEvents cmdlet in Exchange PowerShell to remove events

After the retention window closes and the mailbox is permanently purged, the organizer's calendar entries are gone from their side — but attendees may still have copies on their own calendars that require manual deletion.

For Teams meetings specifically, the meeting link and recording access may also need to be revoked separately through the Teams Admin Center.

Google Workspace

Google Workspace gives admins a transfer window before permanent deletion. Using the Admin Console, an admin can:

  • Transfer the deleted user's Google Calendar data to another account before finalizing deletion
  • Use Google Vault (if licensed) to search, export, or manage the user's data
  • Access the deleted user's Drive and Calendar through admin delegation for a limited period

Once that window closes and the account is fully removed, meetings on attendees' calendars are effectively stranded. Attendees must delete those events individually from their own calendars.

Zoom

Zoom meetings are tied to a host's account. When the host is deleted:

  • Scheduled meetings tied to that host's Personal Meeting ID (PMI) are typically removed automatically
  • Non-recurring meetings may still appear in attendees' calendar apps if the invite was accepted before deletion
  • Recurring meetings require admin action — a Zoom Admin can reassign or delete those meetings through the Zoom Admin Portal before deleting the user

Zoom strongly recommends reassigning or ending active meetings before deleting the host account, as recovery options afterward are limited.

Other Platforms (Slack, Calendly, HubSpot, etc.)

The same principle applies across most scheduling tools: act before the deletion is finalized. Most platforms offer a transfer or data export step during the offboarding flow that's easy to skip in a hurry.

The Key Variables That Affect What's Possible

Whether you can actually delete or clean up orphaned meetings comes down to a few factors:

VariableWhy It Matters
Admin access levelStandard users can't touch another user's calendar data; admins often can
Deletion typeSoft delete leaves options open; hard delete closes most of them
Time since deletionRetention periods are finite — the window closes
Platform and licensing tierSome recovery tools (like Google Vault) require specific license tiers
Meeting typeOne-time vs. recurring meetings may behave differently
Calendar integrationMeetings synced to external calendars (Outlook, Google) may need to be removed from both systems

What Attendees Can Do on Their End

Even if the meeting can't be deleted from the organizer's side, every attendee can remove it from their own calendar. This won't cancel the event for others, but it clears up individual calendars and stops reminders.

In most calendar apps:

  • Right-click the event → Delete or Remove from Calendar
  • If it was a recurring series, you'll typically be asked whether to remove just that instance or all future occurrences

For shared team calendars, only someone with edit permissions on that calendar can remove the event.

When to Involve IT 🛠️

If you're not an admin yourself, this is a situation where IT or your system administrator needs to be in the loop. The tools required — PowerShell cmdlets, Admin Console access, Vault, or the Zoom Admin Portal — typically sit behind admin permissions for good reason. Reaching out to IT with the meeting title, date, and the deleted user's name gives them what they need to locate and resolve it efficiently.

What gets complicated is when the deletion happened weeks or months ago, the retention period has lapsed, and the meeting is still showing up for attendees because no one caught it during offboarding. In that case, manual removal by each attendee is often the only remaining option.

How clean a resolution is possible really depends on how your organization manages account offboarding — and how quickly the issue was flagged after the user was removed.