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

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

Message ID: MC1028317 (Updated)

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.

Source: Microsoft

<<< [MC1028317] Archive
Tooltip: View earlier revisions of this post

Latest Posts

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *