The sharepoint alerts retirement is one of the most overlooked changes hitting Microsoft 365 tenants right now. Microsoft has confirmed through its Message Center that classic SharePoint alerts will be retired, and many organizations still rely on them daily for document and list notifications. The problem: thousands of teams will lose their notification workflows silently if they don't act.
This guide covers exactly what's changing, how to find your existing alerts, and the fastest ways to rebuild them using Power Automate before the deadline arrives.
What the SharePoint Alerts Retirement Actually Means
The retirement means Microsoft is removing the legacy alerting feature that lets users get emails when documents or list items change. Microsoft's Message Center announcement explains that tenants should migrate alert-based workflows to Power Automate before the feature is fully removed. Understanding the sharepoint alerts retirement timeline is critical because it affects every user-created notification across your tenant.
This isn't a minor UI tweak. Alerts built by end users — sometimes years ago — will simply stop sending email. There's no automatic conversion tool that rebuilds every alert as a flow, so each team must inventory what they use and replace it. The sharepoint alerts retirement demands proactive planning rather than reactive scrambling.
Microsoft points tenants to the Microsoft 365 Roadmap for rollout timing, which lands in phases rather than all at once. That phased approach gives you a window to plan, but only if you start now. Treat the sharepoint alerts retirement as a project with a deadline, not a distant rumor.
How to apply this: Check your admin Message Center today and note the exact retirement dates announced for your tenant.
Why Microsoft Is Retiring Classic Alerts
Classic alerts run on aging infrastructure that predates modern Power Platform services. They're hard to audit, hard to govern, and they generate the kind of unmanaged email traffic that IT teams struggle to control. The sharepoint alerts retirement is Microsoft's answer to years of accumulated technical debt around unmanaged notifications.
The retirement also fits Microsoft's broader push to consolidate automation into the Power Automate platform. Flows offer richer logic — conditions, approvals, Teams notifications — that old alerts never supported. With the sharepoint alerts retirement underway, organizations finally get a reason to modernize their notification strategy.
A common scenario: a records team relies on alerts to know when contracts hit a "pending review" status. Under the old system, nobody in IT could see those alerts existed. Under Power Automate, the same notification becomes visible, documented, and governed. The sharepoint alerts retirement exposes exactly these hidden dependencies.
How to apply this: Ask your IT department whether they have a governance policy for tenant-level flows before you rebuild anything.
How to Find Every Alert in Your Tenant
Before you can replace alerts, you need to know what exists. Microsoft has made alert discovery difficult because alerts were user-created across countless sites and libraries. The sharepoint alerts retirement makes this inventory step urgent — once alerts disappear, you lose the ability to see what was there.
Your options include:
- Ask site owners to check Site Settings → Manage Alerts on each site they own
- Use PowerShell with PnP to enumerate alerts across site collections
- Review SharePoint admin center reports for usage signals
- Ask users directly which notifications they actually read
Most enterprises report that a large share of discovered alerts are stale — created for projects that ended long ago. Don't migrate everything; prune first. The sharepoint alerts retirement is actually a forcing function for cleanup.
How to apply this: Run an alert inventory this week and tag each alert as "migrate," "delete," or "unsure."
The Migration Path: Rebuilding Alerts in Power Automate
Power Automate is Microsoft's designated replacement, and each old alert maps to a simple automated flow. The core pattern uses a trigger — When an item is created or modified — followed by an email or Teams action. Approaching the sharepoint alerts retirement with a clear migration path turns a disruption into an upgrade.
Here's the basic rebuild process:
- Open Power Automate and choose Create → Automated cloud flow
- Select the SharePoint trigger matching your old alert (created, modified, or deleted)
- Point the trigger at the specific site, list, or library
- Add a Send an email (V2) or Post message in a chat or channel action
- Add a condition if your old alert only fired for certain changes
One flow can replace an alert for an entire library, and you can set trigger conditions so it only runs on meaningful changes — something classic alerts never did well. The sharepoint alerts retirement gives you permission to design notifications properly this time.
How to apply this: Pick your three most business-critical alerts and rebuild them in Power Automate this week as a pilot.
Alerts Retirement Checklist: Old vs. New Compared
Use this table to compare what you're losing with what you gain, and what to verify during migration. The sharepoint alerts retirement comparison below helps you make informed decisions about each notification you migrate.
| Feature | Classic Alerts | Power Automate Flows | Action to take |
|---|---|---|---|
| Setup effort | One click | 5–10 minutes | Start with simple alerts |
| Conditions/filtering | Very limited | Full condition logic | Add trigger conditions |
| Governance visibility | Almost none | Admin-reportable | Register flows with IT |
| Teams notifications | No | Yes | Choose Teams over email |
| Bulk creation | Per-user only | Templates/deployment | Use flow templates |
The biggest practical difference is visibility: flows are admin-manageable, which is exactly why Microsoft favors them. The sharepoint alerts retirement ultimately improves your notification governance.
How to apply this: Score each alert you found against this table and prioritize the ones where filtering matters.
How to Prepare Your Users Before the Cutoff
Communication is the step most tenants skip, and it's the one that causes the most pain. When alerts die, users assume email broke — not SharePoint. A short announcement prevents weeks of helpdesk tickets. The sharepoint alerts retirement needs a user-facing communication plan just as much as a technical migration plan.
Your rollout should include:
- A tenant-wide message explaining the retirement dates and the reason
- A one-page guide showing how users request a flow instead of an alert
- A support channel for teams with complex alert setups
- A deadline for site owners to confirm their alerts are migrated
Also decide who builds replacements. Power users can handle simple flows via self-service, while IT should own anything touching sensitive libraries. Preparing users for the sharepoint alerts retirement means they'll see it as an improvement, not an outage.
How to apply this: Draft your user announcement now and schedule it at least 30 days before your tenant's retirement date.
Frequently Asked Questions About sharepoint alerts retirement
When exactly will SharePoint alerts stop working?
Microsoft is rolling out the retirement in phases by tenant, so your exact date comes from the Message Center post rather than a single global deadline. Some organizations will see alerts stop earlier than others.
Check the Health → Message center section of your Microsoft 365 admin center for your tenant-specific schedule, and treat the sharepoint alerts retirement timeline as firm once it's posted for you.
Will my existing alerts convert automatically to Power Automate?
No — there is no automatic conversion tool. Microsoft provides guidance and flow templates, but someone must manually rebuild each alert as a flow. The exception is very simple alerts, which you can recreate in under ten minutes. Complex alerts with custom conditions need more careful redesign. The sharepoint alerts retirement requires manual effort, so budget time accordingly.
Do Teams and OneDrive notifications change too?
This retirement targets classic SharePoint alerts specifically. Microsoft Teams channel notifications and OneDrive "follow" notifications are separate systems. However, if you used alerts on files stored in a Teams-connected document library, those alerts are affected. Rebuild them as flows or use native Teams activity settings instead. The sharepoint alerts retirement scope is narrower than many assume.
Can I still create new alerts while the retirement is pending?
In most tenants, yes — until Microsoft flips the switch for your region. But creating new alerts now is wasted effort since they'll be removed anyway. Direct anyone asking how to set up notifications toward Power Automate flows so nothing needs rework later. With the sharepoint alerts retirement approaching, every new alert is throwaway work.
What happens to alert data and history after retirement?
Classic alerts don't store meaningful history — they just fire emails — so nothing substantive is lost. What matters is documenting which alerts existed and what they notified people about, before they disappear. Export your inventory to a list or file so no notification requirement slips through the cracks.
The sharepoint alerts retirement won't erase data, only the notification mechanism itself.
Conclusion: Your Next Steps Before the Deadline
The sharepoint alerts retirement doesn't have to disrupt your organization if you treat it as a small migration project rather than a surprise outage.
Key takeaways:
- Inventory first — find every alert in your tenant before building anything
- Prune ruthlessly — stale alerts outnumber useful ones in most organizations
- Rebuild in Power Automate — flows offer better filtering, Teams delivery, and IT visibility
- Communicate early — announce changes to users well before your retirement date
Start today by opening your Microsoft 365 admin center, reading the Message Center post for your tenant's exact dates, and launching your alert inventory. The teams that prepare now will feel nothing when the feature switches off. The sharepoint alerts retirement is manageable — but only with action.
