Back to all tools
PowerShell ModuleAutomation

Entra ID Device Trust

Entra ID Device Trust enables binding Function Apps to Entra ID joined devices by validating requests originate from trusted devices via the device certificate enrolled during device registration. It combines client-side data gathering (signature hash, device CN, public key, thumbprint) with server-side validation, and can be embedded as a module in your Function App or installed as a dependency. The solution supports embedding EntraIDDeviceTrust.Client on clients and EntraIDDeviceTrust.FunctionApp in Function Apps for seamless, enhanced request security.

Works with
WindowsEntra IDConditional Access

Security Analysis

5of 6
1 Issue Found

17 files scanned on Jun 11, 2026

Issues Detected
No Obfuscated Code
No base64 encoded commands or hidden scripts
Base64 decode and execute in EntraIDDeviceTrust.FunctionApp/Public/Get-EntraIDDeviceAlternativeSecurityIds.ps1 ([lines: 27](https://github.com/MSEndpointMgr/EntraIDDeviceTrust/blob/main/EntraIDDeviceTrust.FunctionApp/Public/Get-EntraIDDeviceAlternativeSecurityIds.ps1#L27))
Passed Checks
No Remote Execution
No Credential Theft
No Data Exfiltration
No Malicious Patterns
No Hardcoded Secrets
AI Analysis

Overall, the EntraIDDeviceTrust codebase is aligned with expected Intune/Entra ID device trust patterns and does not contain obfuscation or hardcoded secrets. A critical functional bug exists in the signing path (undefined variable used to select the certificate) that can disable the attestation flow. There is a legitimate data-exfiltration vector where device identity and attestation data are sent to an external Function App endpoint; ensure the endpoint is trusted, authenticated, and that data minimization/privacy controls are in place. Private key usage for signing is expected for device attestation but should be protected with strong key management and restricted access.