Recommended Automations

104 pre-built automations across 38 connectors, remediation, approval, archival, deletion, notification. Recommended ones activate by default and close the loop from policy violation to fix.

Published For IT Admin, M365 Product Owner

Recommended Automations are Rencore's pre-built remediation workflows. The catalog ships 104 automations across 38 connectors, plus 208 built-in actions for single-object operations. Each automation has a category, criticality level, and an is_recommended flag. The recommended subset activates by default and pairs with the recommended policies, detect a violation, run the automation, close the loop without manual cleanup.

What gets shipped

Across 38 connectors Rencore ships 104 automations and 208 built-in actions. Automations are multi-step workflows (detect violation → notify owner → wait for response → remediate or escalate). Built-in actions are single-object operations triggered from a violation row or a segment view (“delete N8N project”, “archive Claude workspace”).

The recommended subset of automations is the closed-loop pair for the recommended policies. Where a recommended policy detects an anonymous sharing link, the matching recommended automation removes it after owner notification. Where a recommended policy flags an unrotated API key, the matching automation requests rotation through an approval workflow.

How they run

Automations execute on the platform’s V3 engine, branching logic, conditional steps, multi-step approvals, dynamic forms, retry handling. Triggers include policy violations, scheduled runs, or manual initiation from a dashboard or segment.

Every automation produces an audit trail: who triggered it, what was changed, when it ran, and whether it succeeded. Audit data feeds the same reports and SIEM streams as policies, so governance teams can show evidence of action, not just evidence of monitoring.

When to customize

Recommended automations cover the common remediation patterns. For organization-specific workflows, onboarding flows, provisioning rules with custom naming standards, integration with your ITSM, use the workflow builder to author custom automations. Both pre-built and custom automations use the same engine and the same audit pipeline.

Frequently asked questions

Can I build custom automations in Rencore?
Yes. Rencore's V3 automation engine supports custom workflows with branching logic, conditional steps, multi-step approvals, and multiple action types. You can trigger automations from policy violations, schedules, or manual initiation. Built-in integrations include ServiceNow, webhooks, Power Automate, and Copilot Studio for extending governance into other systems.
What is Rencore governance?
Rencore governance is a SaaS platform that continuously monitors your Microsoft 365 tenant for policy violations, configuration drift, and security risks across SharePoint, Teams, Power Platform, Copilot, and AI Agents. It automates compliance evidence collection, surfaces oversharing and sprawl, and provides actionable remediation workflows, reducing manual audit effort by up to 80%.
How do Rencore policies work?
Rencore ships with hundreds of pre-built policies that detect governance violations across every connector, oversharing, sprawl, cost overruns, security risks, and compliance gaps. Policies run on a continuous schedule, evaluate each discovered object against configurable rules, and flag violations with severity (High, Medium, Low), category, and a recommended action.

Trusted by

MAPALBAMVille de LuxembourgWACKERGRUNDFOSAMGENOsramLufthansaHoneywellThyssenKruppSunrisePattern

See Rencore in your tenant

Connect your environment in minutes and surface the governance findings that matter on day one.