A cloud-based service included in Microsoft 365, delivering scalable messaging and collaboration features with simplified management and automatic updates.
Cancel the two occurrence event IDs from the organizer’s calendar with Microsoft Graph; do not use Compliance Search purge or Remove-CalendarEvents, because neither provides safe occurrence-level removal for this scenario.
Recommended approach: cancel the occurrences as the organizer
Microsoft Graph can return expanded instances through calendarView. Supplying an occurrence event ID to the cancel operation cancels only that occurrence and sends the cancellation to attendees. The caller must operate as the organizer and have Calendars.ReadWrite; an attendee receives HTTP 400 when attempting cancellation.^1^^2^
The following delegated PowerShell example uses an explicit UTC interval. Replace the year, organizer, subject, and expected UTC start times with the actual values.
Import-Module Microsoft.Graph.Authentication
Import-Module Microsoft.Graph.Calendar
$organizer = "[Email]"
Connect-MgGraph -Scopes "Calendars.ReadWrite"
$events = Get-MgUserCalendarView -UserId $organizer `
-StartDateTime "2026-11-18T00:00:00Z" `
-EndDateTime "2026-11-26T23:59:59Z" `
-Property "id,subject,start,end,organizer,type,seriesMasterId" `
-All
$events |
Where-Object Subject -eq "Meeting1" |
Select-Object Id,Subject,Type,SeriesMasterId,Start,End,Organizer
Review that output before making changes. Select events only when all these values agree:
-
Subjectis the intended meeting. -
Organizer.EmailAddress.Addressis the expected organizer. -
Typeidentifies an occurrence or exception, not the series master. - Both events have the same expected
SeriesMasterId. -
Start.DateTimerepresents the intended meeting instant after accounting forStart.TimeZone.
Abort if more than one series or unexpected event is returned. Then assign the two reviewed occurrence IDs and cancel them:
$occurrenceIds = @(
"<validated-November-18-occurrence-ID>",
"<validated-November-25-occurrence-ID>"
)
$params = @{ Comment = "These two occurrences have been cancelled." }
foreach ($eventId in $occurrenceIds) {
Stop-MgUserEvent -UserId $organizer `
-EventId $eventId `
-BodyParameter $params
}
Stop-MgUserEvent is the Graph PowerShell command for cancelling a specified user event.^3^
This is destructive and sends cancellations, so test against one nonproduction series first. For unattended tenant automation, use application authentication instead of delegated authentication. The application still requires admin-consented Calendars.ReadWrite; restrict its mailbox access to the required mailboxes where your authorization design supports that.
Time-zone handling
The VM’s Pacific time zone does not control an eDiscovery query. Purview eDiscovery searches use UTC, and that search time zone cannot be changed.^4^ KeyQL date/time values must likewise be specified in UTC.^5^
For Graph discovery:
- Supply explicit ISO 8601 UTC values ending in
Z, or explicit numeric offsets. - Search a UTC interval wide enough to include both possible displayed local dates.
- Match the occurrence by its absolute start instant, organizer, subject, and series ID—not merely by “November 18.”
- A meeting can display as November 18 for one attendee and November 19 for another while still representing the same occurrence.
Graph interprets a calendarView boundary without an offset as UTC, so explicit offsets avoid ambiguity.^1^
Why the Exchange and Purview commands should not be used
Remove-CalendarEvents is unsuitable: if any instance of a recurring meeting falls inside its query window, it cancels the entire series, not only instances within that window.^6^
Compliance Search is designed to find indexed mailbox items, and purge is primarily intended for data-spillage response—not precise calendar-series maintenance. Purge is also limited to 10 items per mailbox per operation and requires the Purview Search And Purge role.^7^ A subject/from query can match the recurring master or associated meeting messages; it does not reliably select two expanded calendar occurrences.
Also, the posted commands create $searchName = "RemoveMI" but invoke the purge against "Meeting1". That identity mismatch would target a different search or fail. It should not be corrected and executed for this requirement because the underlying purge method remains unsafe.
If organizer cancellation is impossible
If the organizer mailbox cannot issue cancellations, each attendee copy must be processed individually using the Graph delete operation and that mailbox’s occurrence ID:
Remove-MgUserEvent -UserId $attendeeUpn -EventId $occurrenceId
The application needs Calendars.ReadWrite access to every processed mailbox. Deleting attendee copies does not issue an organizer cancellation; deleting from the organizer’s calendar does.^8^ Prefer organizer cancellation because it updates attendee calendars through the meeting lifecycle rather than independently modifying every mailbox.
EWS can also address an individual occurrence by occurrence item ID, but it should not be selected for new Exchange Online automation: EWS disablement began in October 2026 as part of its retirement, and Microsoft recommends migration to Graph.^9^
References
- Delegate access and calendar sharing with Microsoft Graph
- event: cancel
- Imports the Microsoft.Graph.Calendar PowerShell module and uses the Stop-MgUserEvent cmdlet to cancel a calendar event for a specified user, optionally includin...
- Create a search for a case in eDiscovery
- Keyword Query Language (KeyQL) syntax reference
- Remove-CalendarEvents-Syntax
- Find and delete email messages in eDiscovery
- Delete event
- Deprecation of Exchange Web Services in Exchange Online