Favorite your Message Center and Roadmap items. Access them anytime via your Profile. Export and share with your team or your LLM.

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

Message ID
MC1309743
View in Message Center
Service
Microsoft Viva
Category
Stay Informed
Tags
Feature updateUser impactAdmin impact
Rollout
September 2026October 2026

Summary

Starting end of September 2026, Viva Engage will stop sending email notifications to users without valid mailboxes, reducing email system load and improving delivery. Users with supported mailboxes or Teams notifications remain unaffected. No action is required, but admins should review mailbox configurations and update support resources accordingly.

Details

Updated September 16, 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 end of September 2026 (previously mid-September) 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.

Change History

Show
September 16, 2026 at 10:30 PM Updated
Summary
Previous
Starting mid-September 2026, Viva Engage will stop sending email notifications to users without valid mailboxes, reducing email system load and improving delivery. Users with supported mailboxes will be unaffected. Notifications via Teams remain unchanged. No action is required, but admins should review mailbox configurations and update support documentation.
New
Starting end of September 2026, Viva Engage will stop sending email notifications to users without valid mailboxes, reducing email system load and improving delivery. Users with supported mailboxes or Teams notifications remain unaffected. No action is required, but admins should review mailbox configurations and update support resources accordingly.
Last Updated Date
Previous
2026-08-26T21:50:47.767Z
New
2026-09-16T21:03:25.027Z
Body Content
Previous
<p>Updated August 26, 2026: We have updated the content timeline. Thank you for your patience.&nbsp;</p><p><b>[Introduction]</b></p><p>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.</p><p>This change reduces unnecessary email traffic, improves delivery efficiency, and helps ensure important communications are delivered reliably and on time.</p><p>Users with supported mailbox configurations, including <b>cloud mailboxes, on-premises mailboxes, shared mailboxes, and other routable email destinations</b>, will continue to receive Viva Engage email notifications as expected.</p><p>Notifications delivered through supported channels such as Microsoft Teams remain unaffected.</p> <p><b>[When this will happen:]</b></p><p> General Availability (Worldwide): Rollout begins <b>mid-September 2026</b> (previously&nbsp;end of August)&nbsp;and is expected to complete by<b>&nbsp;end of October 2026</b> (previously end of September).</p> <p><b>[How this affects your organization:]</b></p> <p><b>Who is affected:</b></p> <ul> <li>Users who do not have a valid mailbox or routable email destination.</li><li>Microsoft 365 admins managing Viva Engage users and mailbox configurations.</li> </ul> <p><b>What will happen:</b></p> <ul> <li>Viva Engage will <b>no longer attempt to send email notifications to users who do not have a valid mailbox or routable email destination.</b></li><li>Users with <b>cloud, on-premises, shared, or other supported mailbox configurations</b> will continue to receive email notifications as expected.</li><li>This change does not affect the existing email notification experience for users with a valid mailbox or routable email destination.</li><li>Notifications delivered through <b>Microsoft Teams or other supported channels are not impacted.</b></li><li>The change is <b>enabled by default</b> and applies automatically.</li> <li>Organizations may see: <ul> <li>Reduced load on email systems and gateways.</li><li>Fewer retry attempts for undeliverable messages.</li><li>Improved email delivery efficiency and reliability.</li> </ul> </li> </ul> <p><b>[What you can do to prepare:]</b></p> <ul> <li>No action is required.</li> <li>Review your <b>Exchange Online licensing configuration</b> to identify users without mailbox access.</li> <li>Evaluate your<b> notification strategy</b> (e.g., Teams vs. Email) for frontline workers.</li> <li>Inform helpdesk and user support teams of the expected behavior change.</li> <li>Update internal documentation if email notifications are referenced for frontline users.</li> </ul> <p><b>[Compliance considerations:]</b></p> <ul> <li>Alters how existing customer data is processed: Email notifications to users without mailboxes are no longer attempted, reducing unnecessary processing of undeliverable messages.</li> <li>No other compliance impacts identified.</li> </ul>
New
<p>Updated September 16, 2026: We have updated the content timeline. Thank you for your patience.&nbsp;</p><p><b>[Introduction]</b></p><p>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.</p><p>This change reduces unnecessary email traffic, improves delivery efficiency, and helps ensure important communications are delivered reliably and on time.</p><p>Users with supported mailbox configurations, including <b>cloud mailboxes, on-premises mailboxes, shared mailboxes, and other routable email destinations</b>, will continue to receive Viva Engage email notifications as expected.</p><p>Notifications delivered through supported channels such as Microsoft Teams remain unaffected.</p> <p><b>[When this will happen:]</b></p><p> General Availability (Worldwide): Rollout begins <b>end of September 2026 </b>(previously mid-September) and is expected to complete by <b>end of October 2026</b> (previously end of September).</p> <p><b>[How this affects your organization:]</b></p> <p><b>Who is affected:</b></p> <ul> <li>Users who do not have a valid mailbox or routable email destination.</li><li>Microsoft 365 admins managing Viva Engage users and mailbox configurations.</li> </ul> <p><b>What will happen:</b></p> <ul> <li>Viva Engage will <b>no longer attempt to send email notifications to users who do not have a valid mailbox or routable email destination.</b></li><li>Users with <b>cloud, on-premises, shared, or other supported mailbox configurations</b> will continue to receive email notifications as expected.</li><li>This change does not affect the existing email notification experience for users with a valid mailbox or routable email destination.</li><li>Notifications delivered through <b>Microsoft Teams or other supported channels are not impacted.</b></li><li>The change is <b>enabled by default</b> and applies automatically.</li> <li>Organizations may see: <ul> <li>Reduced load on email systems and gateways.</li><li>Fewer retry attempts for undeliverable messages.</li><li>Improved email delivery efficiency and reliability.</li> </ul> </li> </ul> <p><b>[What you can do to prepare:]</b></p> <ul> <li>No action is required.</li> <li>Review your <b>Exchange Online licensing configuration</b> to identify users without mailbox access.</li> <li>Evaluate your<b> notification strategy</b> (e.g., Teams vs. Email) for frontline workers.</li> <li>Inform helpdesk and user support teams of the expected behavior change.</li> <li>Update internal documentation if email notifications are referenced for frontline users.</li> </ul> <p><b>[Compliance considerations:]</b></p> <ul> <li>Alters how existing customer data is processed: Email notifications to users without mailboxes are no longer attempted, reducing unnecessary processing of undeliverable messages.</li> <li>No other compliance impacts identified.</li> </ul>
August 27, 2026 at 12:31 AM Updated
Summary
Previous
Starting end of August 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.
New
Starting mid-September 2026, Viva Engage will stop sending email notifications to users without valid mailboxes, reducing email system load and improving delivery. Users with supported mailboxes will be unaffected. Notifications via Teams remain unchanged. No action is required, but admins should review mailbox configurations and update support documentation.
Last Updated Date
Previous
2026-07-13T23:07:05.887Z
New
2026-08-26T21:50:47.767Z
Body Content
Previous
<p>Updated July 13, 2026: We have updated the timeline. Thank you for your patience.&nbsp;</p><p><b>[Introduction]</b></p><p>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.</p><p>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.</p> <p><b>[When this will happen:]</b></p><p> General Availability (Worldwide): Rollout begins <b>end of August 2026</b> (previously&nbsp;mid-June)&nbsp;and is expected to complete by<b>&nbsp;end of September 2026 </b>(previously early August).</p> <p><b>[How this affects your organization:]</b></p> <p><b>Who is affected:</b></p> <ul> <li>Frontline users assigned <b>F1 and F3 licenses without an active Exchange Online mailbox</b></li> <li>Microsoft 365 admins managing Viva Engage and Exchange licensing</li> </ul> <p><b>What will happen:</b></p> <ul> <li>Viva Engage<b> will no longer send email notifications</b> to users without active Exchange mailboxes.</li> <li>Users with valid Exchange mailbox licenses will continue to receive email notifications as usual.</li> <li>Notifications delivered via <b>Microsoft Teams or other supported channels are not impacted</b>.</li> <li>The change is <b>enabled by default</b> and applies automatically.</li> <li>Organizations may see: <ul> <li>Reduced load on email gateways.</li> <li>Fewer retry attempts for undeliverable messages.</li> <li>Improved delivery reliability for critical emails.</li> </ul> </li> </ul> <p><b>[What you can do to prepare:]</b></p> <ul> <li>No action is required.</li> <li>Review your <b>Exchange Online licensing configuration</b> to identify users without mailbox access.</li> <li>Evaluate your<b> notification strategy</b> (e.g., Teams vs. Email) for frontline workers.</li> <li>Inform helpdesk and user support teams of the expected behavior change.</li> <li>Update internal documentation if email notifications are referenced for frontline users.</li> </ul> <p><b>[Compliance considerations:]</b></p> <ul> <li>Alters how existing customer data is processed: Email notifications to users without mailboxes are no longer attempted, reducing unnecessary processing of undeliverable messages.</li> <li>No other compliance impacts identified.</li> </ul>
New
<p>Updated August 26, 2026: We have updated the content timeline. Thank you for your patience.&nbsp;</p><p><b>[Introduction]</b></p><p>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.</p><p>This change reduces unnecessary email traffic, improves delivery efficiency, and helps ensure important communications are delivered reliably and on time.</p><p>Users with supported mailbox configurations, including <b>cloud mailboxes, on-premises mailboxes, shared mailboxes, and other routable email destinations</b>, will continue to receive Viva Engage email notifications as expected.</p><p>Notifications delivered through supported channels such as Microsoft Teams remain unaffected.</p> <p><b>[When this will happen:]</b></p><p> General Availability (Worldwide): Rollout begins <b>mid-September 2026</b> (previously&nbsp;end of August)&nbsp;and is expected to complete by<b>&nbsp;end of October 2026</b> (previously end of September).</p> <p><b>[How this affects your organization:]</b></p> <p><b>Who is affected:</b></p> <ul> <li>Users who do not have a valid mailbox or routable email destination.</li><li>Microsoft 365 admins managing Viva Engage users and mailbox configurations.</li> </ul> <p><b>What will happen:</b></p> <ul> <li>Viva Engage will <b>no longer attempt to send email notifications to users who do not have a valid mailbox or routable email destination.</b></li><li>Users with <b>cloud, on-premises, shared, or other supported mailbox configurations</b> will continue to receive email notifications as expected.</li><li>This change does not affect the existing email notification experience for users with a valid mailbox or routable email destination.</li><li>Notifications delivered through <b>Microsoft Teams or other supported channels are not impacted.</b></li><li>The change is <b>enabled by default</b> and applies automatically.</li> <li>Organizations may see: <ul> <li>Reduced load on email systems and gateways.</li><li>Fewer retry attempts for undeliverable messages.</li><li>Improved email delivery efficiency and reliability.</li> </ul> </li> </ul> <p><b>[What you can do to prepare:]</b></p> <ul> <li>No action is required.</li> <li>Review your <b>Exchange Online licensing configuration</b> to identify users without mailbox access.</li> <li>Evaluate your<b> notification strategy</b> (e.g., Teams vs. Email) for frontline workers.</li> <li>Inform helpdesk and user support teams of the expected behavior change.</li> <li>Update internal documentation if email notifications are referenced for frontline users.</li> </ul> <p><b>[Compliance considerations:]</b></p> <ul> <li>Alters how existing customer data is processed: Email notifications to users without mailboxes are no longer attempted, reducing unnecessary processing of undeliverable messages.</li> <li>No other compliance impacts identified.</li> </ul>
July 14, 2026 at 2:30 AM Updated
Summary
Previous
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 update support accordingly.
New
Starting end of August 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.
Last Updated Date
Previous
2026-06-15T23:08:45.640Z
New
2026-07-13T23:07:05.887Z
Body Content
Previous
<p>Updated June 15, 2026: We have updated the timeline. Thank you for your patience.&nbsp;</p><p><b>[Introduction]</b></p><p>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.</p><p>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.</p> <p><b>[When this will happen:]</b></p><p> General Availability (Worldwide): Rollout begins <b>mid-June 2026</b> and is expected to complete by<b> early August 2026</b>.</p> <p><b>[How this affects your organization:]</b></p> <p><b>Who is affected:</b></p> <ul> <li>Frontline users assigned <b>F1 and F3 licenses without an active Exchange Online mailbox</b></li> <li>Microsoft 365 admins managing Viva Engage and Exchange licensing</li> </ul> <p><b>What will happen:</b></p> <ul> <li>Viva Engage<b> will no longer send email notifications</b> to users without active Exchange mailboxes.</li> <li>Users with valid Exchange mailbox licenses will continue to receive email notifications as usual.</li> <li>Notifications delivered via <b>Microsoft Teams or other supported channels are not impacted</b>.</li> <li>The change is <b>enabled by default</b> and applies automatically.</li> <li>Organizations may see: <ul> <li>Reduced load on email gateways.</li> <li>Fewer retry attempts for undeliverable messages.</li> <li>Improved delivery reliability for critical emails.</li> </ul> </li> </ul> <p><b>[What you can do to prepare:]</b></p> <ul> <li>No action is required.</li> <li>Review your <b>Exchange Online licensing configuration</b> to identify users without mailbox access.</li> <li>Evaluate your<b> notification strategy</b> (e.g., Teams vs. Email) for frontline workers.</li> <li>Inform helpdesk and user support teams of the expected behavior change.</li> <li>Update internal documentation if email notifications are referenced for frontline users.</li> </ul> <p><b>[Compliance considerations:]</b></p> <ul> <li>Alters how existing customer data is processed: Email notifications to users without mailboxes are no longer attempted, reducing unnecessary processing of undeliverable messages.</li> <li>No other compliance impacts identified.</li> </ul>
New
<p>Updated July 13, 2026: We have updated the timeline. Thank you for your patience.&nbsp;</p><p><b>[Introduction]</b></p><p>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.</p><p>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.</p> <p><b>[When this will happen:]</b></p><p> General Availability (Worldwide): Rollout begins <b>end of August 2026</b> (previously&nbsp;mid-June)&nbsp;and is expected to complete by<b>&nbsp;end of September 2026 </b>(previously early August).</p> <p><b>[How this affects your organization:]</b></p> <p><b>Who is affected:</b></p> <ul> <li>Frontline users assigned <b>F1 and F3 licenses without an active Exchange Online mailbox</b></li> <li>Microsoft 365 admins managing Viva Engage and Exchange licensing</li> </ul> <p><b>What will happen:</b></p> <ul> <li>Viva Engage<b> will no longer send email notifications</b> to users without active Exchange mailboxes.</li> <li>Users with valid Exchange mailbox licenses will continue to receive email notifications as usual.</li> <li>Notifications delivered via <b>Microsoft Teams or other supported channels are not impacted</b>.</li> <li>The change is <b>enabled by default</b> and applies automatically.</li> <li>Organizations may see: <ul> <li>Reduced load on email gateways.</li> <li>Fewer retry attempts for undeliverable messages.</li> <li>Improved delivery reliability for critical emails.</li> </ul> </li> </ul> <p><b>[What you can do to prepare:]</b></p> <ul> <li>No action is required.</li> <li>Review your <b>Exchange Online licensing configuration</b> to identify users without mailbox access.</li> <li>Evaluate your<b> notification strategy</b> (e.g., Teams vs. Email) for frontline workers.</li> <li>Inform helpdesk and user support teams of the expected behavior change.</li> <li>Update internal documentation if email notifications are referenced for frontline users.</li> </ul> <p><b>[Compliance considerations:]</b></p> <ul> <li>Alters how existing customer data is processed: Email notifications to users without mailboxes are no longer attempted, reducing unnecessary processing of undeliverable messages.</li> <li>No other compliance impacts identified.</li> </ul>
June 16, 2026 at 2:30 AM Updated
Title
Previous
Viva Engage: Email updates for frontline users without an active Exchange mailbox
New
(Updated) Viva Engage: Email updates for frontline users without an active Exchange mailbox
Summary
Previous
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.
New
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 update support accordingly.
Last Updated Date
Previous
2026-05-13T23:08:25.520Z
New
2026-06-15T23:08:45.640Z
Tags
Previous
Feature update,User impact,Admin impact
New
Updated message,Feature update,User impact,Admin impact
Body Content
Previous
<p><b>[Introduction]</b></p><p>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.</p><p>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.</p> <p><b>[When this will happen:]</b></p><p> General Availability (Worldwide): Rollout begins <b>mid-June 2026</b> and is expected to complete by<b> early August 2026</b>.</p> <p><b>[How this affects your organization:]</b></p> <p><b>Who is affected:</b></p> <ul> <li>Frontline users assigned <b>F1 and F3 licenses without an active Exchange Online mailbox</b></li> <li>Microsoft 365 admins managing Viva Engage and Exchange licensing</li> </ul> <p><b>What will happen:</b></p> <ul> <li>Viva Engage<b> will no longer send email notifications</b> to users without active Exchange mailboxes.</li> <li>Users with valid Exchange mailbox licenses will continue to receive email notifications as usual.</li> <li>Notifications delivered via <b>Microsoft Teams or other supported channels are not impacted</b>.</li> <li>The change is <b>enabled by default</b> and applies automatically.</li> <li>Organizations may see: <ul> <li>Reduced load on email gateways.</li> <li>Fewer retry attempts for undeliverable messages.</li> <li>Improved delivery reliability for critical emails.</li> </ul> </li> </ul> <p><b>[What you can do to prepare:]</b></p> <ul> <li>No action is required.</li> <li>Review your <b>Exchange Online licensing configuration</b> to identify users without mailbox access.</li> <li>Evaluate your<b> notification strategy</b> (e.g., Teams vs. Email) for frontline workers.</li> <li>Inform helpdesk and user support teams of the expected behavior change.</li> <li>Update internal documentation if email notifications are referenced for frontline users.</li> </ul> <p><b>[Compliance considerations:]</b></p> <ul> <li>Alters how existing customer data is processed: Email notifications to users without mailboxes are no longer attempted, reducing unnecessary processing of undeliverable messages.</li> <li>No other compliance impacts identified.</li> </ul>
New
<p>Updated June 15, 2026: We have updated the timeline. Thank you for your patience.&nbsp;</p><p><b>[Introduction]</b></p><p>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.</p><p>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.</p> <p><b>[When this will happen:]</b></p><p> General Availability (Worldwide): Rollout begins <b>mid-June 2026</b> and is expected to complete by<b> early August 2026</b>.</p> <p><b>[How this affects your organization:]</b></p> <p><b>Who is affected:</b></p> <ul> <li>Frontline users assigned <b>F1 and F3 licenses without an active Exchange Online mailbox</b></li> <li>Microsoft 365 admins managing Viva Engage and Exchange licensing</li> </ul> <p><b>What will happen:</b></p> <ul> <li>Viva Engage<b> will no longer send email notifications</b> to users without active Exchange mailboxes.</li> <li>Users with valid Exchange mailbox licenses will continue to receive email notifications as usual.</li> <li>Notifications delivered via <b>Microsoft Teams or other supported channels are not impacted</b>.</li> <li>The change is <b>enabled by default</b> and applies automatically.</li> <li>Organizations may see: <ul> <li>Reduced load on email gateways.</li> <li>Fewer retry attempts for undeliverable messages.</li> <li>Improved delivery reliability for critical emails.</li> </ul> </li> </ul> <p><b>[What you can do to prepare:]</b></p> <ul> <li>No action is required.</li> <li>Review your <b>Exchange Online licensing configuration</b> to identify users without mailbox access.</li> <li>Evaluate your<b> notification strategy</b> (e.g., Teams vs. Email) for frontline workers.</li> <li>Inform helpdesk and user support teams of the expected behavior change.</li> <li>Update internal documentation if email notifications are referenced for frontline users.</li> </ul> <p><b>[Compliance considerations:]</b></p> <ul> <li>Alters how existing customer data is processed: Email notifications to users without mailboxes are no longer attempted, reducing unnecessary processing of undeliverable messages.</li> <li>No other compliance impacts identified.</li> </ul>

Never Miss a Microsoft 365 Update

Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.