Viva Engage: Retirement of Viva Engage Desktop Notifications

Originally posted by Microsoft Oct 10, 2025 Uncategorized 0 Comments

Microsoft is retiring Viva Engage desktop notifications by mid-November 2025 to streamline notifications across Microsoft 365. Desktop push notifications and related settings will be removed. Users will still receive notifications via Viva Engage in-app, Teams, and Outlook. No admin action is needed; inform users accordingly.

To simplify and streamline notification experiences across Microsoft 365, Microsoft is retiring the desktop notification capability in Viva Engage. This change helps reduce redundancy and ensures consistency across supported channels such as Teams, Outlook, and Viva Engage in-app notifications. It also affects how users receive @mention and community announcement notifications on desktop.

When this will happen:

This change will roll out automatically by mid-November 2025. 

How this affects your organization:

• Who is affected:
  
  • Users who previously enabled desktop notifications in Viva Engage.
  • Tenant admins who configured desktop notification settings in Admin Center.

• What will happen:
  
  • The following settings will be removed:
    • The Allow users to enable desktop notifications setting will be removed from Admin Center.

    
    View image in new tab

    • The Desktop push notifications option will be removed from user Notification settings.

    
    View image in new tab

  • Users will no longer receive @mention and community announcement notifications via desktop push.
  • Users will continue to receive notifications via:
    
    • Viva Engage in-app
    • Microsoft Teams
    • Outlook (web, mobile, and desktop)

What you can do to prepare:

• Inform users that desktop notifications—including @mention and community announcement alerts—will no longer be available in Viva Engage.
• Encourage users to rely on Teams, Outlook, and Viva Engage in-app notifications.
• Update internal documentation if it references desktop notification settings.
• No admin action is required for this change.

Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.

Message ID: MC1169069