Posted inMicrosoft Viva

MC1309743: Viva Engage Stops Email Notifications for Users Without Valid Mailboxes

4 minutesPosted inMicrosoft Viva
MWPRO IMPACT SCORE
OPERATIONAL IMPACT
36
0 25 50 75 100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsTenant AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This update changes the rollout timeline for disabling email notifications to users without a mailbox. Admin impact is moderate as mailbox configurations and communication strategies may need review, although the change applies automatically. User impact is low because only those without valid mailboxes stop receiving emails, and Teams notifications remain unaffected. Urgency is moderate as rollout begins in a few weeks, requiring awareness and internal documentation updates rather than immediate action.
40
🛡️ Admin Impact
MEDIUM
15
👥 User Impact
LOW
45
⚡ Urgency
MEDIUM
35
🔧 Effort
MEDIUM
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Viva Engage will stop sending emails to users without a valid mailbox. This aims to reduce failed delivery attempts and improve email reliability.
👥

END USERS

Frontline users without an Exchange mailbox will no longer get Viva Engage email notifications.
🛡️

IT ADMINS

Review licensing to find users without mailboxes and update notification guidance if needed.
📅

ROLLOUT TIMELINE

Upcoming:
Mid-September to end of October 2026

📢 Official Microsoft Message Center Announcement

(Updated) Viva Engage: Email updates for frontline users without an active Exchange mailbox
Message ID: MC1309743 (Updated)

Updated August 26, 2026: We have updated the content timeline. Thank you for your patience. 

[Introduction]

Viva Engage will stop sending email notifications to users who do not have a valid mailbox or routable email destination. Previously, email notifications could still be attempted for these users, resulting in repeated delivery retries, increased load on email systems, and, in some cases, delays to important business communications.

This change reduces unnecessary email traffic, improves delivery efficiency, and helps ensure important communications are delivered reliably and on time.

Users with supported mailbox configurations, including cloud mailboxes, on-premises mailboxes, shared mailboxes, and other routable email destinations, will continue to receive Viva Engage email notifications as expected.

Notifications delivered through supported channels such as Microsoft Teams remain unaffected.

[When this will happen:]

General Availability (Worldwide): Rollout begins mid-September 2026 (previously end of August) and is expected to complete by end of October 2026 (previously end of September).

[How this affects your organization:]

Who is affected:

  • Users who do not have a valid mailbox or routable email destination.
  • Microsoft 365 admins managing Viva Engage users and mailbox configurations.

What will happen:

  • Viva Engage will no longer attempt to send email notifications to users who do not have a valid mailbox or routable email destination.
  • Users with cloud, on-premises, shared, or other supported mailbox configurations will continue to receive email notifications as expected.
  • This change does not affect the existing email notification experience for users with a valid mailbox or routable email destination.
  • Notifications delivered through Microsoft Teams or other supported channels are not impacted.
  • The change is enabled by default and applies automatically.
  • Organizations may see:
    • Reduced load on email systems and gateways.
    • Fewer retry attempts for undeliverable messages.
    • Improved email delivery efficiency and reliability.

[What you can do to prepare:]

  • No action is required.
  • Review your Exchange Online licensing configuration to identify users without mailbox access.
  • Evaluate your notification strategy (e.g., Teams vs. Email) for frontline workers.
  • Inform helpdesk and user support teams of the expected behavior change.
  • Update internal documentation if email notifications are referenced for frontline users.

[Compliance considerations:]

  • Alters how existing customer data is processed: Email notifications to users without mailboxes are no longer attempted, reducing unnecessary processing of undeliverable messages.
  • No other compliance impacts identified.

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1309743] Archive
Tooltip: View earlier revisions of this post

Share This Update
Tags: