Allow Autopilot registration via either Email or Hardware Hash
Currently, to register a device for Autopilot, it's hardware hash needs to be uploaded to the portal via
A) the vendor (partner portal)
B) Manually - the device needs to be progressed past the OOBE and the script needs to be run to extract the hardware hash, the device is then reset.
Whilst A) is great for large volume orders coming from the manufacturer / reseller, what about ad-hoc rapid purchases required immediately. B) is a larger administration overhead which multiplies by the number of ad-hoc devices required.
During OOBE on a non-registered device, at the page, "Sign in using a Microsoft Account or create a local account" you could actually sign in using your firstname.lastname@example.org and based on the @company.com are redirected to your corporation sign in page and then Autopilot continues from there.
There would be security concerns (compromised email could lead to the ability to create corporate network accessible device or at very least corporate image), but additional security layers could be added for email registered devices which would limit the risk from this attack vector, you could restrict ad hoc deployments via portal approval required, admin approval, etc etc. Whilst Hardware Hashed registered devices are auto-approved.