Unable to delete calendar invites on my Calendar App after macOS Sequoia update

I have also experienced this problem. It happened to coincide with my upgrade to Sequoia...

Still no resolution but some further insights:

This issue with calendar events being automatically created with the flag "This event was imported (read-only)" seems to only occur when someone sends a calendar invite to one of our staff mailing lists that I'm part of. So my work email does not appear as part of the invite list but I'm subscribed (system-generated) to the mailing list that the event was sent to. MacOS Calendar picks up all those event invites and pushes them into my MS Exchange work calendar read-only.

I found this Apple Support article, which does not resolve the issue: "If you can’t change a calendar or event on Mac" but it hints at what the problem may be: "If you can’t change an event you created, or you can’t change your status for an event you were invited to, it might be because you’re using an email address in Calendar that isn’t on your card in Contacts. Make sure all your email addresses are listed on your Contacts card." – I haven't tried adding our work mailing lists to my contact card and doing so would be absurd and not a feasible solution.

Do any Apple software engineers actually still read these Discussion threads and could offer some advice or a fix?

Hi all.

I upgraded to 15.2 and this appears to be fixed. The calendar still showed items that were marked read-only and were still unable to be deleted.

HOWEVER, for me, I went into System Settings -> Internet Accounts -> and then to the Exchange account, and then disabled the calendar for the particular Exchange accounts. I also selected to "Delete from My Mac." I let it sit for a few moments, quit calendar, and then rebooted. I don't know whether or not the these last steps were necessary but, what the ****... After enabling the calendar in the Exchange account, only those things that should have come back came back!!

For me, I consider this issue solved/closed. I hope this is the case for everybody else!

aps

Same issue here. It's importing events from my work's Microsoft Exchange email account, and they appear as "This event was imported (read-only)" and it's impossible to get rid of them. Strangely, when I open the SAME calendar in Office 365 / Outlook Calendar, those events do NOT appear (as I have declined them).

There is other people with the same issue in the Microsoft support forum, but Microsoft of course says it's Apple's problem: https://answers.microsoft.com/en-us/msoffice/forum/all/how-to-stop-automatic-read-only-calendar-events/cd6cb278-7ad6-4414-97ef-33bcd8c334ed

Just to confirm what Armando wrote a few weeks ago: as of MacOS 15.2 the problem is not fixed, but the workaround is much easier. Toggling the exchange calendar account off/on will now no longer re-populate previously declined invites.

For me, the problem now seems to be more narrow: if you receive an exchange calendar invite and RESPOND to it in the apple notifications by "declining," the message seems to be sent correctly to the exchange server (it shows declined in outlook), but the event still shows up in your MacOS calendar, as read-only.

I have the same problem too, and I've spent *many* hours working on it.

But I don't think it's simply an Apple problem. I've talked with friends/colleagues who upgraded to Sequoia and are using an Exchange calendar through the built-in Mac Calendar app just fine.

I think it's a combination of changes apple made in Sequoia with permissions and security settings on the Exchange server side. In one way or another, the exchange server is not recognizing the MacOS Calendar app as having proper permissions to read/write to the Exchange calendar.

So either Apple needs to update Sequoia so that when you add your exchange calendar it meets the requirements on the server side, or the server-side settings need to be altered to give Sequoia calendar full access. I've tried to message my IT people who run the exchange server, but their usual response is "no."

Just following up to say that the MacOS 15.2 update did not fix the problem for me.

My problem remains: if I use a default email address different from my Microsoft Account login ID, then any invited calendar events show up as "read-only" on the Mac.**

Those same invitation calendar events still work fine on iOS and in Outlook.

**I hypothesize that if my University allowed me to edit my Microsoft 365 profile so that I could list more than one email address, then this problem would disappear. Unfortunately, they refuse to do this.

I continue to believe the root of the problem is that the Mac sees calendar invites sent to one email address while connecting to an exchange account with a different email address. It cannot reconcile that those are the same identities. An update to the Microsoft 365 profile that includes both addresses seems like it would fix this.

I'm also experiencing this same problem and recently up graded to Sequoia.

Same issue. I've tried responding to events and deleting them and I just can't get them to go away.

Update: The "This event was imported (read-only)" showing on ALL Calendar Events issue seems to have been related to Exchange email aliasing and which "account" Apple sees as "active" when I joined it to exchange. And not just having that email associated to your "me" contact card.

I removed the Exchange account a second time, re-added it using my "alias" as my username, then when clicking the SSO Sign in option using the actual username/password and events now show correctly. Events sent to "me" (aka the alias) now show 'correctly' and any previous 'phantoms' from Events sent to lists have also disappeared. The latter more likely due to deleting the calendar entirely though so I'll have to see the next time I receive a list invite to see whether that functions correctly or not (I suspect it will not).

I came here to post my own solution, which is very similar to DBTubbs, but with one tweak.

The problem is that the Mac Calendar app does not recognize the invite email address as belonging to Exchange account holder. So it treats those invited events as read-only. And as DBTubbs says, you cannot fix this by editing your Apple “me” contact card. You have to make the change on the Exchange server.

In my case the issue appeared because my default University email address (where all my invites were sent) was not the same as my University-Microsoft account email address.

DBTubbs solution would NOT WORK for me. I tried to log into my exchange account using the email address to which the invites were sent, but the exchange authentication server says rejected that with the error “email address not recognized.” I can ONLY log into to exchange with one email that my University exchange account recognizes.

The solution for me:

I changed my “default email address” in a proprietary profile page that my university sets up. This changed my Exchange contact information to the same email address as I log into the exchange servers. (Note that my exchange admin prohibits users from editing their own contact card, so the only way to make this change for me was through the separate profile page.)

After that change propagated to the servers, turning OFF and back ON the exchange calendar loaded all events properly.

I found a workaround to survive. If you set yourself as a delegate in exchange account properties, another copy of your calendar appears. This time without the "imported" events, all working fine so far. All you need then is to stop showing the original calendar.

I'm also a University employee and having the same problem. Deleting the account in Internet Profiles clears out the inaccurate entries as others have said, but then they just start to build back up again. It's getting very frustrating as I can't rely on my own calendar any more. Someone needs to sort this out as it's been a problem since last year.

I found a hack that is not ideal but gets rid of the clutter in calendar.

1. Create a dummy Exchange calendar. I call mine "void"
2. Change the label for the event that you cannot delete to "void"
3. Hide "void" from iCal view.

While I don't know who wrote the Exchange connector on MacOS, I am willing to bet this to be an Apple problem.