User Profile
KellyGM
Level 1.6: Donut
Joined 11 months ago
User Widgets
Contributions
Re: Intune - Compliance policy not assigned
Just wanted to update to say our phones with existing issues all started getting policies and apps late last night/early this morning (UK time)! Haven't figured out the trigger, we only know it wasn't an internal configuration change. Will monitor over the next few days. 🙂4.7KViews1like0CommentsRe: Intune - Compliance policy not assigned
Hi LFagni thanks so much for all the detail! I'm glad yours are working now, unfortunately ours are continuing to fail. We also have a ticket open with Microsoft but it's slow going. Just in case it helps anyone else, we are seeing about 2/3 failure rate with our devices, which are mostly the following: Samsung Galaxy A12 (Android 13) Samsung Galaxy A13 (Android 13 and 14) Samsung Galaxy A15 (Android 14) Samsung Galaxy Tab A7 (Android 12) Samsung Galaxy Tab S9+ (Android 14) We do not use any other device manufacturer so I'm unable to comment on non-Samsung devices. The A15 and Tab S9+ for sure are listed as Google-recommended devices for Android Enterprise. Also, interestingly Android for Work (which we require for BYOD) is fine, it's just Android Enterprise (fully managed) with the issue. Have not yet tested dedicated/kiosk devices. Lizzie just copying you in, in case the above info is helpful/may be passed to the developers. 🙂4.8KViews0likes0CommentsRe: Intune - Compliance policy not assigned
We are also having this issue since about the 24th of July. It seems like some devices are successful, but we are unsure why. A colleague and I have been testing the same devices for the last week and we consistently get no compliance policies, as well as existing devices not updating the Managed Play Store when newly assigned apps should be available either. Some devices are completing correctly (about 50%?) but there is no consistency when we've looked into why. We have ruled out our Intune config (nothing else has changed) and like your experience, our dynamic groups are correct and should be applying the compliance policy. I think a recent update to the Android Device Policy app might explain the issue, but yours is the first post I've seen regarding the same issue we're having!5.6KViews0likes0Comments