A flow using a retired or deprecated Dataverse connector
What it is
Connection reference uses a retired or deprecated connector.
Why it matters
Flows on the retired Dynamics 365 connector no longer run; flows on the deprecated legacy Dataverse connector work on borrowed time with no fixes.
Find it yourself
Read the connector id on each connection reference and compare it against the current Dataverse connector. The retired Dynamics 365 connector and the legacy Dataverse connector are the two to look for, and flows bound to them fail differently: one stops, one degrades.
How to fix it
Recreate the connection on the current Dataverse connector and rebind each flow.
Not a security finding
This one is environment health, so it carries a plain label and no control mapping. Presenting an operational gap as a security finding would make the real security findings harder to trust, so we keep the two apart.
Pathix checks this across every environment you scan, along with 71 other conditions. Self-hosted in your own Azure, read-only, metadata-only.