MC1028317 – (Updated) Microsoft Teams: Enhanced compliance in voicemail messages

Microsoft Exchange Logo

*For this entry exists the more relevant or more recent entry MC987329

check before: 2025-05-01

Product:

Exchange, Teams

Platform:

Online, US Instances, World tenant

Status:

Change type:

Admin impact, Feature update, Updated message, User impact

Links:

MC987329

Details:

Updated April 9, 2025: We have updated the content. Thank you for your patience.
We would like to inform you that the rollout of Request for Comments (RFC) compliance enforcement changes, originally announced in January 2025 (MC987329) have been postponed until May 2025.
With the compliance update in May 2025, the "From" field of voicemail email messages will be modified to meet the latest RFC standard. Specifically, RFC 6854: Update to Internet Message Format to Allow Group Syntax in the "From:" and "Sender:" Header Fields. According to this standard, the Internet message format must always include an address in the "From" header. For example:
Previously: +44 28 7584 5695 <442875845695>
After the change: +44 28 7584 5695 <noreply@skype.voicemail.microsoft.com>
[When this will happen:]
General Availability (Worldwide, GCC): We will begin rolling out early May 2025 and expect to complete by mid-June 2025.
General Availability (GCCH, DoD): We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025.

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:

Created:
2025-03-11

updated:
2025-04-10

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS How does it affect me

XXXXXXX ... free basic plan only

MS Preperations

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

** AI generated content. This information must be reviewed before use.

a free basic plan is required to see more details. Sign up here


change history

DatePropertyoldnew
2025-04-10MC Last Updated03/11/2025 06:04:192025-04-09T15:29:38Z
2025-04-10MC MessagesWe would like to inform you that the rollout of Request for Comments (RFC) compliance enforcement changes, originally announced in January 2025 (MC987329) have been postponed until May 2025.
With the compliance update in May 2025, the "From" field of voicemail email messages will be modified to meet the latest RFC standard. Specifically, RFC 6854: Update to Internet Message Format to Allow Group Syntax in the "From:" and "Sender:" Header Fields. According to this standard, the Internet message format must always include an address in the "From" header. For example:
Previously: +44 28 7584 5695 <442875845695>
After the change: +44 28 7584 5695 <noreply@skype.voicemail.microsoft.com>
[When this will happen:]
General Availability (Worldwide, GCC): We will begin rolling out early May 2025 and expect to complete by mid-June 2025.
General Availability (GCCH, DoD): We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025.
Updated April 9, 2025: We have updated the content. Thank you for your patience.
We would like to inform you that the rollout of Request for Comments (RFC) compliance enforcement changes, originally announced in January 2025 (MC987329) have been postponed until May 2025.
With the compliance update in May 2025, the "From" field of voicemail email messages will be modified to meet the latest RFC standard. Specifically, RFC 6854: Update to Internet Message Format to Allow Group Syntax in the "From:" and "Sender:" Header Fields. According to this standard, the Internet message format must always include an address in the "From" header. For example:
Previously: +44 28 7584 5695 <442875845695>
After the change: +44 28 7584 5695 <noreply@skype.voicemail.microsoft.com>
[When this will happen:]
General Availability (Worldwide, GCC): We will begin rolling out early May 2025 and expect to complete by mid-June 2025.
General Availability (GCCH, DoD): We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025.
2025-04-10MC SummaryThe enforcement of RFC compliance changes for Microsoft Teams voicemail messages has been postponed to May 2025. The "From" field will be updated to meet RFC 6854 standards, changing to noreply@skype.voicemail.microsoft.com. Organizations should allowlist this email by May 2025. Early adoption is available upon request.
2025-04-10MC MessageTagNamesFeature update, User impact, Admin impactUpdated message, Feature update, User impact, Admin impact
2025-04-10MC preparePlease allowlist the following email address as soon as possible, and no later than May 2025: noreply@skype.voicemail.microsoft.com. Starting from May 2025 Voicemails will be delivered from the address noreply@skype.voicemail.microsoft.com.
If you would like to enable RFC compliance changes earlier than May 2025, please contact us by replying to this message post.
https://www.rfc-editor.org/rfc/rfc6854
Please prepare for the following email address to be the sender of this messages, no later than May 2025: noreply@skype.voicemail.microsoft.com. Starting from May 2025 Voicemails will be delivered from the address noreply@skype.voicemail.microsoft.com.
If you would like to enable RFC compliance changes earlier than May 2025, please contact us by replying to this message post.
https://www.rfc-editor.org/rfc/rfc6854

Last updated 2 weeks ago

Share to MS Teams

Login to your account

Welcome Back, We Missed You!