The last post covered how to inventory what SharePoint Alerts exist across a tenant before they stop working in July 2026. This one covers what to actually do with that inventory, because "migrate to Power Automate" isn't quite the right instruction. Power Automate is one tool, not the only one, and reaching for it by default is often more than the job needs.
Alerts had one job: notify you automatically when something changed. Microsoft didn't build a single replacement for that job, they gave you three tools, and only one of them isn't new. Power Automate has been the engine behind SharePoint automation for years, Rules and Quick Steps are newer, simpler front ends built on top of that same engine, designed so that most people never need to open the full flow canvas at all.
The point of this post is picking the right tool for each alert in your inventory.
The three tools
Rules. Automatic, event-triggered, narrow. This is the direct alerts replacement, and it's genuinely simple, a sentence-builder interface, no flow canvas, no connectors to configure. It runs on Power Automate under the hood, but you never see that.
Quick Steps. Manual, button-triggered, broader. Where a Rule fires automatically when something happens, a Quick Step waits for someone to select an item and click a button. In exchange for giving up automatic triggering, you get more action types, starting a Teams chat, moving or copying a file, not just email and setting a value.
Power Automate. The original tool, and still the one with no ceiling. Full conditional logic, any trigger, any connector, any external system. Both Rules and Quick Steps can hand off to a flow the moment they hit their own limits, "execute a flow" is a first-class action in both, so you're never locked out of Power Automate's power just because you started with the simpler tools.
In my tenant, both Rules and Quick Steps live under the Integrate menu on any list or library. Worth checking where they sit in yours, menu naming and placement have shifted around a bit as Microsoft has rolled this out.
Rules, in practice
From the Integrate menu, creating a Rule starts with a trigger:
- A file or metadata is modified
- A new file is added
- A file is deleted
- A date approaches
Pick a trigger, and the rest reads like a sentence: "When a new file is added, always, send an email to [recipient]," with an optional custom message. The "always" can also be swapped for a condition, "when a file is modified, if [column] changes and the new value [is anything / is (a specific value) / is one of / is not], send an email to [recipient]," so a Rule doesn't have to fire on every single change, just the ones that actually matter. That's the entire configuration either way, no flow steps, no expression editor.
The honest limitations, worth knowing before you commit to Rules as the answer:
- Only two actions are available: send an email, or set a column value. Anything else, a Teams chat, moving a file, calling something external, is Quick Steps or Power Automate territory.
- Notifications are immediate only. There's no daily or weekly digest option, so any alert in your inventory with Frequency: Daily or Frequency: Weekly can't be a straight Rules swap.
- Not available on Site Pages libraries.
- A 15-rule limit per list or library.
For a simple "notify me when something changes" alert with no digest requirement, Rules is very often the entire answer, and it's the fastest tool to reach for.
Quick Steps, in practice
Quick Steps solve a different problem: not "notify me automatically," but "give me a one-click way to act on something I'm already looking at."
Also found under Integrate, Quick Steps come in two flavours:
For selected files. Once you select one or more items, the Quick Step appears in the Integrate menu and the more options menu. Available actions: draft an email, start a Teams chat, set a value, execute a flow, move a file or folder, copy a file or folder.
For the current document library. Runs against the whole library rather than a selection, currently limited to executing a flow.
The "set a value" option builds the same way Rules do, a sentence: "Show a command that will, for each selected file or folder, set the value in [column name] to [column value]," with a name for the Quick Step and an option to control when it's shown.
Quick Steps has also recently become available as a column type in its own right, not just a button you click after selecting items. Added as a column on a list or library, it shows as a small button directly in that row of the view, letting users trigger an email, a Teams chat, an approval, or a flow without selecting the item first and digging into a separate menu, built using the same sentence-builder style as Rules. The button can also be shown or hidden conditionally, so it only appears on rows where it's actually relevant, rather than cluttering every row in the view (this is also worth knowing if you've previously built custom action buttons using JSON column formatting, Quick Steps as a column type removes some of that dependency on hand-written JSON for straightforward cases).
Where Quick Steps genuinely earns its place next to Rules: anything that needs to be a deliberate, one-off human action rather than an automatic response to an event. A "flag this document for review and notify the reviewer" button behaves very differently from an automatic alert firing on every single change, and for a lot of real workflows, the deliberate version is what people actually wanted from Alerts in the first place, not true automation, just a faster way to do something they were already doing manually.
When it's Power Automate
Neither Rules nor Quick Steps can do the following, and if your inventory has alerts that need any of these, Power Automate is the right tool, not a fallback for when the simpler ones fail:
- Digest-style notifications (daily or weekly summaries rather than per-event)
- Conditional logic beyond a single field comparison
- Approval chains
- Anything reaching outside SharePoint, another system, a database, an external API
- Multi-step sequences (do A, then B, then C depending on the outcome of A)
And because Rules and Quick Steps can both hand off to a flow, you don't have to choose Power Automate for an entire workflow just because one step in it needs real logic. Build the simple parts as a Rule or Quick Step, and drop into Power Automate only for the piece that actually needs it.
Using this against your inventory
If you ran the alert inventory script from the last post, the ActionNeeded column on each item is exactly what this toolbox is for. A rough sorting pass:
- Single condition, immediate notification, one recipient → Rules
- Daily or weekly frequency → Power Automate (Rules can't do digests)
- The alert was really a "someone should look at this and act" reminder, not a passive notification → consider whether a Quick Step is a better fit than automating it at all
- Multiple conditions, approvals, or anything touching a system outside SharePoint → Power Automate
Worth doing this sorting with the alert's owner, not for them. The inventory tells you what exists, this toolbox tells you the options available, but only the person who relied on the original alert knows which tool actually matches what they needed it for.
Need help sorting your SharePoint Alerts inventory into Rules, Quick Steps, and Power Automate?