HCHTech
Well-Known Member
- Reaction score
- 4,449
- Location
- Pittsburgh, PA - USA
I have run into the "AzureAD-domain-setup-accidentally" problem a couple of times now. Whoever setup that installation of Windows 10 made some sequence of choices in the initial setup that had this result. I haven't had time to play with a setup from scratch to see what sequence of events causes this, but I'm sure it's part of the push to use MS accounts combined with the push to use O365, probably combined with Win10Pro. They probably chose that it was a "work" computer, then created a MS account because they didn't understand local accounts, then just agreed to everything else.