What and Why
We are updating how Microsoft Teams sends guest invitation emails to improve clarity and trust in cross-tenant collaboration. Instead of being sent from a Microsoft no-reply address, guest invitation emails will soon appear to come directly from the inviter’s email address.
This change helps recipients easily recognize who invited them, enables direct replies, and reduces confusion, improving the overall collaboration experience.
Rollout Schedule
General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late June 2026 and expect to complete by late July 2026.
Impact on Your Organization
Who is affected
- All Microsoft Teams users who invite external guests
- External recipients of guest invitations
- Microsoft 365 administrators managing guest access and collaboration policies
Platforms/Services
- Microsoft Teams
- Exchange Online (email delivery behavior)
What will happen
- Guest invitation emails will appear to come from the inviting user’s email address instead of a Microsoft no‑reply address:

- Invitees can reply directly to the inviter via email or can redeem the invitation and use Teams.
- There are no changes to guest access permissions or policies.
- No admin configuration required.
- The feature will be enabled by default across all tenants.
Action Required / Recommendations
No action is required.
However, we recommend that you:
- Inform users that invitation emails will now appear to come from their own email address.
- Prepare helpdesk/support teams for potential questions about unexpected replies from external guests.
- Review your guest access policies to ensure they align with your organization’s collaboration practices.
- Update internal documentation or training materials if they reference invitation email behavior.
Learn more:
Compliance considerations
| Question | Answer |
| Does the change provide a new way of communicating between users, tenants, or subscriptions? | Yes. External guests can now directly reply to the inviter via email, enabling a new communication path tied to the invitation workflow. |