Forum Discussion
Forced Auto Install Issues
Since mid-November '25, forced auto install is not functional for our organization. Apps are loaded and installable as work apps but do not progress as an auto install from our policy.
Has anyone experienced a similar issue? No policy changes, no SW updates on the MDM client. Functionality just stopped working.
Team-
Just reset our Google Workspace account and now everything is working again. We had a former employee responsible for this and didn't close the gap when they left.
7 Replies
It sounds like a recent change in Android or the MDM server may have affected forced auto-install behavior. Check if there were any backend updates, policy enforcement changes, or Android 15 updates that could impact auto-install. Reviewing device logs and MDM audit reports can help identify why apps are no longer auto-installing, even if manual installs still work.
Thank you for your assistance collin-93​ 🤩
THTClient​ could you give us a quick update and let us know if you still need help solving this issue?
We discovered this morning that our profile was tied to an old G Suite account that is no longer supported. Hoping to re-establish this so we can accept the Terms and Conditions in Play to re-enable the functionality. I will update the thread if this fixes the issue.
Team-
Just reset our Google Workspace account and now everything is working again. We had a former employee responsible for this and didn't close the gap when they left.
Thank you for the update and for marking this as a solution THTClient​ - super helpful :)
A few teams have reported similar forced-install issues recently, so it may be a wider backend problem rather than your MDM setup. You can try re-syncing the device and policy, confirming the app is still marked as required, and pushing a small policy update to trigger a fresh pull. It’s also worth checking whether Play EMM services are showing any delays. If everything looks correct, it’s likely not a configuration issue on your end
