Eido provides visibility into both compliance and configuration policies applied to a device, allowing you to understand whether it meets organisational requirements and where issues may exist.
Understanding Policy Types
Eido separates policies into two key areas:
Compliance Policies – define whether a device meets required security and organisational standards
Configuration Policies – control device settings and behaviour (for example security baselines or system configurations)
These are available as separate tabs within the Device Details view.
Viewing Compliance Policies
The Compliance tab shows the compliance policies applied to the device and their current status.
For each policy, you can see:
Policy name
Compliance state (e.g. Compliant, Not compliant)
Assignment (user or device)
This allows you to quickly identify whether a device is meeting required standards.
Identifying Non-Compliant Devices
If a device is not meeting compliance requirements:
The Compliance Status in the header will show Non-Compliant
Individual policies will display a red status indicator
This helps you quickly pinpoint which policy is causing the issue.
Viewing Configuration Policies
The Config Policies tab shows configuration policies applied to the device.
These may include:
Security baselines
Device restrictions
Endpoint protection settings
Custom configuration profiles
Each policy can be expanded to view more detail.
Understanding Configuration Policy Status
For each configuration policy, you can view:
Metric name
Intune state (e.g. Succeeded, Failed, Error)
Assignment type
This allows you to determine whether policies have been successfully applied.
Expanding Policy Details
Policies can be expanded to reveal additional information.
This helps you:
Understand exactly what is configured
See how the policy is assigned
Investigate failures or inconsistencies
Expanding policies is particularly useful when troubleshooting configuration issues.
Using Policies for Troubleshooting
The Policies view helps you quickly answer key questions:
Why is this device non-compliant?
Which policy is failing?
Has a configuration been successfully applied?
Is the issue user-based or device-based?
By reviewing both compliance and configuration together, you get a complete picture of policy health.
Relationship to Device Health
Policy results directly impact overall device status:
A failed compliance policy will mark the device as Non-Compliant
Configuration failures may contribute to broader health issues
These statuses are reflected in dashboards, issues, and reporting across Eido
Compliance and Configuration policy thresholds are configured at the tenant level.
For more information, see
Comments
0 comments
Article is closed for comments.