Hello,

 

Hope you are doing good.

 

Till now I have share many important information which many has query on day to day life. We have cover below topics.  Now you have required information on think how autopilot works let make more clear. How we shall go with deployments. Today we will cover on deployment types and many more.

 

Windows-AutoPilot-Overview

Windows Autopilot scenarios

Windows AutoPilot Capabilities

Requirements for Windows AutoPilot

 

1. Azure AD Join:

 

 

2. Hybrid Azure AD Join:

 

The Intune Connector joins the device to the on-premises domain. Users don't need permissions to join devices to the on-premises domain. This behavior assumes that you configure the connector for this action on the user's behalf.

 

Windows AutoPilot Device Registration:

1. OEM Registration

When you purchase devices from an OEM, that OEM can automatically register the devices with the Windows Autopilot.

 

Customer Consent:

Before an OEM can register devices for an organization, the organization must grant the OEM permission to do so. The OEM begins this process with approval granted by an Azure AD global administrator from your organization.

 

        Supported OEMS:

1. Manual Registration:

Ideally, registration of a device with Windows Autopilot is performed by the OEM, reseller, or distributor from which the device was purchased. However it is also possible to register devices manually. You might need to register a device manually if:

• The device was obtained from a non-participant device manufacturer or reseller.
• The device is a virtual machine (VM).
• The device does not otherwise qualify for automatic registration, such as an existing legacy device.

To manually register a device, you must first capture its hardware hash. Once this process has completed, the resulting hardware hash can be uploaded to the Windows Autopilot service. Because this process requires booting the device into Windows to obtain the hardware hash, manual registration is intended primarily for testing and evaluation scenarios.

1. Automatic Registration:

 

You can automatically register an existing device if it's:

 

• Running a supported versionof Windows
• Enrolled in an MDM service such as Intune
• A corporate device that's not already registered with Autopilot

For devices that meet these requirements, the MDM service can ask the device for the hardware hash. After it has that, it can automatically register the device with Windows Autopilot.

 

 

2. Partner Registration:

Customers may purchase devices from resellers, distributors, or other partners. As long as these resellers, distributors, and partners are part of the Cloud Solution Partners (CSP) program, they too can register devices for the customer.

As with OEMs, CSP partners must be granted permission to register devices for an organization. This process is described in the CSP authorization section of the Windows Autopilot customer consent article. In summary:

 

• The CSP partner requests a relationship with the organization. That organization's global administrator approves the request.
• After the approval, CSP partners add devices using Partner Center, either directly through the web site or via available APIs that can automate the same tasks.

For Surface devices, Microsoft Support can help with device registration.

In Next we will cover  AutoPilot will workflow