Thresholds: Defining Red, Amber, and Green Status – Eido Support

Thresholds control how Eido classifies issues for configuration policies, compliance policies, and managed applications.

When Eido detects a problem, the threshold assigned to that policy or app determines whether it is shown as Green, Amber, or Red in Eido.

This allows you to control which issues are treated as important, which should be monitored as warnings, and which should be ignored.

Thresholds only affect how issues are displayed and prioritised in Eido. They do not change the policy or application itself in Intune.

What Red, Amber, and Green Mean

Eido uses a Red/Amber/Green (RAG) model to show the severity of detected issues.

Green means the issue is ignored and will not affect health status
Amber means the issue is treated as a warning or medium-severity problem
Red means the issue is treated as a high-severity problem

This makes it easier to focus on the issues that matter most in your environment.

Where Thresholds Can Be Set

Thresholds can be configured for:

Compliance Policies
Configuration Policies
Managed Apps

These settings are configured in the relevant tabs under Intune Tenant Settings (for more details, please read Linking and Managing Intune Tenants).

Available Threshold Options

Each policy or managed app can be assigned one of the following threshold levels.

Ignore

Issues detected for that item will remain Green in Eido.

This can be useful for policies or apps that are not business-critical, or where you do not want failures to generate noise in dashboards, issues, or alerts.

Medium

Issues detected for that item will be treated as Amber.

Use this for items that should be monitored, but are not severe enough to be considered critical.

High

Issues detected for that item will be treated as Red.

Use this for critical policies or applications where failures should be treated as important and investigated quickly.

How Thresholds Affect Health Status

Thresholds directly affect how policy and app failures appear across Eido.

Depending on the threshold assigned, detected issues may:

change the RAG status of a policy or app
affect device health views
appear in the Issues page
contribute to dashboards and trends
trigger alerts and external notifications

For example, a policy set to Ignore will remain Green even if it fails. A policy set to High will be treated as Red as soon as a failure is detected.

This allows you to reduce noise from low-priority issues while ensuring critical problems are surfaced clearly.

How Thresholds Affect Issues, Alerts, and Trends

When Eido detects a problem and the assigned threshold changes a policy or app away from Green, an Issue is created and appears in the Issues page.

Thresholds also affect how data is represented in Trends. The Trends view uses the RAG status of configuration policies, compliance policies, managed applications, and OS patch health to show whether health has improved or declined over time.

Because of this, the threshold assigned to a policy or app affects not only whether an issue is raised, but also how that item contributes to trend calculations at each point in time.

Within Trends, you can also choose whether calculations should include:

Red and Amber issues
Red only issues

Trends uses this data to calculate the minimum, maximum, and average values shown for the selected period.

This means threshold settings can influence:

whether an issue appears in the Issues page
whether an Alert is triggered
how health changes are reflected in Trends

If you do not want a specific policy or app failure to affect issues, alerts, or trends in the same way, you should review its assigned threshold carefully.

For more information, see Trends: Monitoring Device Health and Compliance Over Time.

Reducing Alert Noise

Thresholds are particularly useful when Eido is integrated with alerting or ticketing tools such as Email, Slack, Microsoft Teams, Webhooks, or ServiceNow.

If a policy or app is not important enough to generate notifications or incidents, you can set its threshold to Ignore. This helps reduce unnecessary noise and keeps alerts focused on the issues that matter most.

Example Endpoints page highlighting RAG statuses