Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft
Microsoft Viva Engage is changing its email sender domains from @yammer.com to @engage.mail.microsoft, starting August 2025 for U.S. tenants and completing by October 2025 globally. This update includes tenant-specific prefixes for enhanced security and requires admins to update any custom email rules or integrations referencing the old domains. Introduction As part of the final phase of the Viva Engage rebranding, we’re updating the email sender domains used for Viva Engage communications. This change ensures a consistent and secure brand experience across all surfaces and completes the transition from Yammer to Viva Engage. This update was previously communicated in MC679739, “Yammer Rebranding to Viva Engage Domain Migration Update,” in October 2023. When this will happen The email sender domain rollout will begin in mid to late August 2025 for U.S. tenants currently receiving messages from @yammer.com. It will expand to EU tenants using @eu.yammer.com in early September. The entire rollout is expected to complete by the end of October 2025. A fallback/coexistence period will be in place between August and the end of October, during which both the old and new domains will be supported. This will be managed via an internal experiment. How this will affect your organization The sender domain for Viva Engage emails will change as follows: From @yammer.com to @engage.mail.microsoft for U.S. and global regions. From @eu.yammer.com to @eu.engage.mail.microsoft for European regions. These new domains are secured with industry-standard authentication protocols (e.g., SPF) to help prevent spoofing and ensure reliable delivery. To enhance security and reduce cross-tenant spam, sender addresses will now include a tenant-specific prefix. You may see emails from: [email protected] (digests and delegate notifications) [email protected] (community, storyline, and activity notifications) [email protected] (leadership announcements) These changes apply to all Viva Engage tenants, regardless of license tier (e.g., Viva P1, P2), and affect all Viva Engage emails, including notifications, announcements, and digests. Third-party integrations (e.g., journaling, archiving, or routing systems) that rely on the @yammer.com domain for classification or authentication may be impacted. Any such configurations should be reviewed and updated to recognize the new domains. An example of a new Viva Engage email notification sent from […]
The post Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft appeared first on M365 Admin.
Published on:
Learn moreWe can help you with Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Microsoft Entra ID: Risk-based anti-bot verification (CAPTCHA) for SMS and voice multi-factor authentication
Starting mid-November 2026, Microsoft Entra ID will add risk-based CAPTCHA verification for SMS and voice MFA to prevent automated fraud. Some...
[Outlook for iOS and Android] Copilot Chat in Outlook UX improvements
Copilot Chat in Outlook for iOS and Android is being updated with a refreshed, consistent design across Microsoft 365 apps, improved chat inte...
Microsoft Word: Retirement of legacy compatibility settings
Microsoft Word will retire legacy compatibility settings for documents in Compatibility Mode starting December 2026 (Windows) and early 2027 (...
Power Platform – Information regarding the end of support for SharePoint temporary authentication URLs
Starting April 1, 2027, SharePoint temporary authentication URLs will be retired. Power Apps and Automate functionality that relies on these U...
Windows Office Hours: November 19, 2026
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live ...
Scheduled prompts in Microsoft 365 Copilot are moving to native Copilot scheduling and the Tasks view
Microsoft 365 Copilot is moving scheduled prompts from Power Platform to native Copilot scheduling, enabling automatic execution of one-time o...
Prevent issues with NetApp SMB shares: Learn about new Windows Server security requirements
Microsoft introduced additional security requirements for LDAP authentication on Active Directory domain controllers starting with the October...
60-day reminder: Hardening changes for ReFS volumes on removable media
Microsoft is making hardening changes to the Resilient File System (ReFS). The changes improve the security posture of Windows by adding visib...
Microsoft 365 Copilot: Copilot Workspaces is replacing standalone agent selection with agentic chat
Microsoft 365 Copilot Workspaces will replace standalone agent selection (Researcher, Analyst, Designer) with an agentic chat that applies ski...
Microsoft Teams: Updated recording and transcript access setting behavior for town halls and webinars
Microsoft Teams is updating the “Who has access to the recording or transcript” option for Events App town halls and webinars. It ...