Can’t Delete Calendar Invites on Mac After macOS Sequoia Update? Here’s What to Know

Many macOS Sequoia users have run into a frustrating issue in the Calendar app: events from Office 365 or Exchange accounts appear as “This event was imported – read-only.” When this happens, it becomes impossible to delete, decline, or modify the invite directly from the Mac Calendar app—even if the invite has already been declined or deleted on other devices like an iPhone, iPad, or in Outlook.

See also: Outlook Will No Longer Work with Mac Mail, Here is What to Do

The Issue

This issue started appearing after users upgraded to macOS Sequoia (starting with version 15.1). It mainly affects calendars linked to Microsoft Exchange or Office 365. Events that were once editable are now locked in read-only mode, often due to how the Mac identifies the user in relation to the calendar invite.

In most cases, these are events sent to mailing lists or alias email addresses associated with the user’s account. Because macOS Calendar doesn’t always correctly link those addresses to the Exchange identity, the app treats the events as imported data and locks them.

See this article if you’re getting the “Server Responded with an Error” message.

Symptoms

• Calendar invites appear as “read-only” and cannot be removed.
• Even if an event is declined or deleted in Outlook or iOS, it still shows up in the Mac Calendar app.
• Some events are accepted or declined correctly on other platforms, but not synced properly on macOS.
• The problem may not exist on Intel-based Macs or older macOS versions.

Fixes

There’s no permanent fix yet, but several workarounds have been shared by affected users:

1. Disable and Re-enable the Calendar Account. This method helps clear the stuck read-only events:

• Go to System Settings > Internet Accounts.
• Select the Exchange account and uncheck Calendars.
• When prompted, choose “Delete from My Mac.”
• Wait a few seconds, then re-enable the calendar.

This often removes read-only entries, but newly received invites may cause the problem to return.

See also: How to Add or Delete Calendars on Mac

2. Create and Use a “Void” Calendar. A clever workaround is to create a secondary calendar (e.g., named “Void“) and assign unwanted events to it. The steps:

• Create a new calendar folder in Outlook or the Exchange web app.
• Move read-only events into this calendar using the Mac Calendar app.
• Then hide or delete the “Void” calendar.

This hides the clutter without needing to remove the entire Exchange account.

3. Address Mismatched Email Aliases. Some users found the issue is caused by mismatches between:

• The email address receiving the invite, and
• The email address used to sign in to Exchange.

Possible solutions include:

• Updating the default email address associated with the Exchange account (if permitted by the organization).
• Adding all alias and list addresses to the user’s Contacts card in macOS (though results have been inconsistent).

4. Use Delegate Access as a Workaround. By setting yourself as a delegate in Exchange settings, a secondary version of the calendar may appear. In many cases, this copy does not show the problematic read-only events. Go to your calendar settings and add yourself as a delegate.

See also: Calendar Invitation: Your Response To The Invitation Cannot Be Sent