What Microsoft Intune leaves out, and what Eido adds
Intune is where you manage devices. Eido is where you see whether that management is working. It runs alongside Intune and never replaces it.
The question we hear most from enterprise teams is a fair one: what does Eido add that Intune does not already do? Quite a lot, it turns out, and Microsoft’s own documentation is the clearest place to see it. Every Intune line below links to the Microsoft Learn page it comes from. We checked them in October 2026, and we will keep checking, because Microsoft moves quickly and one wrong claim about Intune is one too many.
| Intune on its own | With Eido | |
|---|---|---|
| History | One historical report: a 30-day compliance trend | 12 months of daily scores, down to the devices on any day |
| Policy changes | An audit log of who changed what | A saved version on every change, and a restore |
| Software use | No running application detection | Who ran each app, on which device, and for how long |
| Scheduled reports | None in the admin center | Any report emailed daily, weekly or monthly, and PDF workbooks |
| Performance | CPU and RAM spike scores, a 14-day average | Any of 3,000+ counters, charted by the minute |
| Fixing a device | Device query reads; a fix needs a script, a reboot or a remote session | End a process, restart a service or clear a print queue from the device page |
| Inventory freshness | At check-in, about every 8 hours | As often as every 15 minutes |
History: 12 months, not 30 days
Intune’s reports are mostly a picture of now. Microsoft lists exactly one report as historical, the device compliance trend, and it covers 30 days (Microsoft Learn: Intune reports).
Eido keeps daily scores for compliance, configuration, apps and patching, and lets you open any policy or app to see which devices were failing on which day, for up to 12 months. That is the history an auditor, a CISO or a quarterly service review asks for. One honest caveat: Eido’s history starts the day you connect, so the sooner you connect, the more of it you have.
Policy changes you can undo
Intune’s audit log records who changed a policy and which properties changed (Microsoft Learn: audit logs). It does not keep a version of the policy you can go back to.
Eido saves a new version of a policy each time its settings or assignments change, shows you the value of every setting over time, and restores an earlier version of compliance, configuration, settings catalog, script, remediation and update policies. Restores are an administrator action, with a fresh Microsoft sign-in.
Software use, not just software installs
On whether an installed application is actually used, Microsoft is direct: “At this time, Intune provides no running application detection” (Microsoft Learn: Enterprise App Management).
Eido’s software metering shows who ran each application you choose to meter, on which device, on how many days and for how long. It works through two Intune Remediations, so there is no agent to deploy, and it is the evidence a licence renewal needs.
Reports that send themselves
The Intune admin center has no scheduled report delivery: reports are read there, or exported. Eido emails any report daily, weekly or monthly, and builds workbooks, branded PDFs that land in leadership’s inbox on the 1st of the month without anyone rebuilding them.
Performance by the minute
Intune’s resource performance report gives CPU and RAM spike scores, with the spike percentage averaged over 14 days (Microsoft Learn: resource performance). That is good for spotting which models need replacing.
With the Eido Client on a Windows device, you can chart any of the 3,000+ Windows performance counters, by the minute, for the last seven days, with samples taken as often as every three seconds. That is what you need when the question is why this machine was slow at 14:20 today.
Fixing a device, not just reading it
Device query is a real step forward: it runs a query against a Windows device in real time and returns its state, from processes to registry values (Microsoft Learn: device query). To change anything, Microsoft points you to a reboot or a remediation script, or a remote session.
The Eido Client’s live tools act from the device page: end a stuck process, restart a service, clear a print queue, browse the event log or the registry. Write actions stay off until you switch them on, risky ones ask for a fresh Microsoft Entra sign-in, and every action is logged.
Inventory in minutes, not at the next check-in
Intune’s scheduled check-in comes round about every eight hours (Microsoft Learn: troubleshoot policies and profiles), although some changes are pushed sooner. The Eido Client refreshes its inventory as often as every 15 minutes, checks the event log for crashes, hangs and blue screens every five, and refreshes on demand when you ask it to.
Alongside Intune, not instead of it
None of this replaces Intune. Intune manages the devices. Eido reads it, read-only by default, and adds the history, the evidence and the reach that Intune does not. Book a demo and we will show you the difference on your own estate.