Published Jun 25, 2025
Microsoft 365 is introducing Multi-admin notifications for Microsoft 365 Backup, allowing centralized backup notifications for key stakeholders. The rollout starts in early August 2025 and completes by mid-August 2025. Organizations can configure notification lists for important backup events. No action is required before the rollout.
Updated July 10, 2025: We have updated the timeline below. Thank you for your patience.
We’re introducing a new feature—Multi-admin notifications for Microsoft 365 Backup. This feature enables organizations to configure a centralized backup notifications list to ensure key stakeholders are regularly alerted about important backup events and routine actions. This feature enhances visibility and administrative awareness by sending email notifications to designated admins and stakeholders, helping protect against malicious or accidental changes to backup settings and restores.
This message is associated with Microsoft 365 Roadmap ID 464993.
When this will happen:
General Availability (Worldwide): We will begin rolling out early August 2025 (previously early July) and expect to complete by mid-August 2025 (previously mid-July).
How this will affect your organization:
This feature applies only to the Microsoft 365 Backup tool. If your organization is not currently using or planning to use this tool, no action is required.
After this rollout, if you are using Microsoft 365 Backup, you’ll be able to configure the notification list in one of four ways:
Notifications will be triggered for important backup events, such as:
You can also choose to receive notifications for routine backup job completions.
To access this feature:
This feature will be available by default but requires configuration to activate notifications.
What you need to do to prepare:
This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins and/or users about this change and update internal documentation.
Learn more