Forum Discussion

Harman_Thind's avatar
Harman_Thind
Icon for Microsoft rankMicrosoft
Sep 08, 2022

What's New in Windows Autopatch: September Edition

Check out the latest Monthly Blog on 'What's new in Windows Autopatch: September 2022'! This blog highlights the following:
  • Windows Autopatch will create the following enterprise application: Modern Workplace Management in your tenant
    • This is a limited enterprise application with elevated privileges. We use this account to manage the service, publish baseline configuration updates, and maintain overall service health. For more information, see Changes made at tenant enrollment
    • This change will also remove the Windows Autopatch service accounts, related AAD groups and conditional access policy that were previously deployed as part of the enrollment process.
  • Post-registration device readiness checks
  • Reporting for Quality Updates
 Let us know what you think about the latest changes! As always, keep the discussions, questions and feedback coming!
 
Harman Thind
Product Manager | Windows Autopatch
 

7 Replies

  • bernathe's avatar
    bernathe
    Copper Contributor

    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.

     

     

    • bernathe's avatar
      bernathe
      Copper Contributor

      Also, under Release management, the "Date Available to Update Group" and "Target Completion Date" are showing "Invalid Date". Harman_Thind 

       

      • Chris_Tulip's avatar
        Chris_Tulip
        Icon for Microsoft rankMicrosoft

        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 🙂

         

         

Resources