Security checks / Check reference / Devices & compliance
Device Sign In Not Time Based Non Compliant Devices
Medium Severity Microsoft 365 security check in the Devices & compliance domain.
Sign-in frequency is not time-based for non-compliant devices. Non-compliant devices should be forced to re-authenticate on a schedule Non‐compliant devices keep long sessions; token replay maintains access Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
Sign-in frequency is not time-based for non-compliant devices. Non-compliant devices should be forced to re-authenticate on a schedule
Why it matters
Non‐compliant devices keep long sessions; token replay maintains access
How to fix it
Enforce sign-in frequency limits for non-compliant devices via Conditional Access
Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.
Ask your own AI about this check
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Compliance framework mappings
Findings from this check serve as evidence for:
Related Devices & compliance checks
Common questions
What does the Device Sign In Not Time Based Non Compliant Devices check verify?
Sign-in frequency is not time-based for non-compliant devices. Non-compliant devices should be forced to re-authenticate on a schedule It is a Medium Severity check in the Devices & compliance domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.
How do I fix a Device Sign In Not Time Based Non Compliant Devices finding?
Enforce sign-in frequency limits for non-compliant devices via Conditional Access Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.
Which compliance frameworks does this check evidence?
Findings from this check map to SCuBA, MCSB, NIST, SOC2, CIS, HIPAA, and MCSB control IM-6. That mapping is what turns a scan finding into audit evidence.
Can I ask my own AI about this check?
Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.
All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.