Other Intune-related topics, including unsupported scenarios and platform-specific behaviors
For Intune MDM-only enrollment, the supported local options in the provided material are:
- Check the Workplace Join tenant registry location:
- Open Registry Editor.
- Go to:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WorkplaceJoin\TenantInfo - The subkey name under TenantInfo is the tenant ID.
- If it is not present there, check the same path under:
HKEY_LOCAL_MACHINE
- Use
dsregcmd /status:- Run from Command Prompt.
- Review the User State section.
-
WorkplaceJoined : YESconfirms the connected workplace account context.
There is no official registry path in the provided material that confirms a separate machine-wide Intune MDM-only tenant ID location beyond the Workplace Join paths above.
For enrollment behavior, Microsoft Entra-integrated MDM enrollment passes the discovery URL from Azure directly to the system, and for a user-owned device where a work account is added, MDM enrollment is not mandatory and can be declined. The enrolled certificate type in that model is a user certificate, not a device certificate. That aligns with why user-context artifacts can appear for this enrollment style instead of a clearly exposed system-wide tenant ID location.
If a program must run entirely as LocalSystem or a service account, the provided material does not document another supported system-only method to retrieve the tenant ID locally for Intune MDM-only enrollment.
References: