Connect identity and devices

Sign in with Active Directory or Entra ID, connect Intune, and bring devices in by agent or agentless.

Updated 18 October 2026

Online version, always current: https://cloudvision360.com/docs/itops360/connect-identity-and-devices/

Bringing your estate into ITOps360 has two parts: identity (who your people are) and devices (what they use).

Connect identity

  • Active Directory — connect over LDAPS for sign-in and directory data.
  • Microsoft Entra ID — connect for users, MFA registration, licenses and sign-in activity.

Group-to-role mapping is re-applied at every sign-in, so directory group changes flow through automatically. See Active Directory and Entra.

Bring devices in

Choose whichever path fits each part of your estate — a device seen by several paths is still one asset:

  • Microsoft Intune — connect for already-managed devices.
  • Agentless — WinRM (Windows) or SSH (Linux/macOS) through a site collector, no software on the endpoint.
  • The ITOps360 agent — for Windows, macOS and Linux where there is no endpoint manager, and for patching and live diagnostics.

Deploy a site collector

For discovery and agentless management, deploy a site collector at each site. Collectors call out over HTTPS — no inbound firewall rules — and credentials are sealed to each collector’s own key.

Next

With identity and devices connected, explore device health, the service desk and discovery.