My next question is:

We have moved our endpoint fleet to an Autopilot V2 (Device Preparation) model. We have Surface devices which all log in using APV2 and it works exceptionally well.

Except for one major caviat.

Anyone who uses APV2 knows it only works as long as there's no hash/APV1 as APV1 trumps APV2.

We have had surface devices die on us that are still under warranty. If we were to use the Surface portal to warranty claim anything, registring a surface device automatically registers it for APV1. This is counter productive, this device now has a hash and once we attempt to log into it again, APV2 stops working (all of our policies are based around APV2 now). Not only that, but if we remove the hash again, the history of our warranty for our devices is removed.

We did contact support about this issue, and we got a collective shrug from all agents and escalated managers who were involved and were told to provide feedback. This is very poor service on Microsoft's part.