{
"title": "The SharePoint ‘Alert Me’ Feature Is Dead. Here’s How to Keep Your Notifications Working.",
"content": "For millions of SharePoint Online users, the familiar “Alert Me” button has finally gone silent. Starting this month, Microsoft is pulling the plug on the legacy SharePoint Alerts feature, ending the self-service email notifications that have notified document changes, list updates, and task assignments for over a decade. The retirement follows a phased rollout: since January 2026, no new alerts could be created, and as of July 2026, existing alerts have stopped working entirely. If you’ve been relying on those automatic emails to track a library, approve a document, or respond to a team change, your workflow may already be broken. The good news? Microsoft offers two built-in replacements—SharePoint Rules and Power Automate—and a clear migration path, but only if you act now.

What Actually Changed

In January 2026, Microsoft disabled the creation of new alerts across all SharePoint Online tenants. Users who tried to set up an alert from a list or library saw banners directing them to the retirement notice. Now, in July 2026, the second phase takes effect: existing alerts are no longer supported, and Microsoft has stopped processing them. Any alert configured on a list, library, folder, file, or item will no longer trigger an email. That includes both “immediate” alerts (sent when something changes) and daily/weekly summary alerts.

The retirement does not affect on-premises SharePoint Server (2016, 2019) or hybrid environments where alerts are hosted on local servers. But for the vast majority of organizations using SharePoint Online, this is a hard stop.

What It Means for You

Everyday Users

If you set up an alert on a document library to know when a colleague updates a report, or on a task list to track assignments, those emails have stopped. You won’t get another “Alert Me” message. Look for banners that have been appearing for months warning of the change. Your next step depends on your organization’s plan. If your IT team has already migrated alerts, you might see new notifications coming from a different system. If not, you’ll need to speak with your admin to get a replacement set up.

In smaller teams with site-owner privileges, you can create SharePoint Rules yourself: navigate to your list or library, click “Integrate” > “Rules”, and build a simple notification trigger (e.g., when an item is created or modified). For anything beyond a basic email, your admin will likely configure a Power Automate flow.

IT Administrators and Power Users

This is a tenant-wide change that demands a structured response. The first step is not to fix individual alerts on the fly but to inventory the full scope of dependencies. Microsoft’s own Microsoft 365 Assessment tool includes a scanner specifically for SharePoint Alerts usage. Run it, generate the Power BI report, and sort alerts by site collection and web. Then prioritize: which alerts map to critical business processes? Which ones are tied to compliance, customer-facing operations, or approvals? Those are your overnight ticket generators.

Once identified, assign each alert to one of two replacements:

  • SharePoint Rules: Best for simple, single-condition notifications. A user or admin can set up a rule right on the list/library without leaving SharePoint. It’s ideal for “notify sales when this list changes” or “send an email when a new file is uploaded.”
  • Power Automate: For multi-step workflows, conditional logic, or integration with other services (Teams, approvals, external systems). Templates are available for common alert scenarios, but you’ll likely need to customize them. Power Automate flows require a license (most Microsoft 365 subscriptions include basic flow capabilities), and they should be owned by a service account to avoid breaking when the creator leaves the organization.
After migrating, test each replacement thoroughly—send a test notification to the intended recipients and confirm delivery. Document the new setup (which flow/rule replaces which alert, who maintains it, and the support contact). Finally, train your help desk. The key is to recognize that “my SharePoint alert stopped” now means “replace the alert,” not “troubleshoot an email issue.” A practical triage script should ask users for the SharePoint site, expected recipient, last known successful notification, and whether they saw a retirement banner.

How We Got Here

SharePoint Alerts debuted in the early 2000s as part of SharePoint’s document collaboration toolkit. They offered a no-code way for users to stay informed without building workflows. But as Microsoft shifted toward the cloud and Power Platform, alerts became a maintenance headache—limited customization, no central management, and a cumbersome backend that didn’t scale well in a modern cloud architecture.

Over the years, the company introduced alternatives: first SharePoint Designer workflows (now deprecated), then Microsoft Flow (rebranded Power Automate), and more recently, SharePoint Rules. In 2023, Microsoft began quietly steering users away from alerts by promoting Rules in new UI elements. The official retirement notice (MC1243549) appeared in late 2025, followed by in-app banners and email reminders throughout the first half of 2026.

This retirement aligns with a broader strategy to modernize SharePoint’s notification layer, combining it with the Power Platform’s automation engine and reducing legacy code. It also follows other retirements: Remote Event Receivers are slated for removal in July 2027, urging a similar shift to webhooks. For organizations, the lesson is clear: Microsoft 365’s feature lifecycle moves faster than ever, and admins must treat Message Center notifications as actionable deadlines, not just informational bulletins.

What to Do Now

For IT Teams

  1. Run the Assessment Tool. Download and execute the Microsoft 365 Assessment tool (available from Microsoft documentation). Select the “SharePoint Alerts Usage” scanner. It will produce a detailed inventory of every alert in your tenant.
  2. Analyze the Report. Open the Power BI report and filter by site collection. Look for alerts on high-impact sites: document centers, HR portals, finance libraries, operational dashboards.
  3. Engage Site Owners. For each affected site, contact the owners. Ask them to identify which alerts are critical and which can be retired. Many may have been set years ago and are no longer needed.
  4. Choose the Right Replacement. For each active alert, decide between a SharePoint Rule and a Power Automate flow (see comparison table below). Keep it simple: if the alert was a basic email, use a Rule. If it involved multiple recipients, conditions, or actions, use Power Automate.
  5. Implement and Test. Create the new notification, run it, and confirm that the right people receive it. Involve the original alert owner in testing.
  6. Document Everything. Record the new notification (what triggers it, who gets it, which service it relies on) in your knowledge base. Assign an owner for ongoing maintenance.
  7. **Communicate to