Halo + Microsoft Intune

Your Device Estate, Live Inside Your Service Desk.

Halo's native Intune integration automatically syncs every managed device into your CMDB — so your agents always have real device data, right on the ticket.

Book a Demo See All Integrations

The Integration

Everything Intune knows, Halo knows too.

One connection. Every managed device — Windows, macOS, iOS, Android — synced automatically into your Halo CMDB.

🔄

Continuous Sync

Devices sync automatically — no manual imports, no scheduled jobs to maintain. Your CMDB reflects the current state of your estate at all times.

📋

Device Data on Every Ticket

When a user raises a ticket, their device details appear automatically — OS version, compliance status, serial number, and last Intune check-in.

⚡

Compliance-Driven Automation

Non-compliant devices can automatically trigger incidents in Halo. Catch security risks before users report them.

🔗

User-to-Device Linking

Devices are automatically linked to their assigned users via Entra ID, giving you a complete picture of who owns what across the estate.

📦

Full Asset Lifecycle

Devices move through their full lifecycle in Halo — onboarded, active, decommissioned — tracked alongside your service desk activity.

🏢

Works with Entra ID

Intune and Entra ID sync together. Users, groups, and devices are all connected — no duplicate imports, no configuration overlap.

How It Works

Set up once. Syncs continuously.

Halo connects to your Microsoft tenant via a single App Registration. No agents to install. No third-party middleware.

Connect your tenant

Provide your Microsoft tenant details and App Registration credentials in Halo's integration settings.

Initial device import

Halo pulls your full Intune device inventory into the CMDB. Every managed device becomes an asset record.

Continuous sync keeps it current

Halo polls Intune on a schedule you control. New devices, compliance changes, and ownership updates sync automatically.

Halo vs ServiceNow

Native integration. No extras required.

ServiceNow's device management requires ITOM Discovery — a separate, expensive add-on. Halo's Intune integration is included in every licence.

	Halo	ServiceNow
Intune integration included in base licence	✓	ITOM add-on required
Native connector — no middleware	✓	Custom development
Device data on tickets, out of the box	✓	Configuration required
Compliance-triggered incident creation	✓	✓ (with ITOM)
Entra ID sync alongside Intune	✓	Separate connector
All-inclusive per-agent pricing	✓	Module-based add-ons

Who It's For

Built for IT teams already running Microsoft 365.

If you manage devices through Intune and run a service desk that can't see them, Halo closes that gap.

✓ IT teams managing 100+ devices through Intune who are tired of switching between portals

✓ Service desk teams who need device context on tickets without asking users to find serial numbers

✓ Security-conscious organisations that want non-compliant devices to automatically raise incidents

✗ Organisations on ServiceNow paying for ITOM Discovery just to see their Intune devices

✗ Teams manually exporting Intune CSVs and importing them into their ITSM tool each week

✗ IT managers who only find out a device is non-compliant when a user calls the helpdesk

FAQ

Common questions

Does the Intune integration come included with Halo, or is it an add-on?

It's included. Every Halo licence includes the full integration library — there are no per-integration fees and no additional licensing costs to connect Intune.

Which devices does Halo sync from Intune?

All Intune-managed devices are synced — Windows, macOS, iOS, and Android. Each device becomes an asset record in Halo's CMDB with full metadata including OS version, compliance status, serial number, and last check-in time.

How often does Halo sync with Intune?

The sync frequency is configurable. Halo polls Intune on a schedule you define, so your CMDB stays current without manual intervention.

Can Halo automatically raise incidents when a device becomes non-compliant?

Yes. Halo's automation rules can be configured to trigger incident creation when a device's compliance status changes. Your team is alerted before users start calling the helpdesk.

Does this work with Microsoft Entra ID as well?

Yes — Halo connects to both Intune and Entra ID through the same Microsoft 365 integration. Users, groups, and devices are all linked together in Halo without duplicate configuration.

See Halo's Intune integration in action.

Book a demo with Allied ESM and we'll walk you through exactly how your Intune estate maps into Halo's CMDB.

Book a Demo See All Integrations Email Integration