Use Cancel registration when an attendee withdraws—and, unless your organization specifically requires removal, for duplicate registrations—because cancellation retains the registration with a Canceled status and activates cancellation-aware event processing.
Difference between the actions
| Action |
Documented behavior |
Appropriate use |
| Cancel registration |
Changes the registration’s status to Canceled. It is a supported event-management action available under Registration and attendance. ^1^ |
The attendee can no longer attend, or a duplicate should remain visible as a canceled record for operational tracking. |
| Delete registration |
The supplied Microsoft documentation does not define whether this command removes only the registration row or also affects related session registrations, attendance data, trigger history, capacity, or downstream automation. |
Reserve for records that must be removed rather than retained as canceled, after validating the behavior in a nonproduction environment. |
Canceled registrations remain identifiable in the Registration and attendance grid alongside Registered, Waitlisted, and Checked-in statuses. ^2^
Cancellation also has documented operational effects:
- The Event Registration Canceled trigger can remove the person from an active real-time journey so they stop receiving event reminders. ^3^
- If event waitlisting is enabled, a canceled place can allow the next waitlisted person to be registered, depending on the waitlist configuration. ^4^
Equivalent cancellation behavior is not documented for Delete registration, so deletion should not be assumed to fire the cancellation trigger or produce the same waitlist and journey results.
Recommended handling
When someone says they are not attending
- Open the event.
- Select Registration and attendance.
- Select the attendee’s registration.
- Select Cancel registrations above the grid.
- Verify that Status reason is now Canceled. ^1^
For duplicate registrations
- Keep the valid registration as Registered.
- Cancel the duplicate.
- If the duplicate has related session registrations, review those registrations as well; the attendee-facing cancellation page supports cancellation of individual sessions or the entire event registration. ^1^
- Use Delete registration only if your data-retention policy requires the erroneous registration to be removed and testing confirms the effects on related records, capacity, journeys, and waitlists.
If deletion is required, first reproduce it with a test contact and test event in a sandbox. Compare the event’s registration count, related session records, waitlist, and journey history before and after deletion. Microsoft’s published event-registration guidance does not specify those deletion semantics, so production behavior should not be inferred from the button label alone.
References
- Set up event registration cancellation
- Manage your event registrations
- Boost event engagement with journeys
- Set up and manage an event waitlist