Digest flows give SharePoint alert users one subscribe path
Reviewed by Helen Jones
A 4 September walkthrough by Laura Rogers details a user-managed replacement for retired SharePoint Alerts. It uses the preview Recurring digest of updates trigger as a template, a subscription list, and cloned flows for individual lists or libraries; digest recipients still need permission to open the linked content.
Retiring an alert is simpler than replacing the expectation behind it. Teams still need a way for people to opt into updates without asking IT to build a one-off notification every time a library becomes important. This pattern puts the subscription choice in a SharePoint list while keeping the reporting flow repeatable. It also exposes the operational trade-off: a tenant can reduce missed-update tickets, but must own flow sprawl, subscriber removal, permissions and the preview trigger’s limitations.
Analysis
Choose one high-value library with known alert users. Build the digest template in a solution, keep a subscription list, test permissions and unsubscribe handling, then decide whether the support benefit justifies a flow for each list or library.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Digest flows give SharePoint alert users one subscribe path", Collab365 Spaces. 1 source referenced.