Outlook.com calendar acceptance replies fail for external domains (550 5.5.0 S2017062302)

Question

We identified and resolved one issue related to legacy Outlook aliases (outlook.pt), but a second issue still remains.

Reproducible scenario:

1. Sender uses an external domain email account Example: ******@personaldomain.com
2. A calendar invitation is sent to an Outlook.com account
3. The Outlook.com recipient accepts the invitation
4. Outlook.com generates a delivery failure:

550 5.5.0 Requested action not taken: mailbox unavailable (S2017062302)

Example server: CO1PEPF00012E7D.mail.protection.outlook.com

Important findings:

• Normal emails work correctly
• Only calendar invitation responses fail
• The issue occurs during acceptance processing
• This appears related to Outlook.com calendar response routing/processing

Has anyone reproduced this with external senders?

This does not appear to be related to SPF/DKIM/IP reputation.

Answer 1

No, this is not SPF/DKIM/DMARC related at all.

When your Microsoft account uses a non-Microsoft email address, it does not have its own email functionality. The actual sending and receiving of emails still happens through your third party email provider. As a result, when you send a meeting invitation through Teams, Microsoft cannot access your external email to send it. Instead, it sends the invitation using a randomly assigned Microsoft email address, one that ends in outlook.com. This is why recipients cannot reply to the invite directly. However, your meeting itself is not affected.

To give your Microsoft account proper email functionality, you can create a Microsoft-based email alias and set it as the primary alias. Here is how:

Go to https://account.live.com and sign in to your personal account.

Click on "Your Info," then choose "Sign-in preferences," and select "Add an alias."

Choose to create a new alias. It will allow you to create one that's outlook.com.

After creating it, set it as your primary alias.

Keep your current third party email as a secondary alias. Do not remove it.

Answer 2

The behavior described is not documented in the provided material as a known or reproducible issue specific to external domains and 550 5.5.0 (S2017062302) for calendar acceptance replies.

The only closely related, documented Outlook.com calendar issues are:

1. Known issues with accepting shared Outlook.com calendars using Microsoft 365 for business accounts in Outlook 2016, which produce a generic “Something went wrong” error or sign‑in failure, with a workaround of accepting via Outlook on the web, iOS, or Android.
2. A historical issue with subscribing to .ics/iCal calendars in Outlook.com that has been confirmed as fixed.

There is no documented guidance in the context about:

• 550 5.5.0 S2017062302 errors specifically, or
• Calendar acceptance replies from Outlook.com to external domains failing while normal mail succeeds.

Because of this, no supported, documented reproduction steps or resolution can be provided beyond what is already in the context.

---

References:

• Error when sharing a calendar from Outlook.com personal or home account to an Office 365 business account
• Known issues with shared calendars in Outlook
• Unable to add a Calendar