PathixDataverse Forensics

← All 40 findings

Identity lifecycle & offboarding

A plugin step set to run as a disabled user

Severity High

What it is

Plugin step impersonates a disabled user account.

Why it matters

A step set to always run as a disabled user fails every time it fires, because Dataverse cannot build a run-as context for a disabled principal.

Find it yourself

In the Plugin Registration Tool, check the run-as user on every step. Steps with an impersonating user set are worth listing, then cross-reference those users against disabled accounts. This one fails loudly at runtime, so it is often already a known problem without anyone having identified the cause.

How to fix it

Repoint the impersonation to an active service account, or remove it so the step runs as the caller.

Related controls

SOC 2 CC6.2ISO 27001 A.5.18NIST AC-2 / PS-4

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.

Pathix checks this across every environment you scan, along with 39 other conditions. Self-hosted in your own Azure, read-only, metadata-only.

More in identity lifecycle & offboarding

← Back to all 40 findings

Pathix

Forensics for Dynamics 365 and the Dataverse.

See it on sample data →
USE CASES
CAPABILITIES
  • What we check
  • Dataverse MCPsoon
  • Dependency analysissoon
  • Migration impactsoon
PRODUCT
COMPANY
© 2026 Pathix · self-hosted · metadata-onlyNot affiliated with Microsoft. Dynamics 365, Dataverse, and Power Platform are trademarks of Microsoft Corporation.