Eido connects to your Microsoft Intune tenant, copies what Intune knows about your devices, people, policies and apps, and turns it into a picture you can act on: which devices need attention, why, and since when. It runs in a browser. Nothing is installed on your devices to get started.
Intune is where you manage devices. Eido is where you see whether that management is working.
What Eido reads from Intune#
Once an administrator has connected a tenant, Eido keeps its own copy of the tenant’s data and refreshes it about once an hour. The first sync can take up to 30 minutes.
| Area | What Eido brings in |
|---|---|
| Devices | Every managed device, its owner, operating system, hardware, encryption, last check-in and enrolment details |
| People | Users and groups from Microsoft Entra ID, so that a device can be tied to a person, a department or an office |
| Compliance | Each compliance policy, and its result on each device |
| Configuration | Each configuration profile, its settings, and its result on each device |
| Apps | The apps you deploy and whether each install worked, plus the apps Intune has discovered on devices |
| Windows updates | Patch level, update rings and driver updates |
| Security | Defender status, active malware, firewall and attestation reports |
| Automation | Remediations and platform scripts, and how each run ended |
| Change history | Intune audit events and the history of policy settings |
| Other | Autopilot deployments, enrolment certificates, Apple app licences, remote assistance sessions and Endpoint Privilege Management elevations |
What Eido syncs has the full list, and Permissions Eido needs explains the access behind it. Reporting needs only read access to Intune. Read and write access is asked for only if you want to use Policy Management.
What Eido adds on top#
One health status per device. Intune reports compliance, configuration, apps and updates in separate places. Eido grades every device in four categories (Compliance, Config, Apps and Patch) as Healthy, Unhealthy - Medium, Unhealthy - High or Unknown, and shows them side by side. A device that Intune calls compliant can still be months behind on patches, and Eido shows both facts on one row. Key concepts explains the grading.
Issues with a start and an end. When something on a device goes unhealthy, Eido opens an issue and closes it when the device recovers. That gives you a list to work through, and a record of how long each problem lasted. See Issues.
Patching that accounts for reality. Eido compares each Windows device with the updates Microsoft has released, takes your update rings into account, and tells you which devices are behind and by how much. See Patch compliance and OS compliance.
History. Intune mostly shows today. Eido keeps what it reads, so you can see how health has moved over time in Trends.
Reporting without scripts. Query Hub lets you filter, group and chart any of the data, save the result as a report, schedule it and export it. Dashboards put the reports you care about on one page, and Workbooks turn them into a document.
Alerts and automation. Alerts tell you by email, Teams, Slack, webhook or ServiceNow when a device or certificate becomes unhealthy. Automations watch your data and act when it changes.
Several customers in one place. If you look after more than one organisation, each customer’s tenants sit under that customer, with one overview across all of them. See Customers overview.
Some parts of Eido appear only once an administrator has switched them on:
| Feature | What it does | Switched on in |
|---|---|---|
| App Metering | Shows which applications are really used, by whom and for how long | Setting up App Metering |
| Eido AI | Diagnoses a device for you and tracks changes made in Intune | Eido AI |
| Odie | An assistant on every page that answers questions and builds reports | Odie Assistant |
Who it is for#
- IT administrators and endpoint engineers, who need to know which policies are failing, which apps did not install and which devices are behind on updates.
- Service desk engineers, who need to open one device and see everything about it in one place.
- Security and compliance teams, who need evidence: encryption, patch level, malware and who changed which policy.
- IT managers, who need a dashboard and a report they can send without asking somebody to build it.
- Managed service providers, who need all of the above for every customer, without signing in to each tenant in turn.
The main areas#
- Dashboards The page Eido opens on. Tiles and charts of your choosing.
- Endpoints Every device, with its four health statuses.
- Device details Everything Eido knows about one device.
- Users People, and the devices they use.
- Discovered apps What is actually installed across the estate.
- Patch compliance Which Windows devices are behind on updates.
- Compliance policies Each policy, and the devices that fail it.
- Configuration policies Each profile, and the devices where it did not apply.
- Managed apps The apps you deploy, and where installs failed.
- Issues Everything that is unhealthy now, and what was fixed.
- Query Hub Built-in reports, and your own.
- Certificates Certificates, with their status and expiry date.
Where to go next#
If you are new, read Key concepts for the vocabulary, then Finding your way around for the layout. Your first day is a guided tour of a newly connected tenant.
If your organisation has not signed up yet, start with Signing up.