Classic SharePoint Alerts will fully stop working in July 2026, and organizations must migrate all notification workflows to SharePoint Rules or Power Automate. Microsoft is retiring Alerts because they rely on legacy infrastructure, lack modern automation capabilities, and cannot be centrally governed. Beginning July 2025, new alert creation started shutting off; by October 2025, all alerts began expiring every 30 days; and in July 2026, all remaining Alerts permanently stop functioning. This is now an urgent operational requirement: any team still depending on Alerts will lose change‑tracking notifications unless they migrate.
📌 What’s happening (the retirement timeline)
- July 2025 — New tenants lose the ability to create Alerts.
- October 2025 — All existing Alerts begin expiring every 30 days unless manually extended by each user.
- January 2026 — Alert creation blocked for all tenants.
- July 2026 — Full retirement: Alerts cannot be extended and stop working permanently.
🚨 Why this is urgent
- All classic Alerts will stop sending notifications in July 2026.
- Alerts already became unreliable due to the 30‑day expiration cycle starting October 2025.
- Teams using Alerts for compliance, security, document monitoring, or workflow triggers face immediate operational risk.
- Users receive retirement banners, but no automatic migration exists — organizations must act.
🧭 What stops working in July 2026
- Immediate change alerts (file or list item updates)
- Daily/weekly digest alerts
- Alerts scoped to specific views
- Alerts notifying when someone modifies an item a user owns All of these cease entirely.
🛠 Recommended replacements
1. SharePoint Rules — best for simple notifications
- Built into modern lists/libraries
- No‑code
- Good for “when an item is created/modified, send an email” scenarios
- Limited logic and routing options
2. Power Automate — best for complex workflows
- Rich logic, conditions, approvals, Teams notifications, adaptive cards
- Can replace digest alerts, multi‑step workflows, cross‑system triggers
- Microsoft provides prebuilt templates for common Alert scenarios
📋 Migration priorities (operational guidance)
- Audit existing Alerts using the Microsoft 365 Assessment tool.
- Identify critical alerts used for compliance, security, or business‑critical monitoring.
- Map each alert to either SharePoint Rules (simple) or Power Automate (complex).
- Update user training and helpdesk scripts.
- Communicate the cutoff to prevent surprise outages.
🧩 Comparison table: Alerts vs. Rules vs. Power Automate
| Feature | SharePoint Alerts | SharePoint Rules | Power Automate |
|---|---|---|---|
| Status | Retired July 2026 | Supported | Supported |
| Complexity | Simple | Simple | Simple → Advanced |
| Logic | Very limited | Limited | Full conditional logic |
| Integrations | Email only | Email only | Email, Teams, Approvals, Adaptive Cards |
| Governance | No central admin | Limited | Full admin visibility |
| Best for | Legacy change notifications | Basic list/library triggers | Enterprise workflows |
🏁 Final takeaway
SharePoint Alerts retirement is now a critical operational deadline. Any organization still relying on Alerts must migrate immediately to avoid notification failures across document libraries, lists, and business processes.
