Two Governance Checks Worth Building Yourself After the CoE Starter Kit
Diesen Beitrag auf Deutsch lesen
Dependency checks before decommissioning and automatic inactive-owner detection for flows - two concrete ideas, regardless of which tool you use.
TL;DR
With the CoE Starter Kit gone, two concrete governance gaps are worth plugging yourself: before removing a SharePoint site or environment, check what flows, reports or agents actually depend on it; and for departed employees, auto-detect flows whose owners are no longer active and route reassignment to a designated admin instead of letting them fail silently.
Original by Matthias Einig, on Rencore. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: build both checks with Power Automate and the admin connectors alone, no separate governance product required, starting with a dependency lookup before decommissioning anything.
- Makers: benefit directly from the inactive-owner scan — a departed colleague’s flow gets rerouted to a designated admin instead of failing silently the next time it runs.
- Security/Compliance: push for the decommissioning check specifically, since removing a site or environment without checking dependent flows, reports, or agents is exactly the kind of gap that turns into an unplanned outage.