{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/", "slug": "dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error", "url": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/" }, "title": "Track the seven-day hold when an Intune compliance setting reports Error", "summary": "Why can a device retain its earlier compliance state while one setting is in Error?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "identity-cloud", "label": "Identity & cloud", "alt": "Governed cloud identity system with connected service and lifecycle nodes.", "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-17T16:33:21+00:00", "modified_at": "2026-09-17T16:38:46+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 197, "potentially_affected": "Use this explanation when an Intune compliance setting reports Error. Record the affected setting, its first observed error time, the prior device compliance state and the policy's configured grace period.", "dse_recommendation": "DSE recommends treating the error as an owned investigation while recording the temporary state carry-forward.", "primary_source": { "name": "Monitor results of your device compliance policies in Microsoft Intune - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/device-security/compliance/monitor-policy", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

When a compliance setting reports Error, Intune preserves the device’s existing compliance state for up to seven days while waiting for a valid evaluation. If Error remains after that period, the device becomes noncompliant or enters the policy’s configured grace period. Microsoft Learn.

\n

Applicability

\n

Use this explanation when an Intune compliance setting reports Error. Record the affected setting, its first observed error time, the prior device compliance state and the policy’s configured grace period.

\n

DSE recommendation

\n

DSE recommends treating the error as an owned investigation while recording the temporary state carry-forward. Give support a deadline tied to the first observed failure and the policy behavior, rather than assuming an unchanged device status means the setting passed. Coordinate any expected access impact with the device and application owners.

\n

Verification

\n

Review the per-setting result and overall device status together as troubleshooting progresses. Retain the relevant check-in times and the eventual compliant or noncompliant evaluation. If the error persists, verify the resulting status against the documented seven-day behavior and configured grace period. Close the investigation only when the setting has an explained result.

\n

Official references

\n

Microsoft Learn: Monitor results of your Intune device compliance policies. Source reviewed September 17, 2026.

", "content_text": "Source facts\nWhen a compliance setting reports Error, Intune preserves the device’s existing compliance state for up to seven days while waiting for a valid evaluation. If Error remains after that period, the device becomes noncompliant or enters the policy’s configured grace period. Microsoft Learn.\nApplicability\nUse this explanation when an Intune compliance setting reports Error. Record the affected setting, its first observed error time, the prior device compliance state and the policy’s configured grace period.\nDSE recommendation\nDSE recommends treating the error as an owned investigation while recording the temporary state carry-forward. Give support a deadline tied to the first observed failure and the policy behavior, rather than assuming an unchanged device status means the setting passed. Coordinate any expected access impact with the device and application owners.\nVerification\nReview the per-setting result and overall device status together as troubleshooting progresses. Retain the relevant check-in times and the eventual compliant or noncompliant evaluation. If the error persists, verify the resulting status against the documented seven-day behavior and configured grace period. Close the investigation only when the setting has an explained result.\nOfficial references\nMicrosoft Learn: Monitor results of your Intune device compliance policies. Source reviewed September 17, 2026.", "content_markdown": "## Source facts\n\nWhen a compliance setting reports Error, Intune preserves the device’s existing compliance state for up to seven days while waiting for a valid evaluation. If Error remains after that period, the device becomes noncompliant or enters the policy’s configured grace period. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/device-security/compliance/monitor-policy).\n\n## Applicability\n\nUse this explanation when an Intune compliance setting reports Error. Record the affected setting, its first observed error time, the prior device compliance state and the policy’s configured grace period.\n\n## DSE recommendation\n\nDSE recommends treating the error as an owned investigation while recording the temporary state carry-forward. Give support a deadline tied to the first observed failure and the policy behavior, rather than assuming an unchanged device status means the setting passed. Coordinate any expected access impact with the device and application owners.\n\n## Verification\n\nReview the per-setting result and overall device status together as troubleshooting progresses. Retain the relevant check-in times and the eventual compliant or noncompliant evaluation. If the error persists, verify the resulting status against the documented seven-day behavior and configured grace period. Close the investigation only when the setting has an explained result.\n\n## Official references\n\n[Microsoft Learn: Monitor results of your Intune device compliance policies](https://learn.microsoft.com/en-us/intune/device-security/compliance/monitor-policy). Source reviewed September 17, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/", "url": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Track the seven-day hold when an Intune compliance setting reports Error", "item": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/", "url": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/", "headline": "Track the seven-day hold when an Intune compliance setting reports Error", "description": "Why can a device retain its earlier compliance state while one setting is in Error?", "abstract": "Why can a device retain its earlier compliance state while one setting is in Error?", "articleBody": "Source facts\nWhen a compliance setting reports Error, Intune preserves the device’s existing compliance state for up to seven days while waiting for a valid evaluation. If Error remains after that period, the device becomes noncompliant or enters the policy’s configured grace period. Microsoft Learn.\nApplicability\nUse this explanation when an Intune compliance setting reports Error. Record the affected setting, its first observed error time, the prior device compliance state and the policy’s configured grace period.\nDSE recommendation\nDSE recommends treating the error as an owned investigation while recording the temporary state carry-forward. Give support a deadline tied to the first observed failure and the policy behavior, rather than assuming an unchanged device status means the setting passed. Coordinate any expected access impact with the device and application owners.\nVerification\nReview the per-setting result and overall device status together as troubleshooting progresses. Retain the relevant check-in times and the eventual compliant or noncompliant evaluation. If the error persists, verify the resulting status against the documented seven-day behavior and configured grace period. Close the investigation only when the setting has an explained result.\nOfficial references\nMicrosoft Learn: Monitor results of your Intune device compliance policies. Source reviewed September 17, 2026.", "datePublished": "2026-09-17T16:33:21+00:00", "dateModified": "2026-09-17T16:38:46+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260917-099-track-the-seven-day-hold-when-an-intune-compliance-setting-reports-error/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Track the seven-day hold when an Intune compliance setting reports Error" }, "articleSection": [ "Cybersecurity", "IT" ], "keywords": [ "Cybersecurity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 197, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Monitor results of your device compliance policies in Microsoft Intune - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/device-security/compliance/monitor-policy" } } ] } }