Microsoft Teams: Enhanced compliance in voicemail messages
The 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 [email protected]. Organizations should allowlist this email by May 2025. Early adoption is available upon request. 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 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. 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 allowlist the following email address as soon as possible, and 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. Message ID: MC1028317
The post Microsoft Teams: Enhanced compliance in voicemail messages appeared first on M365 Admin.
Published on:
Learn moreWe can help you with Microsoft Teams: Enhanced compliance in voicemail messages
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
External messaging limits for onmicrosoft.com-only organizations in Microsoft Teams
Microsoft Teams will impose outbound external messaging limits starting mid-September 2026 for organizations using only the default onmicrosof...
Microsoft Teams: Enable agents for existing applications in your organization
For third-party applications already being used in your organization, admins can now discover and enable the corresponding Teams agents from w...
Microsoft Viva: Campaigns Hub in Engage and Engage in Teams mobile
The Campaigns Hub in Viva Engage provides a centralized mobile destination where employees can discover and participate in organizational camp...
Planner: Conditional Coloring
Conditional Coloring highlight tasks based on selected criteria, making priorities, status, and important task details easier to spot. Product...
Outlook: Offline settings “Days of email to save” admin policy
Tenant admins will be able to define the default value for “Days of email to save” in Offline settings and designate whether end u...
Microsoft Copilot Studio: Agent Sharing amongst makers
Enables sharing of agents with other makers in the new GHCP harness. Makers can grant other makers Agent Viewer (view analytics/evaluations on...
OneDrive Photos on Windows: admin controls and policy support
OneDrive Photos, integrated into the OneDrive sync app for Windows 10/11, is currently available only for personal Microsoft accounts, with wo...
Admin app retiring in Teams, Outlook and Microsoft365.com
The Admin app for very small businesses in Teams, Outlook, and Microsoft365.com will retire by October 2026, with rollout starting August 2026...
Calls popout into a new window on the browser to support multi-tasking and collaboration during a meeting
Microsoft Teams for Web will introduce a Picture-in-Picture Call Monitor in October 2026, allowing users to manage meeting controls in a separ...
Microsoft Windows Autopatch: September 2026 Windows security update requires a restart for hotpatch-enabled devices
The September 2026 Windows security update requires a restart for hotpatch-enabled devices because it is a standard update. Devices will remai...