Hi I have a couple of questions regarding AutoPilot user driven experience.
I am doing some testing during the autipilot process the user see's two options
1) Privacy settings
2) Personal or Work or School
Question is can we eliminate the Privacy settings options so the user is not able to set them and enforce corporate work account and not give an option for personal account login?
Thanks
@berket2020, Thanks for the reply. I am glad to hear that it is working. To find which configuration policy conflict with Autopilot profile. we can check if any policy in the following link is existing in the existing configuration profile:
https://docs.microsoft.com/en-us/mem/autopilot/policy-conflicts
If there's any finding, feel free to let us know.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
@berket2020,To eliminate the Privacy settings options, we can set the "Privacy settings" with the value "Hide". 
To enforce corporate work account, we can remove the "change account" to see if it can help. To do this, we can follow the steps as below:
1. Configure company branding in Azure AD.
2. Ensure the device is windows 10 1809 or later.
3. Set "Hide change account options" as Hide.
We can see more details in the following link:
https://docs.microsoft.com/en-us/mem/autopilot/profiles
Hope it can help.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Yes I checked they have it set both Privacy and Hide account options to hide but the computer still is bringing them up.
Any idea why that is?
Thanks
@berket2020, Thanks for the reply. I have met a similar case before. The issue is caused by one conflict policy setting with Autopilot.
https://docs.microsoft.com/en-us/answers/questions/121816/autopilot-privacy-oobe-not-hidden.html
Please check if there's any policy conflict in our environment:
https://docs.microsoft.com/en-us/mem/autopilot/policy-conflicts
Hope it can help.
@berket2020, Hope things are going well. i am writing to see if our issue is fixed now. If there's any update, feel free to let us know.
6 people are following this question.
