Classic SharePoint alerts (the old "Alert me" feature) show up in real-world sites far more often than many admins expect. Every few weeks I meet business users who depend on them to keep track of changes in a document library or a list. This happens mostly in long-running SharePoint Online sites where Teams and automation never filled every gap. The SharePoint alerts retirement is official, though. From July 2025, creating new alerts is no longer possible, and by July 2026 all existing alerts stop sending notifications. It sounds like a gentle sunset, but quite a few users will be caught off guard if nobody manages it proactively.

The retirement removes the Alert me menu and stops every alert email

Admins have long seen classic alerts as a bit dated, but for many end users they are a lifeline for keeping up with activity. With the retirement, the "Alert me" menu disappears for good and all existing scheduled or event-based alert emails are disabled. In most tenants I review, usage is surprisingly widespread, often because anyone can set up an alert without admin approval. Microsoft's official timeline gives us until July 2026 to migrate and inform users. As usual, though, the real change has to happen well before the final cutoff if you want to avoid surprises.

Built-in rules, Power Automate and notifications can replace classic alerts

These are the options admins and users have to replace classic SharePoint alerts, from least to most flexible:

  • Simple rules in modern SharePoint lists and libraries ("Automate" → "Create a rule")
  • Power Automate flows using the SharePoint connector (actions and triggers explained)
  • Native OneDrive/SharePoint notifications (especially for sharing activity)

Which approach fits depends on what users need and how comfortable they are with the technology. Built-in rules cover basic "notify me on any change" scenarios, and non-technical users can configure them easily. Power Automate gives you much more room for filtering, custom messages and integration with Teams or other systems. It is a step up in complexity, though (and sometimes in licensing). Governance matters here too. If you haven't done so yet, review your Power Platform DLP policies. I cover this in more detail in [/blog/copilot-studio-governance-power-platform-dlp].

Pro tip: Many business users don't know that list and library rules exist now, let alone how to set them up. A bit of proactive communication, such as a quick mail with screenshots and step-by-step instructions, goes a long way toward a smoother transition with less frustration.

PnP PowerShell is the only practical way to find existing alerts

Often the biggest headache is simply working out where classic alerts are still in use. Microsoft doesn't offer a tenant-wide dashboard for this. In larger or older tenants I've seen hundreds of lingering alerts spread across dozens of sites. PnP PowerShell is the only practical inventory tool. The Get-PnPAlert cmdlet lists all alerts for a given site. You need the PnP PowerShell module installed and at least Site Collection Admin rights on each site.

Here is a sample command for PowerShell 7 (run it after Connect-PnPOnline):

# Requires PnP PowerShell module, Connect-PnPOnline first
Get-PnPAlert

I recommend running this check on your high-usage and business-critical sites, exporting the results and contacting the affected users directly. Early, personal communication makes a real difference, particularly for teams that have quietly relied on alerts for years. Also write down who was using what, because that helps you recommend the right alternative.

Direct communication makes the migration work in practice

This is the rough playbook I follow when I help organizations through the SharePoint alerts retirement:

  1. Inventory: list all active alerts per site with PnP PowerShell
  2. Identify and contact users or teams directly instead of relying on broadcast comms
  3. Recommend the best replacement (rules, Power Automate, native notifications)
  4. Offer support, for example short user guides, info sessions or Q&A clinics

In most cases a SharePoint rule or a simple Power Automate flow is enough. Microsoft has an overview of SharePoint and Power Automate integration if you want to dig deeper.

The diagram below shows the real-world transition from classic alerts to their modern replacements. In my experience the hardest part isn't technical. It's making sure nobody wakes up one day to find that updates they counted on have stopped arriving.

flowchart TD
    User["User"] --> AlertMe["'Alert me' feature"]
    AlertMe --> ClassicAlert["Classic SharePoint alert emails"]
    ClassicAlert -->|"Retirement July 2026"| NoAlert["No more alerts"]
    User --> ModernRules["SharePoint rules"]
    User --> PowerAutomate["Power Automate flow"]
    User --> Notification["OneDrive/SharePoint notification"]

Figure: Classic SharePoint alerts and their modern alternatives.

I recommend auditing now and communicating early to avoid the stress

The SharePoint alerts retirement is more than a technical footnote. It shows how many important business processes quietly depend on old workflows and habits. My advice is to audit now with PowerShell and talk directly to the users affected. Offer them hands-on help with setting up rules or Power Automate replacements. The earlier you start, the less disruption you'll see. Your users are also more likely to find that the modern options fit their needs, and some will find they work better than what they had before. If you wait for the retirement date, confusion and support tickets are guaranteed. I wouldn't go there.