Jul 27 2022 10:50 PM
Hi,
During the enrollment with Windows Autopatch, my block-legacy-authentication conditional access policy is also modified automatically by the service to exclude the service accounts.
Does it mean that Windows Autopatch is using legacy authentication?
I don't think so, hence need a confirmation to undo the modification with confidence.
Many thanks.
Jul 28 2022 05:52 AM
Jul 28 2022 09:15 PM
Aug 05 2022 08:52 AM - edited Aug 05 2022 08:52 AM
Solution@Alber Thanks for the question, yes in Public Preview the authentication method for Windows Autopatch was traditional User and Password with a randomized password. With General Availability we introduced our 1st Party Enterprise App with and no longer use the Service account. We are introducing an option for customer on service account auth to transition to our Enterprise App. Stay tuned we will get an announcement out when it will be available in the MEM Portal.
Aug 05 2022 08:52 AM - edited Aug 05 2022 08:52 AM
Solution@Alber Thanks for the question, yes in Public Preview the authentication method for Windows Autopatch was traditional User and Password with a randomized password. With General Availability we introduced our 1st Party Enterprise App with and no longer use the Service account. We are introducing an option for customer on service account auth to transition to our Enterprise App. Stay tuned we will get an announcement out when it will be available in the MEM Portal.