Microsoft Copilot
Take control of Power Automate flows before they sprawl
Rencore inventories the flows your people build, with their owners, state, runs, triggers, actions and connections. Thirteen policies find the flows that stopped, never ran, need a premium licence or have no owner, and owners can be told by email.
Flows quietly run the business, and nobody has a list of them
The questions are the ones you already ask of a Team or a SharePoint site: who built it, is it still needed, what does it connect to, what does it cost and who owns it now.
Which flows still work
Flows stop, fail or run for hours. Without a list, you hear about a stopped flow when the process that depends on it breaks.
Which flows nobody uses
Flows that never ran, or have not run in half a year, keep their connections and their owners' attention. They are clutter that nobody has been asked to retire.
What they cost
Flows with premium connectors, premium actions or premium triggers need a premium licence. The cost shows up at renewal unless someone looks.
Who owns them
A flow can be owned by users, groups or SharePoint lists, and shared with run-only users. When the owner is gone, nobody is responsible for it.
What Rencore sees and does in Power Automate
Every flow, with its owners, state and connections
Rencore inventories the Power Automate flows in your tenant with their environments, triggers, actions, connections and runs. Each flow is related to its creator, its owners and its run-only users, so a list of flows reads as a list of people to ask.
- Creator, owner users, owner groups and owner SharePoint lists
- State of the flow (started, stopped or suspended), last run and last modification
- Number of actions and connections used, with the triggers and runs behind them
- Ready-made segments for flows with 10 or more actions, flows with 3 or more connections and stopped flows
- A risk score on every flow, scanned daily by default
Thirteen policies over stopped, unused and costly flows
Policies run over the flow inventory as they run over Microsoft 365, each with a severity, a category and a trend. Several thresholds, such as the run time, the run count and the number of actions, start from a default.
- Stopped flows, and stopped flows from last week with errors (severity High)
- Long running flows, 3 hours by default (severity High), and flows that require a premium licence (severity High, category Costs)
- Flows without runs (Medium), and unused flows created more than 30 days ago with no run in more than 180 days (Information)
- Flows without owners, new flows in the last 30 days, flows with many runs and complex flows with 20 or more actions (Information)
- Flows with errors, flows that use a specific connector, and flows not shared with a given service account (Low)
Owners told by email, and access changed from one place
An automation can send one combined email to all owners of a flow, or one email per owner that addresses them by name. Owners and run-only access are changed with an action, and the Rencore Teams app can ask owners to review access on a schedule.
- Send a combined email to all owners of a flow
- Send one email per flow owner, addressed by first and last name
- Actions to add or remove an owner user, an owner group, a run-only user or a run-only group
- Access and sharing reviews for flows, started ad hoc or on a schedule and delegated to end users in the Rencore Teams app
What the Power Automate connector covers
What Rencore reads in Power Automate, and where the evidence is thinner than it looks.
One consenting account
Microsoft 365 does not let third parties scan Power Automate and Power Apps with application permissions. The scan runs under delegated permission, with a dedicated Power Platform Administrator account that is not a Global Administrator.
Runs before the first scan
The policy for flows without runs cannot find a flow whose runs all happened before the first Rencore scan.
Email and access actions
The actions available for Power Automate change who owns a flow and who can run it, and the automations send email to owners.
Apps, Automation and BI
Power Platform
Inventory Power Platform environments, apps and flows, rank them by risk and cost, and ask owners to act.
View the Power Platform connectorPower Apps
Inventory canvas apps with owner, sharing, connections and premium licence need, then fix ownership and access with policies and reviews.
View the Power Apps connectorPower BI
Prevent Power BI oversharing and sprawl, keep license costs in check and review access on a schedule.
View the Power BI connectorFabric
Inventory Fabric and Power BI workspaces, datasets, dataflows, pipelines and capacities, and find the unused and externally shared ones.
View the Fabric connectorPower Automate questions, answered
Which Power Automate objects does Rencore inventory?
Flows, with their environments, triggers, actions, connections and runs. Each flow carries its creator, owners, run-only users, state, last run, last modification and a risk score. Flows are scanned daily by default.
What does Rencore need to scan Power Automate?
A dedicated user account that gives the consent. Microsoft 365 does not allow third parties to connect to Power Automate and Power Apps with application permissions, so this is the one Rencore scanning application that runs on delegated permission, and that account is used during every scan. It needs the Power Platform Administrator role, assigned permanently, and it must not be a Global Administrator. Microsoft requires multi-factor authentication for administrators, so MFA has to be set up for it, or the permissions are revoked and the consent has to be given again.
Does Microsoft already cover this?
In part. The Power Platform admin center is Microsoft's own place to manage environments and flows. Microsoft stopped actively maintaining the Power Platform Center of Excellence Starter Kit in May 2026 and points customers to the admin center. Rencore does not replace either. It adds the flows in one inventory beside your apps, Teams and SharePoint sites, policies with a severity and a trend, and automations that tell the owners. Our comparison of Rencore and the CoE Starter Kit sets out the differences.
How does Rencore decide that a flow is unused?
The Unused Flows policy lists flows created more than 30 days ago that have not run in more than 180 days. The Flows without runs policy lists flows that have never run since the first Rencore scan. The long-running time (3 hours), the run count (100) and the number of actions (20) in the other policies are defaults as well.
How is Power Automate coverage licensed?
Power Automate is part of the Apps, Automation and BI module, an optional paid module on the Premium and Enterprise plans. The Professional plan does not include it. The pricing page has the full plan comparison.