Forum Discussion
windows autopatch
Hi folks, thanks for the feedback here. The accounts that we are blocking on here are MsAdmin, MsAdminInt and MsTest. If you have these accounts in your tenant currently, you must either rename or remove these accounts to move forward with enrolling to the Windows Autopatch service as we will create these account as part of running our service.
There will be an update coming to the Windows Autopatch docs as well as the Readiness assessment tool you shared the screenshot of.
Microsoft
Hi folks, thanks for the feedback here. The accounts that we are blocking on here are MsAdmin, MsAdminInt and MsTest. If you have these accounts in your tenant currently, you must either rename or remove these accounts to move forward with enrolling to the Windows Autopatch service as we will create these account as part of running our service.
There will be an update coming to the Windows Autopatch docs as well as the Readiness assessment tool you shared the screenshot of.
it looks like a bug of the Checking Tool. These Accounts are in my Tenant, but created from the Enrollment. It looks like the failure is "normal", the checker found its own created accounts and see this as an issue.
- Harman_Thind
Hi sjansen
It sounds like you ran the assessment tooling again after enrolling into the service, can you share the steps you took to do this and why? Would love to understand if there are gaps or if you felt it was necessary to re-run. In its current state, the tool is designed to only be run prior to enrolling to Windows Autopatch.