Skip to content

Device Encryption & TPM / Secure Boot Posture

The question it answers: Which managed devices are unencrypted, and which Windows devices lack TPM 2.0 or Secure Boot?

Which managed devices hold company data unencrypted, and which Windows devices lack the hardware roots of trust (TPM 2.0, Secure Boot) that BitLocker, Windows Hello and Windows 11 depend on.

Where in the appIntune › Encryption & TPM Posture
WorkloadIntune
KindTable · dashboard tile
DataBuilt from the tenant data IntensiveReports keeps in memory and refreshes in the background, so it opens at once.
LicenceMicrosoft Intune.
Report id (API and MCP)intune.devices.encryption-posture
Tabs on its pageTPM / Secure Boot Hardware Scan
ColumnKeyType
DeviceDeviceNameLink
UserUserPrincipalNameText
PosturePostureStatus
PlatformOsFamilyText
EncryptedIsEncryptedYesNo
TPMTpmVersionText
Secure BootSecureBootText
OwnershipOwnerTypeText
ComplianceComplianceStateText
Last syncLastSyncDateTimeDate
FilterKey (API)On when the page opens
Only devices with a problemproblemsYes

Licence: Microsoft Intune.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
DeviceManagementManagedDevices.Read.AllMicrosoft GraphRead Microsoft Intune devices
Data sources it reads
  • GET /beta/deviceManagement/managedDevices
  • GET /beta/deviceManagement/managedDevices/{id}?$select=hardwareInformation,deviceHealthAttestationState (hardware scan)
GET /ir-api/v1/reports/intune.devices.encryption-posture?size=100
GET /ir-api/v1/reports/intune.devices.encryption-posture?filter=problems

An AI assistant reads it with the MCP tool get_report and the id intune.devices.encryption-posture. The client needs the Read grant for Intune. See Using the API.