Dom Cote : theoretically, the problem is not the reset, which is still sth understandable from a technical point of view. The problem are these steps :
- step 2.5 : contact the user, guide him to collect the hardware hash, and send it to you (by email in case you have no SCCM infra?). Also share every CSV file with your colleagues, in case sth goes wrong at Step 4 and someone need to delete and reupload a hash.
- step 3.5 : Intune Admin to wait until AP profile is assigned to the new AP record in the new tenant. In 95% of the cases, profile is assigned within few minutes. Unfortunately, this can sometimes take few hours with no reason (sometimes even 24 hours, but this is still an acceptable processing timeframe according to MS).
The positive point of this article is that it is made very explicit there is no much other solution, if you do not want to use the purchase new Windows devices path.
Realistically, purchasing new devices makes your process fully decoupled from the old tenant, reduce probabilities that your company branding is not appearing with you reach OOBE phase after reset, and endusers can do the transition anytime without interacting with IT support guys. They are also less stressed if sth goes wrong...especially if you also add a new MFA account enrollment on their mobile phones at same time, because most likely new user identity in the new tenant.