Forum Discussion
20H2 Removing Device from Azure Domain
My organization has started to observe that devices who have processed the recent 20H2 update are no longer prompted to login with their azure ad account. Upon investigation via access of system ...
We're having the exact same issue. Been offloading clients from RDSH's to local devices as everything is becoming cloud-based.
However; recent updates seem to break AzureAD connection. Devices are still present in AzureAD, but on the device there is no notice of any domain-joined stuff..
Figured out the same fix as you described: create local account via our software monitoring tool, remove device from AutoPilot/AzureAD and rejoin the device.
Luckily no files are lost as the users can then login to the same account they used to, keeping their local files.
This is a very bad update; these shenanigans are costing us a lot of time..
