Fix Microsoft 365 Cannot Send Emails or Teams Invitations to Same Domain
Question details
Users are unable to send emails or Microsoft Teams meeting invitations to colleagues sharing the same custom domain when the organization's email is hosted by a third-party provider.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Attempting to send Teams meeting invitations or standard emails to users on the same domain while utilizing a split-domain or third-party email host setup.
- Observed behavior
- Microsoft 365 attempts to route the messages internally instead of externally to the third-party host, resulting in a non-delivery report (NDR) stating the address may be misspelled or does not exist.
Ensure you have Microsoft 365 Administrator privileges, as resolving this routing issue requires access to the Exchange Admin Center to modify domain and mail flow settings.
Change the Accepted Domain Type to Internal Relay
Switching your domain type from Authoritative to Internal Relay forces Microsoft 365 to forward emails and Teams invitations to your third-party email provider when an internal mailbox is not found.
By default, when you add a custom domain to Microsoft 365, it is set as 'Authoritative'. This means Exchange Online assumes it hosts all mailboxes for that domain.
If your email is actually hosted by a third party (like Google Workspace or a local server), you must change this setting to 'Internal Relay' so Microsoft 365 knows to route unknown addresses outward.
Sign in to the Microsoft 365 admin center with your administrator credentials, expand the left menu, and select 'Exchange' to open the Exchange Admin Center.
In the left navigation pane, go to 'Mail flow' and then click on 'Accepted domains'.
Select the custom domain experiencing the issue. A details pane will appear on the right side.
Under the 'This accepted domain is' section, select 'Internal Relay' instead of 'Authoritative', then click 'Save'.

Set Up an Outbound Connector for the Domain
Create a mail flow connector to explicitly direct Microsoft 365 on how to route messages for your shared domain to your third-party email host.
Run a Message Trace to Identify Delivery Drops
Use the Exchange Message Trace tool to analyze the exact point of failure for your Teams invitations and gather diagnostic details.
Experience Seamless Document Collaboration with WPS Office
While troubleshooting Microsoft 365 domain routing and email hosting issues can be a complex administrative burden, editing and sharing documents shouldn't be. WPS Office offers a free, lightweight, and highly compatible alternative for teams looking to collaborate without the hassle of intricate server setups.
- 1. Download WPS Office: Visit the official WPS Office website to download the lightweight installer for your preferred operating system.
- 2. Install the Suite: Run the downloaded setup file and follow the quick installation prompts to set up the software.
- 3. Start Collaborating: Open your existing Microsoft Office files instantly and start collaborating with your team without worrying about email domain restrictions.

Frequently Asked Questions
Why does Microsoft 365 reject emails sent to my own domain?
When a custom domain is configured in Microsoft 365, the system defaults to assuming it hosts all mailboxes for that domain (Authoritative). If your email is actually managed by a third-party host, Microsoft 365 tries to route the message internally, fails to find the mailbox, and drops the message instead of sending it out to the internet.
Can I use Microsoft Teams if my email is hosted by a third-party provider?
Yes, you can use Teams. However, to ensure calendar invitations and notifications reach colleagues on the same domain, your Microsoft 365 administrator must configure the domain as an 'Internal Relay' so Teams knows to forward unresolved invites to your external email host.
What is an Internal Relay domain in Exchange Online?
An Internal Relay domain tells Microsoft 365 that mailboxes for this domain are shared between Exchange Online and another email platform. If Microsoft 365 cannot find a matching recipient internally, it will relay the message to your designated external email provider.
How do I fix the 'misspelled or does not exist' error when sending Teams invites?
This NDR error indicates the recipient's mailbox is missing from the Microsoft 365 internal directory. To fix it, an administrator needs to log into the Exchange Admin Center, change the accepted domain from Authoritative to Internal Relay, and ensure a proper mail flow connector is set up pointing to the actual email host.




