Streamlined Surface registration support for Autopilot

Published 09-15-2020 04:21 PM 11.1K Views

We’re pleased to announce simplified options for registering Surface devices to your Azure AD tenant for Windows Autopilot deployment. Beginning today, customers and partners can submit registration requests directly to Microsoft Support.  


The streamlined process means customers no longer need to harvest their own hardware hashes. Instead, they just open a ticket and get the hashes or request Microsoft to register their Surface devices on their behalf, reducing the cost and time hit, especially for customers without dedicated IT resources. This registration by Microsoft also enables Device Firmware Configuration Interface (DFCI) on those devices, allowing customers to make their devices more secure.


Getting started


Before submitting requests, you’ll need to have some basic information about your Azure AD environment and the devices you want to register including:


  • Azure Active Directory Tenant ID
  • Azure Active Directory Domain Name
  • Proof of ownership
  • Device serial numbers


For complete details, go to Surface Registration Support for Windows Autopilot.  


Zero-touch provisioning


We hope this new initiative will enable more customers to take advantage of zero touch provisioning for full lifecycle management. If you're not familiar with Windows Autopilot, registration for new or recycled devices allows IT admins to configure Autopilot profiles that can automatically be applied to those devices. Devices are then delivered directly to an end user who needs only to power the device on, connect to a network, and enter their organization credentials. The device will be provisioned into a fully business ready state --  secured and managed with all the apps that they need to be productive.  


To learn more, check out Windows Autopilot and Surface devices and visit Windows Autopilot - Microsoft 365.


Occasional Contributor

Awesome, thanks for  the share!


Now AutoPilot looks like a feature of the Surface device. That was a looooong way. But great to have a process in place. I hope, this will be a worldwide service, right? When are you good to go? September is now... The link is still generic - shows the generic support site, where the business customer has to answer 20 questions before placing the request.
Re DFCI - please make clear in the docs what kind of partner - direct/indirect - can configure the DFCI profile that will take effect. Please don’t assume that partner means “any kind of” - distributor, OEM, CSP direct or CSP indirect. Currently is does not work when configured by an indirect CSP partner. And btw I’m aware that meanwhile only 3 devices can support the DFCI.
Anyway - good news.





Hi @Red Flag,


When we launched Autopilot for Surface back in January 2018, we mainly focused on partner-led registrations which should still be the main source of autopilot registrations for most Surface customers. Microsoft has been informally supporting these types of requests since launch but we have now formalized it as a complement to the service from partners. It is put in place for customers who would rather Microsoft register their devices for variety of reasons or want to register themselves by using the hardware hashes.


DFCI should be configured by the customers within Microsoft End-point Manager admin center after they are registered by either the Direct CSPs, Indirect Providers or Microsoft. Please note that Indirect Resellers cannot register devices to Autopilot which means those devices will have to be registered by Microsoft Support to work with DFCI.


The service is live now. I am not sure why you see a generic site. This is what you should be seeing when you click the support link:


Untitled picture.png


For Surface partners enabled for Windows Autopilot services, please visit this link:


Hi @Oz Ayakta 

Thank you for not leaving this unanswered! Link to the AutoPilot registration directs now the proper form. Great!

Regarding DFCI – I’m referring to docs which don’t state clear enough what is meant with “CSP Partner”. My company is a CSP partner (Indirect Reseller but it doesn’t allow us to enable DFCI. So, your statement is clear – however docs are still misleading while saying “By design, DFCI management requires external attestation of the device’s commercial acquisition through an OEM or a Microsoft CSP partner registration to Windows Autopilot.”

Thanks for enabling the service. With that, the Surface footprint deployed with AutoPilot in SMB can increase. SMC customers can really benefit from that. 100 devices have been proactively quoted last week by my company.


It is great to hear that this service will enable partners like you to get devices registered to Autopilot with ease. Really glad to have partners like you.


I will provide the feedback on partner center documentation about DFCI to the appropriate team. Thank you for the feedback.

Version history
Last update:
‎Sep 15 2020 04:22 PM
Updated by: