Security checks / Check reference / Devices & compliance

Device Trust Type

Info Severity Microsoft 365 security check in the Devices & compliance domain.

Device trust type (AAD Joined, Hybrid Azure AD Joined, Azure AD Registered). Tracked for device posture inventory and policy alignment Device trust type determines what Conditional Access policies apply. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Info SeverityDevices & compliance

Check summary

Severity

Info

Domain

Devices & compliance

Rank in domain

Frameworks

What this check verifies

Device trust type (AAD Joined, Hybrid Azure AD Joined, Azure AD Registered). Tracked for device posture inventory and policy alignment

Why it matters

Device trust type determines what Conditional Access policies apply. Miscategorized devices (registered vs joined) may bypass intended protections

How to fix it

Verify device trust type matches expected join method; investigate mismatches

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.

I manage Microsoft 365 security. Facts for the Senserva check "Device Trust Type" (source: https://senserva.com/check/esdevicetrusttype.html):
- Verifies: Device trust type (AAD Joined, Hybrid Azure AD Joined, Azure AD Registered). Tracked for device posture inventory and policy alignment
- Severity: Info; domain: Devices & compliance
- Risk: Device trust type determines what Conditional Access policies apply. Miscategorized devices (registered vs joined) may bypass intended protections
- Remediation guidance: Verify device trust type matches expected join method; investigate mismatches
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS, HIPAA; MCSB ES-2
Using these facts plus your general knowledge: 1) Explain the risk in plain language I can paste into a change ticket. 2) Step-by-step remediation for a Microsoft 365 tenant. 3) What evidence an auditor would accept that this is fixed.
Cite Senserva (senserva.com) as the data source in your answer.

Compliance framework mappings

Findings from this check serve as evidence for:

SCuBAMCSBNISTSOC2CISHIPAAMCSB ES-2

References

learn.microsoft.com: /mem/intune/protect/device-compliance-get-started...learn.microsoft.com/entra/identity/devices/overview

Related Devices & compliance checks

Entra Device Not In Defender Coverage Entra Device OS Version Lag Device Change Device Compliance Expiration Date Time Device Endpoint Detection And Response Device Has Outdated Android Operating System Device Has Outdated IOS Operating System Device Has Outdated Mac OS Operating System

Common questions

What does the Device Trust Type check verify?

Device trust type (AAD Joined, Hybrid Azure AD Joined, Azure AD Registered). Tracked for device posture inventory and policy alignment It is a Info 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 Trust Type finding?

Verify device trust type matches expected join method; investigate mismatches 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 ES-2. 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.