M365 Changelog: (Updated) Yammer Rebranding to Viva Engage Domain Migration Update

MC679739 – Updated March 11, 2024: Microsoft has updated the rollout timeline below. Thank you for your patience.

If you took action to change or update your email configuration based on the previous communication then that should remain largely valid. Microsoft encourages users to review changes when any updated notice is received.

As previously communicated in MC561701 (May 2023), a key step in our rebranding from Yammer to Viva Engage is changing our web and email domains. These changes happen on different schedules and may impact you differently.

Changes to our web domain are currently not anticipated to impact our APIs. Should there be any changes in the future Microsoft will notify you.

This message is associated with Microsoft Roadmap ID 180352

When this will happen:

  • Web domain change: Rollout will begin in late March 2024 and is expected to be complete by mid-April 2024.
  • Email domain change: Rollout will begin in late June 2024 and is expected to be complete by mid-July 2024.

How this will affect your organization:

Web Domain

  • During rollout, the web domain will change for all tenants from https://web.yammer.com to engage.cloud.microsoft. No admin action is required to initiate the change, and it is not possible to opt-out of this change.
  • Admins need to prepare for this change because the old URL may be saved in bookmarks, linked from intranet pages, or configured in network devices like proxies. Microsoft will indefinitely redirect URLs to the new domain ensuring uninterrupted access in many cases, but you must review any domain usage specific to your environment. It is not possible for us to identify all places within your environment where redirections may not function correctly. Users may initially need to refresh their browsers to receive the redirect if they are using Viva Engage once the change occurs.
  • Most attention is required to other usage of the old domain which may be hardcoded in a network proxy or security system. It is not possible for Microsoft to identify instances like these which exist inside your environment. IT, network, or security admins inside your organization may be able to help identify instances and plan changes. Check your configuration for desktop and mobile browsers because they may be different.

Email Domain

  • The sender domain used in emails from Viva Engage will start changing from https://web.yammer.com to engage.mail.microsoft. This phased change to emails will continue until all Viva Engage email notifications and digests use the new sender domain. No admin action is required to initiate the change, and it is not possible to opt-out of this change.
  • Preparation for this change will depend on how you use the sender domain. If you have made specific customizations for the old domain in the past, then you may need to replicate the change for the new domain. If the old domain has been configured in transport rules, or an email gateway, then the new domain will need to be added. End users may need to update rules in Outlook. The impact will depend upon how you use the sender domain, so you will need to review your mail configuration and communicate with end users.
  • This change may go unnoticed by most users unless they have specific Outlook rules based on the sender domain. Outlook rules can be updated to use the new domain without admin intervention, but you will need to communicate that the change is coming. Moving to mail.microsoft eliminates the need for yammer.com rules. Customers can delete previous rules or modify them for mail.microsoft. Admins should review their email configuration.

Progressive Web App (PWA)

Users will need to re-install after the domain migration is completed in order to continue using the application this can be done through the browser PWA options: ChromeEdge and Firefox.

Desktop Notifications

Users who have enabled desktop notifications previously, after the domain migration will have to enable them again in the Settings menu.

What you need to do to prepare:

Review all places where you might have explicitly configured or hardcoded domain names. Share this information on the domain changes with the relevant admins noted above to give them time to make any necessary changes. Use existing changes implemented for the old domain as a guide to what you may need to implement for the new domain.

While changes are not anticipated to impact our APIs, it is possible that the old domain is hardcoded within a custom application, script, or automation – possibly in an unsupported manner. Review your usage of custom applications and contact your developer or partner for updates.