Skip to content

Device Registration & Join Settings

The question it answers: Who may join and register devices, does it need MFA, and who becomes local administrator on joined devices?

Who may join devices, whether that needs MFA, and who becomes local administrator on every joined device are tenant-wide settings nobody looks at after day one. The defaults let every user join devices and make them local admins.

Where in the appEntra ID › Identity Configuration › Device Registration & Join
WorkloadEntra ID
KindFindings list · dashboard tile
DataRead from Microsoft 365 when someone first opens it, then kept for the report cache lifetime (Settings > Data & cache, 1 hour unless changed).
LicenceNo extra licence needed.
Report id (API and MCP)entra.configuration.device-registration-policy
ColumnKeyType
SeveritySeverityStatus
AreaCategoryText
SettingSubjectLink
CheckSettingText
ValueValueText
FindingFindingText
DetailDetailText
DateWhenDate
CountNumberNumber

A findings list hides columns that no row fills. Severity is Critical, Serious, Warning, OK or Info; rows rated Critical, Serious or Warning need attention (Working with findings).

Licence: No extra licence needed.

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

PermissionAPIWhat it allowsNote
Policy.Read.DeviceConfigurationMicrosoft GraphRead your organization’s device configuration policies
Policy.Read.AllMicrosoft GraphRead your organization’s policies
Data sources it reads
  • GET /v1.0/policies/deviceRegistrationPolicy
  • GET /v1.0/identity/conditionalAccess/policies (cached)
GET /ir-api/v1/reports/entra.configuration.device-registration-policy?size=100

An AI assistant reads it with the MCP tool get_report and the id entra.configuration.device-registration-policy. The client needs the Read grant for Entra ID. See Using the API.