Incorrect Device Registration & Compliance Query from Intune

[vishnuvardhan-gollapudi]

Hi everyone,

We are facing an issue with Intune-ISE integration, where ISE is not recognizing managed phones (iPhones & Android) as registered and compliant, even though Intune shows them as registered and compliant

Scenario:

• When an iPhone connects to corporate Wi-Fi, it correctly hits the BYOD portal policy in ISE.
• The device is redirected to the BYOD portal, where it completes the registration process via Intune Company Portal.
• After registration, the iPhone appears in Intune and is marked as compliant.

Issue Encountered:

• When the iPhone reconnects to the corporate Wi-Fi, ISE is expected to recognize the device as managed and compliant and apply the appropriate corporate policy, but instead, it assigns the default policy as if the device is unknown.
• ISE logs show:
  • Device Register Status: False
  • Compliance Status: False
  • The issue seems specific to iPhones and Android devices, as they are not being recognized as managed and compliant in ISE.

Policies:

  

 Intune Policy:

 

Result:

 

 

Observations:

• Corporate Windows devices registered in Intune correctly hit corporate policies in ISE.
• For Windows devices, logs show registered = True.
• However, for iPhones and Android devices, logs show registered = False, even though they are successfully registered and compliant in Intune.

Has anyone faced a similar issue, and if so, how was it resolved?

Would appreciate any insights or troubleshooting steps. Thanks in advance!

[abi]

This is old but I would like to shed light on one thing,

If you are not using a certificate with proper GUID assignment attribute, then the way the device record from be matched is through MAC address. However, for Apple devices they usually use MAC randomization so you have to check that its disabled (assuming Intune already have the correct device MAC address), for Android the same might be also, is that MAC address not being collected in Intune. Some MDM require that the device to be fully managed to be able to recognize its MAC address.

Please let us know, if this is the issue, if not then we can track something else.