Teams voicemail by email: new sender and new subject starting in March 2027 (MC1511072)

With Message Center notification MC1511072 dated October 16, 2026, Microsoft announced a new delivery method for Teams voicemail emails. According to the current plan, rollout will begin in early March 2027 and is expected to be completed by the end of June 2027; Microsoft reserves the right to make changes and intends to provide binding dates and any required customer actions in a further notification. The purpose is to support custom sender domains (Bring Your Own Domain), so voicemail emails are covered by the organization’s SPF, DKIM, and DMARC policies.

What is changing

The “From” field will no longer contain the caller’s name, phone number, or email address. This information will instead appear in the subject line and continue to appear in the message body. The display in Teams itself will remain unchanged.

For users, this has two visible consequences: all voicemails will appear in the inbox with the same sender, “Microsoft Teams,” and because the address is a no-reply address, the “Reply” feature will no longer reach the caller.

Who is affected

All organizations using Teams Calling with voicemail are affected, including Teams Phone with Calling Plan, Operator Connect, or Direct Routing, as well as call queues and auto attendants with shared voicemail. The notification does not mention any licensing or cloud restrictions; the rollout has been announced worldwide.

Action is required wherever something relies on the current sender or subject:

• Exchange transport rules that check for skype.voicemail.microsoft.com, the caller as the sender, or the subjects Voice mail and Shared Voicemail
• Entries in allow lists: Tenant Allow/Block List, spoof allow entries, AllowedSenderDomains in anti-spam policies
• Inbox rules for users and call queue shared mailboxes that sort or forward voicemails based on sender or subject
• Power Automate flows, ticketing systems, and CRM integrations that read the caller’s phone number from the sender
• Upstream or downstream gateways (for example, with centralized mail flow in hybrid environments) that contain rules or exceptions for the voicemail domain

How to check whether you are affected

The following queries run in an Exchange Online PowerShell session (Connect-ExchangeOnline).

Search transport rules

$muster = 'skype\.voicemail|voice ?mail|shared voicemail'
Get-TransportRule |
  Where-Object { ($_ | Format-List * | Out-String) -match $muster } |
  Select-Object Name, State, Priority

Review every matching rule for conditions such as FromAddressContainsWords, SenderDomainIs or SubjectContainsWords.

Allow lists and anti-spam policies

Get-TenantAllowBlockListItems -ListType Sender |
  Where-Object Value -match 'voicemail'
Get-TenantAllowBlockListSpoofItems |
  Where-Object SpoofedUser -match 'voicemail'
Get-HostedContentFilterPolicy |
  Select-Object Name, AllowedSenderDomains, AllowedSenders

Determine actual mail volume

Message tracing shows whether and where voicemails are currently being delivered:

Get-MessageTraceV2 -StartDate (Get-Date).AddDays(-10) -EndDate (Get-Date) -ResultSize 5000 |
  Where-Object { $_.SenderAddress -like '*@skype.voicemail.microsoft.com' -or $_.Subject -match 'voice ?mail' } |
  Group-Object RecipientAddress | Sort-Object Count -Descending |
  Select-Object Count, Name

The recipient list shows which mailboxes and shared mailboxes receive voicemails. There, it is worth reviewing inbox rules (Get-InboxRule -Mailbox <Adresse>) and connected flows.

What to do

1. Change rules to use the subject instead of the sender: Base new conditions on the future subject patterns - Voicemail ( and - Shared voicemail in . Until rollout reaches your tenant, keep the old and new conditions in parallel.

2. Remove allow entries for skype.voicemail.microsoft.com after rollout. Emails from your own tenant domain do not need an exception; allowing your own domain would be a security risk because it makes spoofing easier.

3. Adjust automations that read the caller’s number from the sender. The number will instead appear in parentheses in the subject or, for unknown callers, immediately after Unidentified:.

4. Prepare your custom sender domain: Microsoft plans to provide configuration instructions for sending from a custom domain in the follow-up notification. If DMARC for this domain is set to p=reject, SPF and DKIM must cover sending from Exchange Online; otherwise, voicemails will end up in quarantine.

5. Inform users and the service desk: sender “Microsoft Teams,” caller details in the subject, and no more ability to reply to the caller by email.