Fix Android Intune Device Information Missing in Azure AD Sign-In Logs
Question details
The administrator needs to resolve an issue where Android devices enrolled in Microsoft Intune do not pass their device identity information to Azure AD sign-in logs.

- Product
- Microsoft Intune and Azure AD
- Device & OS
- Android
- Scenario
- Reviewing Azure AD sign-in logs for conditional access policy evaluation and compliance monitoring.
- Observed behavior
- Android devices do not show device details in the sign-in logs, whereas other device platforms display the information correctly.
Ensure you have Azure AD Premium or Intune administrator privileges and that the affected Android devices are currently powered on with an active internet connection.
Verify Android Enrollment Method and Broker Application
Android devices require a broker app like Microsoft Authenticator or Intune Company Portal to successfully pass device identity data to Azure AD.
Without the correct broker application installed and configured, Azure AD Conditional Access policies cannot properly evaluate the device's state, resulting in missing information in the sign-in logs.
Log in to the Microsoft Endpoint Manager admin center, navigate to Devices, and verify if the Android enrollment is set to Android Enterprise (personally-owned with a work profile or fully managed).
Ensure the required broker application (Microsoft Authenticator or Intune Company Portal) is installed, updated, and actively running on the affected Android devices.
Instruct the user to open the broker application on their Android device and complete any pending registration prompts or re-authentication requests.

Review Intune Compliance Status and Conditional Access Logs
Determine if the device is correctly marked as compliant in Intune and investigate specific conditional access policy failures.
Escalate to Microsoft Intune Support
If local configuration is fully correct but logs still omit device data, contact Microsoft support for backend troubleshooting.
Looking for an Easily Deployable Office Suite?
While troubleshooting Intune and Azure AD conditional access, consider optimizing your organization's software deployment. WPS Office is a highly compatible, lightweight, and free alternative to Microsoft Office that is easy to manage and deploy across enterprise mobile and desktop environments.
- 1. Download the software: Download the appropriate WPS Office installer package for your target operating systems.
- 2. Deploy via MDM: Deploy the application across your endpoints using your existing Mobile Device Management (MDM) solution.
- 3. Open existing files natively: Start opening existing Microsoft Office files natively in WPS Office without any formatting loss.

Frequently Asked Questions
Why does Azure AD Conditional Access require a broker app on Android?
On Android devices, Azure AD requires a broker application like Microsoft Authenticator or Intune Company Portal to securely store the device identity certificate and pass it to Azure AD during the sign-in process for conditional access evaluation.
How long does it take for Intune device status to reflect in Azure AD?
Device compliance and enrollment status changes typically sync between Intune and Azure AD within a few minutes. However, depending on network conditions and Microsoft backend synchronization, it can occasionally take up to 8 hours.
Can I manage WPS Office mobile app deployment via Microsoft Intune?
Yes, WPS Office applications for Android and iOS can be centrally deployed and managed using Microsoft Intune by uploading the application package or adding the store app, and then assigning it to your organization's device groups.




