MC1467355 - Power BI subscriptions: Changes to notification delivery and sender experience

Message Center

Summary

Power BI is updating subscription notification delivery to improve reliability and sender reputation, changing sender identity, email formatting, and Copilot summary presentation. The phased rollout starts late September 2026 through January 2027. No subscription recreation is needed, but organizations should review mail rules relying on the old sender identity.

Published

Sep 4, 2026

Service

Power BI

Tag

Feature update
Admin impact

More information

What and why:

Power BI is making changes to how subscription notifications are delivered as part of ongoing efforts to improve notification delivery reliability, sender reputation, and long-term service health.

As part of this change, customers may notice updates to sender identity, email formatting, notification presentation, and Copilot-generated summary formatting for some subscription scenarios.

This change will roll out in phases as Power BI subscription scenarios are transitioned to the updated notification delivery experience.

Rollout schedule:

General Availability (Worldwide): Rollout is expected to begin in late September 2026 and continue in phases through early January 2027.

Impact on your organization:

Customers may notice changes in the way Power BI subscription emails are delivered and presented.

Depending on tenant configuration and subscription scenario, customers may notice changes to sender identity used for Power BI subscription emails.

Customers may also observe differences in:

  1. Email formatting
  2. Notification presentation
  3. Copilot-generated summary formatting

No interruption to subscription delivery is expected.

Existing subscriptions do not need to be recreated, and no changes to subscription schedules or recipient lists are expected.

Action required / Recommendations:

No tenant administrator action is required.

Organizations that have configured mail-processing rules, routing rules, allow lists, inbox rules, safe-sender configurations, or automated workflows that depend on the historical sender identity ([email protected]) should review those configurations and update them as needed following migration.

Existing subscriptions do not need to be recreated.

For additional information, including scenarios that may behave differently based on tenant configuration, please visit:

https://aka.ms/subs-update-message-more-info