Nimbostratus
Hi Man_Yau,
Could you share the logs from the APM, a 500 error is sent by the server, could you review the logs from the user in the Mdm, could you confirm the credentials or test with another user?
NimbostratusHi Sebastiaan,
This is only message i see in the logs: 019dffff:3: (null)::00000000: {} /Common/intune-test3: Error during updating device details: Mdm server internal error (Mdm internal server error for get all non compliant devices request: 500)
When F5 tries to login to Azure, we seen successful sign-in, the credentials looks correct. It's not the user tries to logon, it's the step before. F5 tries to logon to fetch compliance device status from intune.
Hi
I have found an article that mentions this:
"If user has already migrated to Microsoft Graph, from Azure AD Graph, then they will need to upgrade the APM to v17.0 in order for APM to connect to Intune for APM's Endpoint Management System (EMS) agent creation."
https://my.f5.com/manage/s/article/K79439133
Did you have any change in your intune service?
NimbostratusHi,
I have configured the Endpoint Management System on device is running 17.1.1.2, i still have same issue. User is indeed migrated to Microsoft Graph.
in the logs after querying to: 019dffff:5: (null)::00000000: {} /Common/ms_intune-test: Start querying devices from https://fef.msub07.manage.microsoft.com/TrafficGateway/TrafficRoutingService/ResourceAccess/ComplianceRetrievalService
i see the error message:
019dffff:3: (null)::00000000: {} /Common/ms_intune-test: Error during updating device details: Mdm server internal error (Mdm internal server error for get all non compliant devices request: 500)
Intune service configuration has not change
