Welcome to the Windows Autopatch AMA. Let's get started! Post your questions in the Comments. Our experts will be answering questions in the live stream—and others will be answering here in the chat.

Windows Autopatch looks like a massive value add to organizations and even better that its included with E3 and above licensing, I have some questions that I was hoping you could cover in the AMA:

1. Are you able to provide more detail about how Service Accounts and conditional access policy changes relate to the service, what assurances would you give to an InfoSec team that might question the security of the service accounts and the changes to conditional access?
2. Are the AzureAD Groups that are created as a part of enrollment able to be renamed to meet custom requirements that Orgs might be using already?
3. Are the Configuration Profiles able to be renamed as well?
4. What would a typical customer interaction look like where the Autopatch team/service would contact our admin with the details provided if there was an issue with a patch?
5. For customers that are already using update rings in MEM (and have a great experience doing so) what is the value proposition for migrating to Windows Autopatch?

Formatted for readability by your friendly Windows Community Manager.

While we understand the shift of planning and operation of moving from Windows Update for Business to Windows AutoPatch, once you have done the planning for WUFB, it's set and forget. Getting an understanding of the questions below will help us determine if we can make the shift and if it would be helpful. As we are in Australia, we won't be able to dial into the 'AMA". Happy for a separate call:

1. If during a ring deployment, devices are offline due to users travelling, the user is on leave and comes back. How are these devices handled?
2. General hesitation as patching is in our metrics which has board visibility. If we don't meet our SLAs, we can hold our MSP accountable. If we fail to meet our SLAs, it's now a Woodside problem. How are existing SLAs handled?
3. If there is an issue with an update ring, this has to be paused. Who calls when to proceed, and what implications does this have if we miss our patching targets?
4. At the moment, we exclude drivers/firmware. Can this be done with autopatch? An example is through Windows Update for Business, we deployed the latest sound audio driver update, and it broke our audio and stopped them working on all our devices. When a support case was raised, Microsoft (rightly so) mentioned that they couldn't be held responsible for vendors releasing faulty drivers. Another alternative would be to have a dedicated ring solely for Drivers/Firmware. Another example is the BIOS. When it updates, we don't have any granularity, i.e. device has to be plugged in, and the user isn't using it. At the moment, if we deploy it, a user could shut their laptop lid.
5. What does the reporting look like?
6. Who makes the call if an update gets pushed out and needs to be rolled back? Or if Woodside finds an issue with an update, what do we do?
7. If we have update failures, as in update failed to install. Who fixes this? Microsoft or us?

Formatted for readability by your friendly Windows Community Manager.