Hello Merstrom,
What you are seeing is a classic case of a device that was previously enrolled in an organization’s Azure Active Directory (Azure AD) or Intune MDM. Even though Dell wiped and reinstalled Windows, the enrollment information is stored in the device’s firmware and provisioning package. That’s why, during OOBE (the initial setup wizard), Windows automatically tries to rejoin the company tenant and forces the “Work or School” login screen with the company name.
The only way to fully remove that is to break the device’s association with the company tenant. A simple reinstall of Windows does not clear the Autopilot profile or Azure AD join metadata.
The proper resolution is for the original company’s IT administrator to release the device from their Azure AD and Intune environment. They need to remove the hardware hash from Windows Autopilot and deregister the device from their tenant. Until that is done, every reinstall will continue to pull down the enrollment profile and force you into their login flow.
As the end user, you cannot override this on your own. Even if you manage to log in locally, the device remains bound to the tenant and will continue to enforce policies. You need Dell or the company that originally owned the device to confirm that the hardware hash has been removed from Autopilot and that the device object has been deleted from Azure AD. Once that is completed, a clean reinstall of Windows will behave normally and allow you to set up with a personal Microsoft account.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
Domic Vo.