Microsoft Teams Free – Meeting invitations appear in Teams but are not delivered by email

Hello everyone,

I'm investigating an inconsistent behavior with meeting invitations in Microsoft Teams Free, and I would appreciate some guidance.

Environment:

• Microsoft Teams Free, using personal Microsoft accounts registered with company email addresses.

Corporate email is hosted by an external provider (Skymail), not Microsoft 365 or Exchange Online.

Meetings are scheduled directly through Microsoft Teams.

The issue has been tested using the Teams desktop application, web version, and PWA.

Issue description:

When the meeting organizer types a participant's email address, Teams automatically suggests the corresponding contact.

If the organizer selects that suggested contact:

The meeting invitation appears in the recipient's Teams notifications.

The recipient can access and join the meeting normally.

However, no invitation email is received in the external corporate mailbox.

During testing, I found a different behavior when manually entering the recipient's full email address and adding a semicolon (;) at the end, without selecting the suggested contact.

In that case:

The invitation was successfully delivered to the recipient's corporate email address.

However, the invitation did not appear in the recipient's Teams notifications.

The email displayed the organizer's name, but the actual sender was an automatically generated-looking ******@outlook.com address rather than the organizer's corporate email address.

Unfortunately, this workaround was not reliable. When repeating the same procedure, Teams started displaying an error indicating that the contact could not be found.

Troubleshooting already performed:

Tested both contact selection and manual email entry.

Repeated the tests using Teams desktop, Teams web, and PWA.

Tested with another personal Microsoft account registered using an externally hosted corporate email address.

Confirmed that meetings can be accessed normally through Teams when the suggested contact is selected.

Confirmed that email delivery was possible in some tests, but the behavior could not be reproduced consistently.

My questions are:

Is this a known behavior or limitation of Microsoft Teams Free when personal Microsoft accounts use email addresses hosted by an external provider?

Why does selecting an existing Teams contact deliver the invitation within Teams but not generate an email notification?

Why does manually entering the email address sometimes trigger an email invitation, but not a Teams notification?

Is the automatically generated ******@outlook.com sender address expected for this type of Microsoft account?

Is there a supported way to ensure that meeting invitations are delivered both to the recipient's external email mailbox and to their Teams account?

The users previously relied on receiving meeting invitations by email, so I'm trying to determine whether this is a known limitation, a recent behavioral change, or an issue that can be resolved through configuration.

Any clarification, official documentation, or suggested troubleshooting steps would be greatly appreciated.

Thank you!Hello everyone,

I'm investigating an inconsistent behavior with meeting invitations in Microsoft Teams Free, and I would appreciate some guidance.

Environment:

Microsoft Teams Free, using personal Microsoft accounts registered with company email addresses.

Corporate email is hosted by an external provider (Skymail), not Microsoft 365 or Exchange Online.

Meetings are scheduled directly through Microsoft Teams.

The issue has been tested using the Teams desktop application, web version, and PWA.

Issue description:

When the meeting organizer types a participant's email address, Teams automatically suggests the corresponding contact.

If the organizer selects that suggested contact:

The meeting invitation appears in the recipient's Teams notifications.

The recipient can access and join the meeting normally.

However, no invitation email is received in the external corporate mailbox.

During testing, I found a different behavior when manually entering the recipient's full email address and adding a semicolon (;) at the end, without selecting the suggested contact.

In that case:

The invitation was successfully delivered to the recipient's corporate email address.

However, the invitation did not appear in the recipient's Teams notifications.

The email displayed the organizer's name, but the actual sender was an automatically generated-looking ******@outlook.com address rather than the organizer's corporate email address.

Unfortunately, this workaround was not reliable. When repeating the same procedure, Teams started displaying an error indicating that the contact could not be found.

Troubleshooting already performed:

Tested both contact selection and manual email entry.

Repeated the tests using Teams desktop, Teams web, and PWA.

Tested with another personal Microsoft account registered using an externally hosted corporate email address.

Confirmed that meetings can be accessed normally through Teams when the suggested contact is selected.

Confirmed that email delivery was possible in some tests, but the behavior could not be reproduced consistently.

My questions are:

Is this a known behavior or limitation of Microsoft Teams Free when personal Microsoft accounts use email addresses hosted by an external provider?

Why does selecting an existing Teams contact deliver the invitation within Teams but not generate an email notification?

Why does manually entering the email address sometimes trigger an email invitation, but not a Teams notification?

Is the automatically generated ******@outlook.com sender address expected for this type of Microsoft account?

Is there a supported way to ensure that meeting invitations are delivered both to the recipient's external email mailbox and to their Teams account?

The users previously relied on receiving meeting invitations by email, so I'm trying to determine whether this is a known limitation, a recent behavioral change, or an issue that can be resolved through configuration.

Any clarification, official documentation, or suggested troubleshooting steps would be greatly appreciated.

Thank you!