Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 11:37 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Enhanced compliance in voicemail messages

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 14 May 2025 early May 2025, mid-May 2025 → late May 2025, early June 2025, late June 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated May 14, 2025: We have updated the timeline below. 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 <[email protected]>  When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late May 2025 (previously early May) and expect to complete by mid-June 2025. General Availability (GCCH, DoD): We will begin rolling out early June 2025 (previously mid-May) and expect to complete by late June 2025 (previously mid-June). How this will affect your organization: Voicemails will be delivered from the email address [email protected] to meet the latest RFC standard. What you need to do to prepare: Please prepare for the following email address to be the sender of this messages, no later than May 2025: [email protected]. Starting from May 2025 Voicemails will be delivered from the address [email protected]. If you would like to enable RFC compliance changes earlier than May 2025, please contact us by replying to this message post.

What changed

Between archive captures, newest first
  1. Updated April 9,May 14, 2025: We have updated the content.timeline below. Thank you for your patience. We would like to inform you that … this will happen: General Availability (Worldwide, GCC): We will begin rolling out earlylate May 2025 (previously early May) and expect to complete by mid-June 2025. General Availability (GCCH, DoD): We will begin rolling out mid-Mayearly June 2025 (previously mid-May) and expect to complete by mid-June 2025.late June 2025 (previously mid-June). How this will affect your organization: Voicemails will be delivered from the …

    • Tags Feature update, User impact, Admin impact → Updated message, Feature update, User impact, Admin impact

    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 … the latest RFC standard. What you need to do to prepare: Please allowlistprepare for the following email address as soon as possible, andto be the sender of this messages, no later than May 2025: [email protected]. Starting from May 2025 Voicemails will …

  2. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

Other posts named in this one

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

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.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 11:37 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current