Introducing Workbooks: Eido Release 2026.6

June 2026  | Product Update

Eido release 2026.6 introduces Workbooks, a new capability for building scheduled, branded PDF reports directly from your Eido data. This release also includes significant improvements to patch compliance accuracy through Update Ring integration, new configurable Patch Rules, and several enhancements to QueryHub.

Workbooks

Workbooks provide a structured way to turn live Eido data into polished, repeatable PDF reports. Rather than manually exporting dashboards or assembling data each reporting cycle, administrators can build are port once and schedule it to be delivered automatically to the right stakeholders at the right time.

Report composition

Workbooks are built using a flexible widget System Administrators can combine any of the following components into a single report:

• Piecharts and column charts for visualizing data distributions

• Tables for detailed row-level data

• Stat tiles for key metrics and summary figures

• Cover pages, logos, headers, footers, and page numbers for branded presentation

Scheduling and delivery

Once a workbook is configured, it can be scheduled for automatic delivery. Teams receive up-to-date reports without any manual export work, ensuring stakeholders always have current data without placing additional burden on the administrators who manage the environment.

‍

Update Ring Reporting

Eido now synchronizes with Intune Windows Update Ring configurations and applies the configured deferral periods when calculating patch status. This change improves the accuracy of patch compliance assessments across managed device estates.

How deferral periods affect patch status

Previously, Eido assessed patch status without accounting for the deferral periods defined in an organization’s Update Ring policies. A device could be flagged as Amber or Overdue even if it was still within its configured deferral window.

With this release, Eido evaluates patch status relative to the Update Ring assigned to each device. For example, if a device has a 7-day deferral configured in Intune, Eido will not begin counting toward an Amber or Overdue threshold until that deferral period has elapsed. Devices are not marked as Overdue until both the Intune deferral period and the configured Eido threshold have been exceeded.

New system reports

Five new system reports are included in this release:

• Devices by Update Ring

• Outstanding Patches by KB

• Overdue Devices

• Overdue Devices by Ring

• Patch Status Breakdown

Patch Rules

Eido now provides configurable rules for assessing device security health, giving organizations more control over how patch compliance is calculated across their device estate.

Configurable patch tolerance

Administrators can define the level of patch currency required before a device is flagged. Options include requiring the latest patcher allowing a tolerance of N-1, N-2, N-3, or N-4. This is useful for environments where some devices operate on slower update cadences or have extended maintenance windows.

Green, Amber, and Red thresholds

The timeframes that govern when a device moves from a healthy state to an attention state, and then to an urgent state, are now fully configurable. Different threshold rules can be applied to different device groups, allowing stricter compliance requirements for higher-risk devices alongside more permissive rules for devices with longer maintenance windows.

Separate minor and major rule handling

Security patch compliance and major operating system version compliance are now assessed independently. This allows organizations to apply different thresholds and tolerances depending on whether they are tracking routine security updates or broader OS version compliance.

Apple device compliance

For Apple devices, Eido now assesses compliance against the latest major OS version supported by the specific hardware model, rather than applying a single tenant-wide version. Tenant-wide minimum OS rules remain available where a consistent floor is preferred.

‍

QueryHub Enhancements

New computed column types

QueryHub now includes two new computed column capabilities:

• Rank against dataset. Bucket rows by how their value ranks within the full dataset or within defined groups. A common use case is identifying the most recent BIOS version per device model.

• Compare to dataset. Flag rows where a value is equal to, below, or above the maximum, minimum, or average value across the dataset or within a group.

Entra Group filtering

QueryHub now supports filtering by Microsoft Entra groups, available in new QueryHub reports, custom dashboard widgets, and Workbook widgets. Both device Entra groups and primary user Entra groups are supported, making it easier to scope reports and dashboards to specific populations of devices or users.

Additional improvements

• Lenovo Advanced Inventory is now supported, including synchronization of friendly model names via the Lenovo API.

• Manual color selection is now available for slices on bar and pie charts.

‍

Bug Fixes

• QueryHub column naming. Columns with duplicate names now display distinct names consistent with their filter and group-by references.

• QueryHub sorting. Entra extended properties are now sorted alphabetically.

• QueryHub report saving. Resolved an occasional error when saving reports caused by are fresh token being renewed mid-save.

• Global Search. Global Search now returns results when searching by UPN, email address, serial number, and IMEI.

• Software Metering. Resolved an issue where Software Metering did not correctly attribute users when permissions were elevated via Run as Admin.

‍

Get started with Eido

To see these features in action, request a personalized demo or visit eido.io to learn more.

‍

‍

‍

‍

‍

‍