{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibdbls5ws4tdgfijngiqt2xp27gblcdzr3g5yft6goawfodmg7ppq",
    "uri": "at://did:plc:xxrzfynfiasdpbxteqxi4jgq/app.bsky.feed.post/3mgya3zdw6b22"
  },
  "description": "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 ...",
  "path": "/m365-message-center/message/mc1251200/",
  "publishedAt": "2026-03-14T01:00:06.000Z",
  "site": "https://blog.tophhie.cloud",
  "tags": [
    "Yammer is evolving to Viva Engage | Viva Engage Blog",
    "@yammer.com",
    "@engage.mail.microsoft",
    "@eu.yammer.com",
    "@eu.engage.mail.microsoft"
  ],
  "textContent": "**[Introduction]**\n\nAs 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.\n\nThis update was previously communicated in **MC1117814** ,**Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft** , in September 2025.\n\n**[When this will happen:]**\n\n  * 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.\n  * The rollout is expected to complete by**mid‑April 2026**.\n  * 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.\n\n\n\n**[How this affects your organization:]**\n\n**Who is affected:**\n\n  * All Microsoft Viva Engage tenants in U.S., EU, and global regions.\n  * All users who receive Viva Engage emails, including notifications, announcements, and digests.\n  * Microsoft 365 administrators who manage:\n    * Exchange Online mail flow rules\n    * Email security gateways\n    * Journaling, archiving, or third-party mail integrations that reference the @yammer.com domain.\n\n\n\n**What will happen:**\n\nThe sender domain for Viva Engage emails will change as follows:\n\n  * **From @yammer.com to @engage.mail.microsoft** for U.S. and global regions.\n  * From **@eu.yammer.com to @eu.engage.mail.microsoft** for European regions.\n\n\n\nThese new domains are secured with industry standard authentication protocols (e.g., SPF) to help prevent spoofing and ensure reliable delivery.\n\nTo enhance security and reduce cross-tenant spam, sender addresses will now include a **tenant-specific prefix**. You may see emails from:\n\n  * **noreply_tenant@engage.mail.microsoft** (digests, delegates, leader identification, community expert, and other notifications)\n  * **notifications_tenant@engage.mail.microsoft** (community, storyline, and activity notifications)\n  * **announcements_tenant@engage.mail.microsoft** (leadership announcements)\n\n\n\nThese 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.\n\n**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.\n\nScreenshot: _An example of a new Viva Engage email notification sent from the updated @engage.mail.microsoft domain:_\n\n**[What you can do to prepare:]**\n\nReview and update the following configurations:\n\n  * Transport rules and email gateways: Update any rules that reference @yammer.com to include the new domains.\n  * Exchange filtering: Ensure filtering rules remain effective with the new sender domains.\n  * Outlook rules: Inform users that any rules based on **@yammer.com** will no longer apply. Users can manually update or remove these rules.\n\n\n\n**No admin action is required** unless your organization has custom configurations based on the old domain.\n\nLearn more: Yammer is evolving to Viva Engage | Viva Engage Blog\n\n**[Compliance considerations:]**\n\nNo compliance considerations identified, review as appropriate for your organization.",
  "title": "MC1251200: Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft",
  "updatedAt": "2026-03-14T01:00:06.450Z"
}