Endpoint & MDM
Fleet, patching, device posture, and management signals across employee endpoints.
- Jamf
- Microsoft Intune
- Kandji
- VMware Workspace ONE
- Automox
- Tanium
Real endpoint & mdm evidence, as the report renders it
Top-confidence claims from our public Bentley Systems sample profile — same renderer, same provenance badges customers see. Practitioner names are anonymized in the public sample.
Evidence
| Vendor | Product | Deployment scope | Conf. | Source | Date |
|---|---|---|---|---|---|
MMicrosoft | Intune (Microsoft Endpoint Manager) | Windows device policy enforcement, compliance, and MAM; confirmed by Endpoint Management team manager in current-role description | Practitioner-Attestedpractitioner-attestationEmerson Tanaka – LinkedIn (current role, Bentley Systems) | 2026-05-19 | |
JJamf | Jamf Pro | Apple device deployment and management across Bentley Systems fleet | Practitioner-Attestedpractitioner-attestationEmerson Tanaka – LinkedIn (current role, Bentley Systems) | 2026-05-19 | |
LLakeside Software | SysTrack | Endpoint management backend analytics; confirmed by Endpoint Management team manager | Practitioner-Attestedpractitioner-attestationEmerson Tanaka – LinkedIn (current role, Bentley Systems) | 2026-05-19 |
Evidence methodology
- A current or recent employee named this vendor in their LinkedIn work-history snippet — first-person disclosure, strongest non-deterministic signal.
What the sample could not confirm
- SCCM deployment scope unclear — may be legacy co-management alongside Intune rather than primary channel; no practitioner snippet explicitly scopes SCCM as current production.
- Mobile device management scope (iOS/Android vs. macOS/Windows only) not explicitly defined.
How this shows up in a profile
Every profile organizes vendor mentions, practitioner evidence, confidence, and source links by domain so account teams can move from broad hypothesis to call-ready context.