Flows not shared with specific service account

Last updated Oct 17, 2026 Policies

AI summary

Identify Power Automate flows that lack your organization's service account as a co-owner. Flows with only one owner become difficult to maintain when that person is unavailable or leaves; configure the policy with your service account email and add it as a co-owner to the listed flows.

Severity: Low Operation Generally available

What it detects

Shows all Flows that are not shared with a specified service account (adjust account in Policy).

Why it matters

A flow that only one person owns cannot be maintained when that person is away or leaves. Many organizations add a service account as co-owner of every business flow so that IT can take over. The template uses a placeholder address: set the account your organization uses, then add it to the flows this policy lists.

The rule

Every Flow that has no Owner Users where User Email equals '[email protected]'

In Rencore Governance

Details

Applies to	Flow
Connector	Power Automate
Severity	Low
Category	Operation
Recommended	No
Recommended automation	None
License type	Standard

Other policies that check Flow objects:

Flows with many runs in last 30 days (Information)
Flows requiring a premium license (High)
Complex flows (Information)
Long running flows (High)
Flows with errors (Low)
Stopped flows (High)
Flows without runs (Medium)
New flows (Information)
Flows that use a specific connector (Low)
Unused flows (Information)
Flows without owners (Information)
Stopped flows last week with errors (High)

Frequently asked questions

What does the flows not shared with specific service account policy detect?

The Flows not shared with specific service account policy shows all Flows that are not shared with a specified service account (adjust account in Policy).

Which objects does the flows not shared with specific service account policy check?

The Flows not shared with specific service account policy checks Flow objects from the Power Automate inventory and reports each one that matches its rule as a violation.

How severe is a violation of the flows not shared with specific service account policy?

Violations of the Flows not shared with specific service account policy have Low severity. The policy is in the Operation category.

Which module includes the flows not shared with specific service account policy?

The Flows not shared with specific service account policy comes with the Power Automate connector in the Apps, Automation & BI module of Rencore Governance, an add-on module on the Premium and Enterprise Plans.

Was this page helpful?