wroot - regarding this comment:
That's what i am saying too. I don't understand who is the target audience for this service. Those that don't care about testing, rings and such won't care about this one either. Others would want to retain some control.
Our intent with Autopatch is to provide a service that meets the needs a broad and diverse set of customers. We believe we need to provide a service where we are "the update admin" for a range of different customer types. Some customers do not care about how updates are deployed, they just need help if something goes wrong. Others need customization options to tailor the experience (for example update my executive devices last, and more). So there will be a range of customers where on one extreme they just want us to "do everything", and then on the other end are customers with unique business logic or intent that needs to be honored while we keep their devices and managed apps up-to-date.
I think that there is fine line. We are not asking customers to configure detailed policies, but rather tell us, "the update admin" the business rules that need to be followed, and let our service deliver this outcome. Admittedly our capabilities will need to grow in this area as we get feedback from the community and customers on specific business rules they might need.
Hopeful this better explains the positioning of Autopatch, and thank you for the comment