Forum Discussion
MicrosoftWhat's New in Windows Autopatch: September Edition
Harman_Thind I'm finding that all of a sudden my devices are reporting as "Readiness failed" in a Microsoft 365 test and dev tenant I am trialling autopatch in. The two not ready states are "Microsoft Office update policy managed via Group Policy Object" and "Windows OS build, Architecture and Edition". These are fresh VM's with Win 11 and Win 10 that have never been joined to active directory. They are autopiloted and azure ad joined. The second has a link to the prerequisites but otherwise I'm having difficult finding better troubleshooting and diagnostic information.
Also, under Release management, the "Date Available to Update Group" and "Target Completion Date" are showing "Invalid Date". Harman_Thind
- Chris_Tulip
bernathe - I can't say for sure without knowing which tenant is yours specifically but I strongly suspect that the default Windows Autopatch policies have been modified. As mentioned in our documentation if those policies are modified devices will be rendered ineligible for management and there won't be an appropriate release schedule shown in the Release Management blade. If my assumption is correct, please raise a support ticket and we can work with you to bring your tenant back into compliance or if I'm wrong I'd love to get some more details!
As an aside, I totally understand the need for custom quality update schedules and we're working on that and a whole bunch of other cool features as a part of the service but we just aren't quite there! Stay tuned for future announcements 🙂
Chris_Tulip thanks for the reply. I had opened a ticket with support and they replied that
“our Dev team has identified a bug with Autopatch readiness check and fixed it. The service automatically runs these checks once a day so it may take 24 hours for devices to appear in the "Ready' tab. Feel free to contact us in case of follow-up questions or queries.”
It appears to be working now.
- Chris_TulipGreat - addresses the issue you were mentioning on the Device Registration page, glad you got it sorted out! My previous comment was regarding your second screenshot on the Release Management page - are you still seeing issues there or did that get addressed int he same ticket?
