How can I set up the Loop Table Rules automation shown in Microsoft’s official video?

Hi @anastasia trushina

Based on the information you provided, I understand that: you watched the official Microsoft 365 video demonstrating Table Rules in Loop (trigger an action such as Notify in Loop, Teams message, or email based on a table condition), and you now want to build a similar automation on your own task-tracking table that (1) monitors Status and Due date, (2) detects incomplete/overdue tasks, (3) identifies the assigned person, and (4) automatically sends that person a reminder. You’d also like to confirm whether the feature is still available, whether it’s fully rolled out, and what licensing/admin prerequisites apply to your tenant.

1. Current availability, Table Rules still exist

The feature shown in the video is still available and is accessible from loop.microsoft.com: select a table-based component (tables, task lists, voting tables, and board-based components are supported), open the ellipses (…) menu, choose Table rules, then set your trigger, condition, and action. One important limitation to be aware of: you can’t create rules on a table component inside Teams, Outlook, or other host applications, rules can only be created in the browser (loop.microsoft.com) or the Loop PWA.

2. How to configure your reminder scenario

-Open your task table in the Loop web app and make sure it has: a Status column (choice type, e.g., Not started / In progress / Done), a Due date column (date type), and a Person/Assigned to column.

-Click … on the table > Rules > New rule.

Build the condition, e.g., When Status - Done combined with a date condition on the Due date column. As a practical example from the community, a rule can be configured as: When “Status” “Equals” a value, then “Send a message in a Teams channel”.

-Choose the action: Notify in Loop, Send a Teams message, or Send an email.

-For “send a reminder to the responsible person,” use the dynamic content from the row so the recipient is pulled from the Person column. Note that the rule creation screen offers email and Teams options, but you’re not limited to those defaults, each rule opens in the Power Automate flow interface where you can fully customize the action. This is exactly where you would insert the row’s assignee as the To/recipient field.

-For overdue detection specifically: the built-in rule triggers fire on table changes/conditions. If you want a daily sweep that catches tasks that silently pass their due date, the common approach is to use a scheduled rule/flow that runs daily to evaluate due dates and send reminders (email or Teams) to the task owner, optionally configuring how far in advance reminders go out e.g., 1 day, 3 days, or 1 week before the due date. You can create the rule in Loop first, then edit the generated flow in Power Automate to add a recurrence trigger.

3. Licensing, admin settings, and permissions

-Each automation rule in Loop corresponds to a flow in Power Automate, and limits on rule creation/execution are determined by your Power Automate license. The prerequisites are: a Power Automate license, Loop connectors enabled in your organization’s DLP policy, and the feature is available to Microsoft 365 subscribers. In practice, the Power Automate rights included with Microsoft 365/Office 365 plans (standard connectors) are sufficient for Teams/Outlook notification actions.

-The lighter-weight Notify in Loop action is different: in-app notifications were added precisely because the original email/Teams rules required an active Power Automate license, and in-app notifications are available to all users of the Loop app.

-If the Rules option doesn’t appear for you, the typical checklist (seen in similar cases, including tenants where all users already have E5 licenses) is: (a) confirm Loop is enabled for your tenant via the Cloud Policy service in the M365 admin ecosystem, (b) make sure you’re in loop.microsoft.com rather than an embedded component, (c) ask your admin to verify the DLP policy allows Loop connectors, and (d) confirm your account has an Exchange Online mailbox.

4. One maintenance caveat

Disabling a rule in Loop does not stop the corresponding flow in the Power Automate portal, while deleting a rule in Loop also removes the flow, worth knowing when you test and iterate.

If the Rules button is still missing after checking the items in section 3, could you share (a) your license type, (b) whether you’re using loop.microsoft.com or an embedded component, and (c) whether your admin has restricted Power Platform connectors? That will help narrow it down further.

Hope this helps, if it resolves your question, please mark it as the answer so others can benefit as well.