Yesterday I ran into an issue when adding a Surface Pro 4 to Autopilot. The machine is not new and has been used before in a traditional setup, AD joined and managed by SCCM. After recovering the Surface with the USB recovery image, I used the get-windowsautopilotinfo powershellscript inside of the OOBE to collect the necessary information in a XML

After entering the Microsoft Store for Business I’ve tried to add it. This threw an error. Luckily you can download the error as a csv file.

After looking up the error wadp009 at https://docs.microsoft.com/en-us/microsoft-store/add-profile-to-devices#autopilot-device-information-file-error-messages

Since I’ve used the script before, I did a quick check and the last version is dated February 27^th, and is the one I’ve been using successfully in a demo 2 weeks ago. So I didn’t believe the explanation of the error.

I decided to try adding the machine to AutoPilot by using the Intune portal. This ended up in a timeout after 10 minutes and no useful error message.

Since I was already logged into the portal, I did a quick check by searching for the previous name of the Surface. In our traditional setup we use the serial number with a prefix. And there it was, it was known as Azure AD Registered.

After deleting this object, importing in the Microsoft Store for Business was successful and the Surface was ready for use.