SharePoint Alerts stopped working. This runs instead.
Microsoft turned off classic SharePoint Alerts in July 2026. AlertSentinel is the SPFx-native notification layer that replaces them — installed into your own tenant, on standard connectors, with no premium licensing. Built by Wickroom, on thirteen years of production SharePoint work.
30-day trial · $990 per tenant per year · unlimited users and sites
Built natively on the Microsoft 365 platform
Microsoft 365
SharePoint
SPFx
Teams
Power Platform
Azure
Two ways to put Wickroom to work.
One studio, one team, two offerings held to the same standard of care.
AlertSentinel
Notification infrastructure for SharePoint Online. The replacement for classic SharePoint Alerts, built on SPFx — your customer content stays in your tenant.
AlertSentinel: See AlertSentinelExpertise & custom apps
Architecture, SPFx engineering, and custom backend and frontend apps built on Microsoft 365. The hard parts, handled by a senior team.
Expertise & custom apps: See expertiseClassic Alerts went dark in July 2026. AlertSentinel is what runs after.
A notification layer for SharePoint Online, built on SPFx. No premium licensing, no Azure AD app registration, no flow sprawl — and no customer content leaving your tenant. The right signal, where your teams already work.
- Installs into modern SharePoint as an SPFx solution
- Standard connectors only — no premium Power Automate licensing
- Routing that sends the right alert to the right person
- A like-for-like path off classic Alerts, available now
See the replacement in action.
A short walkthrough of AlertSentinel as a tenant-wide replacement for classic SharePoint Alerts.
The alerts are already off. The processes that depended on them are not.
Classic SharePoint Alerts are gone
Microsoft removed classic SharePoint Alerts in July 2026. New alert creation was blocked across all tenants in January 2026, and remaining alerts stopped functioning at the July cutoff — including alerts users had extended manually. There is no built-in successor.
The failures are quiet
Nobody gets an error when an alert stops firing. Approvals sit unread, document reviews go unnoticed, and the ticket that eventually arrives says "SharePoint stopped emailing me." The dependencies nobody documented are the ones that surface last.
Rebuilding it yourself is a heavy lift
Reconstructing alerts as custom flows means per-site maintenance, throttling limits, and often premium licensing. A third-party service usually means your content leaving the tenant. AlertSentinel ships the notification layer for you, inside Microsoft 365.
Built for how SharePoint actually works.
AlertSentinel does one job well: dependable notifications, inside the platform your teams already use.
SPFx-native
Installs into modern SharePoint as a single SPFx solution. No external services to host and no Azure AD app registration. Your documents, list items, and alert content are processed and stored entirely inside your tenant. The only outbound call is a periodic license check that transmits your tenant ID and nothing else.
No flow sprawl
Three tenant-wide flows on Standard connectors cover every site - no premium licensing, no per-site flows to maintain. Alert logic lives inside SharePoint where your content already is.
Routing that fits
Immediate, daily, or weekly digests. Delivery by email, Microsoft Teams, or the in-app notification bell - scoped to a list, a library, or a single item.
Familiar by design
Alerts are created from the SharePoint command bar and the item menu — the same gesture your users already knew. A like-for-like replacement means the retraining cost is close to zero.
One place to manage every alert.
A clear dashboard, per-site and per-user views, and a focused form for creating alerts.
It lives where your team already works.
AlertSentinel adds itself to the SharePoint command bar and item menu. Setting an alert is the same gesture people already know, with none of the classic limitations.
- Create an alert straight from the list command bar
- Alert on a single item from its context menu
- Manage every subscription from one place
SharePoint Alerts retirement — questions
Did SharePoint Alerts really stop working?
Yes. Microsoft fully retired classic SharePoint Alerts in mid-July 2026. Alert creation had already been blocked tenant-wide since January 2026, and existing alerts — including manually extended ones — stopped firing at the July cutoff.
My SharePoint alerts stopped sending emails. Is that the retirement?
Most likely. If notifications you configured through "Alert me" went silent around July 2026 with no error and no configuration change, that is the retirement rather than a permissions or mail-flow problem.
What replaces SharePoint Alerts?
Microsoft points to SharePoint Rules and Power Automate. Both work for simple cases but neither is a like-for-like replacement: Rules are narrow, and Power Automate means building and maintaining flows per site. AlertSentinel is an SPFx-native alerts layer built specifically to take over the role classic Alerts played.
Does AlertSentinel need premium Power Automate licensing?
No. It runs on three tenant-wide flows using standard connectors only.
Does AlertSentinel require an Azure AD app registration?
No. It installs as a single SPFx solution, with no external services for you to host.
Does my content leave my tenant?
No. Documents, list items, and alert content are processed and stored inside your tenant. The only outbound call is a periodic license check carrying your tenant ID.
Can I try it before buying?
Yes. Installing AlertSentinel from AppSource starts a 30-day trial automatically — no separate request or manual approval needed.
How is it priced?
$990 per tenant per year: unlimited users, unlimited sites, one invoice. No per-seat counting.
Get your notifications back.
$990 per tenant per year — unlimited users, unlimited sites, one invoice. No per-seat licensing to reconcile.
30-day trial · $990 per tenant per year · unlimited users and sites
When the template will not carry the load, we build the rest.
Wickroom is the senior Microsoft 365 team behind the architecture, the SPFx, and the custom apps that sit on top of the platform. Six things we do well, listed plainly.
- Information architectureHub structure, content types, governance
- SPFx engineeringWeb parts, extensions, command bar
- Custom apps on M365TypeScript, React, Microsoft Graph
- Workflow automationPower Platform and Graph services
- Governance & lifecycleOwnership models, retention, audit
- Migration & modernizationOff legacy, onto something maintainable
When the platform alone is not enough, we build.
Some problems do not fit a list, a flow, or an out-of-the-box web part. For those, Wickroom designs and builds custom backend services and frontend apps that sit on top of Microsoft 365 and feel native to it.
- Front ends in SPFx or standalone apps, built with TypeScript and React
- Backends and APIs that talk to SharePoint, Teams, and Microsoft Graph
- Authentication and permissions that respect your existing tenant model
Tools we build with
A structured engagement, not a retainer treadmill.
Four steps, each with a clear output, so you always know where the work stands.
Discovery call
A focused conversation about your environment, your constraints, and what you are actually trying to fix.
Architecture review
A structured look at your current SharePoint estate, with findings and a recommended direction.
Scoped engagement
A clear statement of work: defined deliverables, a timeline, and a fixed scope. No retainer treadmill.
Knowledge transfer
Documentation and a handover so your team owns and can maintain what was built.
Talk to the person doing the work.
No account layer between you and the work; you are on the call with the person who architects it.
Senior craft, at modern speed.
Two beliefs, in this order. The first is what most studios skip; the second is what most senior architects refuse to do.
Decided before it is built
Hub structure, content types, permissions, and the ownership model are written down before any web part is wired up. That document is what keeps a SharePoint estate coherent two years later.
Built faster, not looser
Modern tooling and a senior team mean fewer meetings and faster delivery. The shortcuts we will not take are the ones around testing, accessibility, and the handover document your team owns the day we leave.
Arrioph
Microsoft 365 modernization studio · Casablanca
Wickroom is operated by Arrioph, a Microsoft 365 modernization studio in Casablanca. We build AlertSentinel and take on senior SharePoint and SPFx engineering work, backed by over a decade of hands-on production experience.
The standard, in one line.
Build it so the next person can understand it, and so it still works the day after you stop looking at it.
Tell us what you are running.
A short note about your Microsoft 365 environment is enough to start. We reply within two business days, from a senior engineer, not a sales desk.