A flow or workflow owned by a disabled user
What it is
Enabled automation is owned by a disabled user account.
Why it matters
A live flow or workflow owned by a disabled account authenticates and runs under that owner, so it stalls or refuses reactivation, and the process it drove silently stops.
Find it yourself
List active workflows and flows with their owner, then cross-reference the owners against disabled users. Worth running whenever an incident timeline lines up with somebody's last day, because the failure usually surfaces months after the departure.
How to fix it
Reassign to a service account, re-test its connections, and add reassignment to offboarding.
Related controls
These mappings are indicative. Pathix detects a condition relevant to a control. It does not certify your compliance, and a finding is not an audit opinion. You stay responsible for your control environment.
CMMC relevance
This condition produces evidence for PS.L2-3.9.2 (Level 2: protect systems containing CUI during and after personnel actions such as termination), for the Dataverse system in your assessment scope. A flow keeps running in its owner's context after that owner is disabled. The personnel action removed the person and left their access executing on a schedule.
Pathix is not a CMMC compliance platform. It does not assess the rest of your environment, mappings are indicative, and assessment outcomes rest with your assessor.
Pathix checks this across every environment you scan, along with 71 other conditions. Self-hosted in your own Azure, read-only, metadata-only.