Loading...

Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft

Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft

Microsoft Viva Engage is migrating email sender domains from @yammer.com to @engage.mail.microsoft (and @eu.yammer.com to @eu.engage.mail.microsoft) between September 2025 and April 2026. This affects all Viva Engage tenants and users, requiring updates to mail flow rules, security gateways, and third-party integrations referencing the old domains. 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 MC1117814, Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft, in September 2025. When this will happen: The email sender domain rollout began in early September 2025 for U.S. and EU tenants that were receiving messages from @yammer.com and @eu.yammer.com, respectively. The rollout is expected to complete by mid‑April 2026. A fallback/coexistence period will be in place between September 2025 and April 2026, during which some tenants will remain on the old experience while others transition to the new one. How this affects your organization: Who is affected: All Microsoft Viva Engage tenants in U.S., EU, and global regions. All users who receive Viva Engage emails, including notifications, announcements, and digests. Microsoft 365 administrators who manage: Exchange Online mail flow rules Email security gateways Journaling, archiving, or third-party mail integrations that reference the @yammer.com domain. What will happen: 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, delegates, leader identification, community expert, and other 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 […]

The post Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

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

M365 Admin
M365 Admin

by João Ferreira

Share post:

Related posts

Dynamics 365 Sales: Choose the data sources AI-powered Data Enrichment uses, including CRM notes

AI-powered Data Enrichment now lets admins choose which data sources the agent uses to enrich records. Outlook emails, Teams meetings, and the...

1 day ago

Microsoft Teams: Pro Management portal Analytics & Reports Design Refresh

We are refreshing the way we organize the Analytics & Reports area in the Pro Management portal to make it more user-friendly. Product Mic...

1 day ago

Copilot: Audio overviews on PDF Reteirement

Microsoft 365 Copilot mobile app’s Audio Overviews on PDFs, which create AI-generated podcast-style summaries for commercial users, will...

1 day ago

Public CDN is becoming optional during Brand Center setup

Brand Center setup will no longer require enabling Public CDN by default, allowing organizations to use branding governance without it. Public...

1 day ago

Microsoft 365 Copilot and Power Apps: Retirement of App Builder agent and vibe.powerapps.com

Microsoft is retiring the App Builder agent and vibe.powerapps.com by November 30, 2026, consolidating app creation into Copilot Cowork and Mi...

1 day ago

Outlook: Reply With a Template in Rules

New Outlook for Windows and Outlook on the web will let users create inbox rules that auto-reply with saved templates, automating routine resp...

1 day ago

Microsoft Purview Audit: AuditLogQuery API generally available and Search-UnifiedAuditLog retiring

The Microsoft Graph AuditLogQuery API will be generally available in October 2026, replacing the Search-UnifiedAuditLog PowerShell cmdlet, whi...

1 day ago

Dynamics 365 Sales – Information regarding the retirement of the Dynamics 365 Sales Insights standalone add-on

Starting November 1, 2026, Dynamics 365 Sales Insights as a standalone add-on will have reached end of support. Sales Insights is a legacy off...

1 day ago

Work IQ: Updating documents in Office

Work IQ enables agents to create and edit Microsoft Office documents using organizational context, helping users produce and update content mo...

1 day ago

Microsoft Purview: Information Protection – Apply default SharePoint library labels to data at rest

Enables auto‑labeling of existing SharePoint files to match the default sensitivity label configured on their document library. This helps org...

1 day ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.