Teams voicemail emails get a new sender
- Maxime Hiez
- Teams
- 28 Oct, 2026
Introduction
In Microsoft Teams, a voicemail lands in the Exchange Online mailbox as an email with an audio attachment, and many organizations have built rules around these emails. With the announcement MC1511072, published on October 16, 2026 and classified as a Major change, Microsoft is changing the sender and subject of voicemail emails : the From field will show “Microsoft Teams” with a no-reply address on the tenant’s domain, and the caller’s information will move to the subject. The worldwide rollout is estimated between early March 2027 and late June 2027.
Check the Auto Attendant shared voicemail history article HERE.
What changes in voicemail emails
The From field of voicemail emails will no longer contain the caller’s name, phone number or email address. That information moves to the subject and stays in the message body. For personal voicemail, MC1511072 describes the following before and after :
| Field | Today | After the change |
|---|---|---|
| From | Identified caller’s name and address, or unidentified caller’s number, with noreply@skype.voicemail.microsoft.com | “Microsoft Teams” with no-reply@ on the tenant’s default domain, or on a custom tenant domain when one is configured |
| Subject | “Voice mail (22 seconds)” | Caller (name and number, or number only), “Voicemail” and duration, for example “John Smith (+19371817273) - Voicemail (00:22)” |
| Sending domain | skype.voicemail.microsoft.com for PSTN calls, the tenant’s domain for Teams-to-Teams calls | The tenant’s default domain, or a custom tenant domain when one is configured |
Spelling matters : the current address is spelled noreply@, the new one no-reply@, with a hyphen. A rule that looks for the string “noreply” will therefore stop matching anything. In Teams, on the other hand, caller information displays the same way it does today.
Shared voicemail for Call Queues and Auto Attendants
Shared voicemail for Call Queues and Auto Attendants is changing format too. Today, the From field shows “Shared Voicemail” followed by the name of the call queue or Auto Attendant in parentheses.
After the change, that label gives way to the caller, the name of the queue or Auto Attendant and the duration, for example “John Smith - Shared voicemail in [queue name] (00:05)” for a Teams-to-Teams call. For a PSTN call, the caller’s name and number appear when the contact is found in Microsoft Entra ID, otherwise only their number. MC1511072 doesn’t yet make it clear whether this string will sit in the From field or in the subject. Either way, Outlook rules based on the “Shared Voicemail” sender will need to be reviewed.
A custom sending domain for voicemail
The sender address will support Bring Your Own Domain (BYOD) : with their own domain, organizations will be able to apply their existing SPF, DKIM, DMARC and domain-protection policies against spoofing and impersonation. It’s no small gain : according to Microsoft Learn, voicemail messages generated by Cloud Voicemail aren’t DKIM-signed today.
As of October 22, 2026, neither MC1511072 nor Microsoft Learn explains how to configure this domain, and no cmdlet has been published.
What administrators need to prepare
The change affects organizations that use Teams Calling, and MC1511072 mentions no way to keep the current format. Microsoft recommends reviewing mail-flow rules, allowlists and automation that depend on the current sender identity or domain, and getting ready to update them. Microsoft doesn’t break these categories down ; in practice, here’s where to look first :
- Mail-flow rules : Transport rules that target noreply@skype.voicemail.microsoft.com or its domain.
- Filtering and allowlists : Anti-spam bypasses and third-party gateway rules built on the current sender.
- Routing and automation : Outlook rules, Power Automate flows or ticketing integrations that read the caller from the From field.
The Microsoft Learn troubleshooting article shows what’s at stake : for voicemails filtered as spam, it suggests adding the service’s IP addresses to an SPF record, or creating a transport rule that bypasses filtering for those addresses. These are typically the configurations to review before March 2027.
No new license is mentioned (Cloud Voicemail doesn’t require a Teams Phone license), and neither is any additional compliance requirement.
note
Conclusion
In Teams, nothing changes for users ; in Outlook, they’ll see “Microsoft Teams” as the sender and the caller in the subject. For mail administration, the impact is sharper : a rule built on noreply@skype.voicemail.microsoft.com or on the caller in the From field will stop matching as soon as the rollout lands. The inventory can start now, without waiting for the custom domain, since the default address changes either way. What’s left is to watch for the MC1511072 update with the confirmed timeline and, ideally, the custom domain configuration.
Sources
Microsoft Learn - Set up Cloud Voicemail
Microsoft Learn - Manage shared voicemail for auto attendants and call queues
Microsoft Learn - Voicemail messages aren’t delivered in Teams
Did you enjoy this post ? If you have any questions, comments or suggestions, please feel free to send me a message from the contact form.
Don’t forget to follow us and share this post.
