[What and why]
Microsoft Viva Engage is updating email reply notifications to make them more relevant and intent-driven. With this change, users will continue to receive email notifications for interactions that directly involve them, such as direct replies and @mentions, while notification emails generated from broader participation in conversations will be reduced.
This update is designed to help users focus on the conversations most relevant to them and reduce unnecessary email volume. Existing community subscription settings and other notification controls will remain unchanged.
[Rollout schedule]
- General Availability (Worldwide): Beginning in early September 2026 and expected to complete by late October 2026
[Impact on your organization]
Who is affected
- Users who receive Microsoft Viva Engage notifications through email
- Organizations that use Viva Engage communities or storylines
- Users who participate in Viva Engage conversations
Platforms and services
- Microsoft Viva Engage
- Viva Engage email notifications
What will happen
After this rollout:
Users will continue to receive email notifications when:
- They start a conversation.
- Someone directly replies to their post or comment.
- They are @mentioned.
Users will no longer be automatically subscribed to all future replies in a conversation because they:
- Read the conversation.
- Commented on the conversation.
Community subscribers will continue to receive notifications for new posts and announcements.
Storyline followers will continue to receive notifications for new posts and announcements.
Existing user notification preferences and tenant-level controls will remain unchanged.
No new admin settings, policies, or controls will be introduced.
The change will be enabled automatically as part of the service update.
[Action required and recommendations]
No action is required.
You may want to:
- Review and update internal documentation that describes Viva Engage email notifications.
- Update training and support materials that reference reply notification behavior.
- Inform support and help desk teams that users may notice a reduction in email notifications from active conversations.
- Gather user feedback after rollout is complete.
[Compliance considerations]
No compliance considerations identified, review as appropriate for your organization.