Intune device compliance and configuration status delay

%3CLINGO-SUB%20id%3D%22lingo-sub-1092506%22%20slang%3D%22en-US%22%3EIntune%20device%20compliance%20and%20configuration%20status%20delay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1092506%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3Esince%20a%20couple%20of%20weeks%20we're%20(checked%20within%20many%20tenants%20EU%20region)%20facing%20an%20issue%20with%20Intune%20reporting%20latency.%20Device%20compliance%20and%20device%20configuration%20profile%20status%20remains%20either%20%22pending%22%20for%20config%20profiles%20or%20%22not%20evaluated%22%20for%20compliance%20policies.%3C%2FP%3E%3CP%3EAs%20both%20are%20applied%20successfully%20to%20the%20device%20it%20pretty%20much%20looks%20like%20a%20delay%20within%20the%20reporting%20instance%20of%20Intune.%3C%2FP%3E%3CP%3EAnyway%20this%20issue%20could%20become%20a%20real%20problem%20in%20case%20of%20troubleshooting%20an%20Intune%20managed%20device%20during%20enrolment.%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20the%20latency%2C%20until%20a%20valid%20status%20is%20reported%20within%20Intune%2C%20is%20something%20about%201-2%20hours.%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20a%20ticket%20already%20ongoing%20for%20this%20topic%2C%20but%20we%20received%20a%20somehow%20questionable%20feedback%20from%20Microsoft%3A%20there%20is%20no%20SLA%20on%20reporting%20frequency...%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20answer%20is%20somehow%20funny%2C%20as%20the%20reporting%20latency%20between%20the%20device%20and%20Intune%20was%20working%20perfectly%20fine%20during%20the%20last%202%20years%2C%20with%20an%20update%20frequency%20aligned%20to%20the%20sync%20frequency%20(every%203%20min%20first%2030%20min)%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20can%20you%20kindly%20check%20this%20and%20fix%20it...%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3CP%3EThomas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1092506%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1145803%22%20slang%3D%22en-US%22%3ERe%3A%20Intune%20device%20compliance%20and%20configuration%20status%20delay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1145803%22%20slang%3D%22en-US%22%3E%3CP%3Ewe%20are%20facing%20the%20same%20issue%20as%20well...started%20in%20dec19%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi all,

since a couple of weeks we're (checked within many tenants EU region) facing an issue with Intune reporting latency. Device compliance and device configuration profile status remains either "pending" for config profiles or "not evaluated" for compliance policies.

As both are applied successfully to the device it pretty much looks like a delay within the reporting instance of Intune.

Anyway this issue could become a real problem in case of troubleshooting an Intune managed device during enrolment. 

Currently the latency, until a valid status is reported within Intune, is something about 1-2 hours. 

There is a ticket already ongoing for this topic, but we received a somehow questionable feedback from Microsoft: there is no SLA on reporting frequency... :) 

This answer is somehow funny, as the reporting latency between the device and Intune was working perfectly fine during the last 2 years, with an update frequency aligned to the sync frequency (every 3 min first 30 min) 

So can you kindly check this and fix it...

Thank you

Thomas

1 Reply
Highlighted

we are facing the same issue as well...started in dec19