How to govern Power Automate
A step-by-step guide to governing Power Automate with Rencore: detect with 13 policies, review with 5 reports, and remediate with 2 automations.
Governing Power Automate means keeping its access, configuration, and lifecycle under continuous control rather than reacting after something breaks. Rencore governs Power Automate with 13 pre-built policies, 5 reports, and 2 automations, so teams can detect risk, review posture, and remediate with an audit trail. The steps below turn that coverage into a repeatable routine.
Steps
-
Inventory Power Automate
Connect Power Automate and let Rencore build a continuous inventory of its resources, owners, and configuration, so governance starts from what exists rather than a stale export.
-
Detect with policies
Turn on the pre-built policies that cover Power Automate to surface oversharing, sprawl, and misconfiguration on the first scan, before writing a single custom rule.
-
Review by owner and severity
Use the Power Automate reports to review findings by owner, category, and severity, and to share them with stakeholders who do not have a seat in the platform.
-
Remediate and automate
Apply automations to fix findings at scale, route sensitive changes through approvals, and keep every action reversible and logged for the audit trail.
Recommended Power Automate policies
Grounded in the Rencore catalog. See the full Power Automate catalog on the Power Automate connector page.
-
Long running Flows
Shows Flows that ran for a longer period (default 3 hours)
Severity: High -
Flows with many runs in last 30 days
Shows flows with run count exceeds defined value (default 100 runs)
Severity: Information -
Flows without runs
Shows Flows that have never been used. Warning: Flows with runs that happened before the first flow scan of Rencore Governance occurred will not be found.
Severity: Medium -
Stopped Flows
Shows Flows that have stopped
Severity: High -
Flows requiring a premium license
Shows Flows with premium connectors, premium actions or premium triggers (e.g. common data service)
Severity: High -
Flows with errors
Shows Flows that have failed runs and might not function as intended
Severity: Low -
New Flows
Shows Flows created in the last defined number of days (default 30 days)
Severity: Information -
Unused Flows
Shows Flows created more than 30 days ago that haven't run in more than 180 days
Severity: Information -
Stopped Flows Last Week with errors
Shows Flows that have stopped
Severity: High
