Viva Engage: Email updates for frontline users without an active Exchange mailbox

Starting mid-June 2026, Viva Engage will stop sending email notifications to frontline users with F1 and F3 licenses who lack active Exchange mailboxes, reducing email system load and improving delivery reliability. Notifications via Teams remain unaffected. No action is required, but review licensing and notification strategies.

[Introduction]

Viva Engage will stop sending email notifications to frontline users (F1 and F3 licenses) who do not have an active Exchange mailbox. Previously, notifications could still be sent to users without provisioned mailboxes, resulting in repeated delivery retries, increased load on email systems, and in some cases delays to the delivery of important business communications.

This change reduces unnecessary email traffic, improves delivery efficiency, and helps ensure business-critical communications are delivered reliably and on time. Notifications through supported channels such as Microsoft Teams remain unaffected.

[When this will happen:]

General Availability (Worldwide): Rollout begins mid-June 2026 and is expected to complete by early August 2026.

[How this affects your organization:]

Who is affected:

• Frontline users assigned F1 and F3 licenses without an active Exchange Online mailbox
• Microsoft 365 admins managing Viva Engage and Exchange licensing

What will happen:

• Viva Engage will no longer send email notifications to users without active Exchange mailboxes.
• Users with valid Exchange mailbox licenses will continue to receive email notifications as usual.
• Notifications delivered via 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 gateways.
  • Fewer retry attempts for undeliverable messages.
  • Improved delivery reliability for critical emails.

[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.