Return of key functionality for Windows Autopilot sign-in and deployment experience

Maybe I missing some tech background, but could you confirm me, that if we run pre-provision environment and motherboard will be replaced what are the next steps to be able to get he machine to work?

Because it was my understanding I will simply sign to Windows and Intune should repair the hash. We don't need to delete any records etc???

Could anyone please confirm this, because this is the workaround I used. Motherboard was replaced, I signed to Windows, then there was message that our Device is having problem with work or school account, where I could click sign in, which triggered joining this device to AD Azure. I could NOT see any meesage on Endpoint with Profile status (it was signed from the first moment, when device joined Azure AD), but I can see 2 devices with exactly same name on Endpoint - just the old device keep icon for Windows autopilot device, which makes me nervous.
Intune_Support_Team