Inspect overlapping configuration profile payloads with evidence instead of guesswork.

What the scan can confirm

• Two profiles share one or more payload families.
• Comparable keys inside supported payloads were inspected directly.
• Conflicting values were observed for those comparable keys.
• Some scope overlap paths can be confirmed from direct devices, group membership, or all-computers scope.

How results are classified

• Confirmed Conflict means conflicting payload key values were observed directly in both profiles.
• Potential means payload overlap exists, but the app could not prove a conflicting effective setting from the supported comparison model.
• Allowed means the shared payload is known to allow duplicate instances or the compared configuration matched.
• Unknown remains possible when scope overlap could not be resolved far enough to prove or rule out a real shared target set.

Scope overlap handling

Scope overlap is evaluated separately from payload comparison. The app can show confirmed device intersections, fleet-wide overlap, fleet-wide partial overlap, or insufficient overlap evidence depending on how much of the targeting path Jamf exposes in the current scan.

What the detail view shows

• Both profile names and their scope context
• Shared payloads and the disposition of each payload
• Comparable keys inspected for supported payload types
• Any conflicting effective settings that were directly observed
• Limitations that affected scope or payload certainty

Important limits

• The feature does real payload comparison where supported, but it is not a universal device-side precedence simulator.
• Jamf scope resolution can still be partial when group, department, or building membership cannot be fully expanded in the current scan.
• Apple does not document deterministic winners for every overlapping payload family, so “review” still matters after a confirmed finding.