Microsoft Teams: Upcoming change to voicemail message delivery by email
Rollout
- Ends
- 30 Jul 2027
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedWhat and why
We’re changing how Microsoft Teams voicemail messages are delivered by email to improve security and give organizations more control over sender identity. Organizations will be able to send voicemail notifications from their own domain and apply existing SPF, DKIM, DMARC, and domain-protection policies to help prevent spoofing and impersonation.
Supporting organization-owned sending domains requires a new voicemail email delivery solution. Caller information will move from the email From field to the Subject line and remain in the message body.
Rollout schedule
- General Availability (Worldwide): Rollout is currently estimated to begin in early March 2027 and complete by late June 2027.
- Note: This schedule is subject to change. We will publish an updated Message center communication with the confirmed rollout timeline and required customer actions.
Impact on your organization
Who is affected
- Organizations that are using Teams Calling.
Platforms and services
- Microsoft Teams
- Voicemail
- Exchange Online
What will happen
- The From field in voicemail email messages will no longer contain the caller’s name, phone number, or email address.
- The sender address will support Bring Your Own Domain (BYOD), allowing organizations to use their own domain for voicemail email delivery.
- Caller information will move to the Subject line and remain in the message body.
- Organizations should review and prepare to update mail-flow rules, allowlists, filtering, routing, or automation based on the current voicemail sender identity or domain.
- Caller information will continue to appear in Teams as it does today, while the underlying email delivery and sender domain will change.
| Component | Today | After the change |
|---|---|---|
| E-mail From field | Identified caller: John Smith "[email protected]" or unidentified caller: "+19371817273" [email protected] | "Microsoft Teams" no-reply@<default tenant domain> or "Microsoft Teams" <custom tenant domain> when configured |
| E-mail Subjectfield (personal voicemail) | Voice mail (22 seconds) | Identified: John Smith (+19371817273) - Voicemail (00:22) Unidentified: +19371817273 - Voicemail (00:22) |
| E-mail domain | “skype.voicemail.microsoft.com” for PSTN calls or tenant owned domain for Teams-to-Teams calls | <default tenant domain> or <custom tenant domain> when configured |
| E-mail From field (Call queue shared voicemail) | Shared Voicemail (<CQ name>) | Teams-to-Teams: John Smith - Shared voicemail in <CQ name> (00:05). PSTN, contact found in Entra: John Smith (+37251223123) - Shared voicemail in <CQ name> (00:05) or contact not found in Entra +3751223123 - Shared voicemail in <CQ name> (00:05) |
| E-mail From field (Auto Attendant shared voicemail) | Shared Voicemail (<AA name>) | Teams-to-Teams: John Smith - Shared voicemail in <AA name> (00:11). PSTN, contact found in Entra: John Smith (+3725122312) - Shared voicemail in <AA name> (00:11) or contact not found in Entra: +3725122312 - Shared voicemail in <AA name> (00:11) |
Action required and recommendations
We recommend that you review any mail-flow rules, allowlists or automation that depend on the current voicemail sender identity or domain and prepare to update them as needed.
Compliance considerations
No compliance concerns or additional compliance requirements have been identified as part of this change.
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.