Security checks / Check reference / Intune configuration

Intune Policy Compliance Tpm Required

High Severity Microsoft 365 security check in the Intune configuration domain.

TPM (Trusted Platform Module) is not required by device compliance policy TPM provides hardware-based key storage and attestation Without it, BitLocker keys and device identity are software-only and easier to extract Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

High SeverityIntune configuration

Check summary

Severity
High
Domain
Intune configuration
Rank in domain
4
Frameworks
6

What this check verifies

TPM (Trusted Platform Module) is not required by device compliance policy

Why it matters

TPM provides hardware-based key storage and attestation Without it, BitLocker keys and device identity are software-only and easier to extract

How to fix it

Require TPM in compliance policy; block devices without TPM capability

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:

SCuBAMCSBNISTSOC2CISHIPAAMCSB ES-1MCSB ES-8

Common questions

What does the Intune Policy Compliance Tpm Required check verify?

TPM (Trusted Platform Module) is not required by device compliance policy It is a High Severity check in the Intune configuration domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Intune Policy Compliance Tpm Required finding?

Require TPM in compliance policy; block devices without TPM capability 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 controls ES-1, ES-8. 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.

Reference: the compliance and audit guide, and the full checks catalog.
Data notice: check definitions describe what Siemserva verifies and are provided as is, for informational purposes only, without warranty of any kind. Framework mappings are informational and do not constitute compliance advice; confirm requirements with your assessor. All use of this data is subject to the Senserva EULA.