PathixDataverse Forensics

← All 40 findings

Identity lifecycle & offboarding

A disabled user who still has records shared with them

Severity High

What it is

Disabled user account still holds manually shared records.

Why it matters

Disabling a user revokes neither roles nor record shares, and shares have no surface in the user UI, so they survive careful offboarding. Re-enable the account and the shared records are reachable again.

Find it yourself

Manual shares live in the principalobjectaccess table, which has no user-interface surface at all. You need a direct query against it, filtered to disabled principals. The absence of any screen is exactly why this survives offboarding that otherwise went well.

How to fix it

Revoke manual shares alongside role removal, or reassign the records to a team.

Related controls

SOC 2 CC6.2ISO 27001 A.5.18NIST AC-2 / AC-21 / 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.