Does Autopilot Convert All Targeted Devices Apply Here?

Deploy and upgrade Windows clients by using cloud-based tools Add devices to Microsoft Entra ID Enroll devices to Microsoft Intune

Answer Device 1: No (not Intune enrolled, no hash collected). Device 2: No (excluded by Group 2). Device 3: No (a Restart does not trigger Autopilot).

HOTSPOT You have an Azure AD tenant named contoso.com that contains the devices shown in the following table. exhibit The tenant contains the Azure AD groups shown in the following table. exhibit You add an Autopilot deployment profile as shown in the following exhibit. exhibit For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point. exhibit

Community Insight

The question tests whether 'Convert all targeted devices to Autopilot' actually harvests a hardware hash, and the trap is assuming Entra ID join alone or a restart is enough to produce an Autopilot deployment.

This MD-102 hotspot tests the Intune Windows Autopilot deployment profile setting 'Convert all targeted devices to Autopilot' against three devices in contoso.com. The page establishes that conversion only occurs for Intune-enrolled, hardware-hash-eligible devices that are not excluded by the profile's group scope, and that a restart alone triggers nothing.

The most common wrong approach is marking Device 1 Yes because it is Entra ID joined (or because the profile says 'all targeted devices'), when the hash is only collected from a device already enrolled to Intune and reporting to the service.

Community Discussion (16 comments)

Besxp 👍 1

Oh god, please ignore this comment. Merrybob is correct

oopspruu 👍 3

NNN if the 3rd question is actually "Restart" NNY if the 3rd question is "Reset". Convert to Windows Autopilot - This really means that Intune will automatically ask the device for its HWID and upload it. But for that to happen, the device needs to be enrolled to Intune. In this case Device1 is simple Entra Joined and not Intune enrolled so this setting doesn't take effect. Hence answer for 1st one is No until someone manually uploads the hash or enrolls it to intune.

Meek_Learner 👍 2

Device1: Not enrolled in Intune, hardware hash not registered, so Autopilot deployment won't occur on reset. Device2: Excluded from the Autopilot deployment profile (via Group2), so it won't use Autopilot on reset. Device3: Restarting doesn't trigger Autopilot deployment; it only occurs during initial setup or reset.

665d390 👍 2

YNN Device 1: It's included in the autopilot profile that states "Convert all targeted devices to Autopilot," so it will be deployed by autopilot. Device 2: Is excluded. Device 3: Restart does not have autopilot actions.

ExamBud 👍 1

No, it needs to be enrolled in Intune so it can take the hash. Device 1 will not be deployed as AP until it is enrolled.

MR_Eliot 👍 2

Y, Device is Entra ID joined. Which means the hw hash is already imported, but not yet enrolled in Intune. N, Device2 is excluded N, Restarting does nothing

OyYaGotta 👍 3

Entra ID joining has nothing to do with hashes. They need to be bulk imported or singly imported into Intune, not Entra ID. You're confusing PRT tokens with device hashes.

Merrybob 👍 23

NNN Device 1: Only devices enrolled to Intune can be used with Autopilot Ref: https://learn.microsoft.com/en-us/autopilot/configuration-requirements#:~:text=Device%20registration.%20Devices%20must%20be%20added%20to%20Windows%20Autopilot%20to%20support%20most%20Windows%20Autopilot%20scenarios. Device 2: Excluded by policy Device 3: This one says Restart. If that's true then the answer would be No. If it's meant to say Reset, then the answer would be Yes.

sn0r 👍 1

Agree with NNN I had this question on the exam, and the third option was "restart", not "reset".

Besxp 👍 1

Wrong about Device3. Resetting a device that is Intune enrolled, targeted by Autopilot profile, and not excluded, will trigger Autopilot if the profile applies.

NoursBear 👍 2

am now sure NNN

NoursBear 👍 1

Requirements An existing device can automatically register if it's: Running a supported version of Windows Enrolled in an MDM service such as Intune A corporate device that isn't 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. https://learn.microsoft.com/en-us/autopilot/automatic-registration

NoursBear 👍 2

my take would be NNY ? But I have a doubt with the 3d one, does a RESTART perform anything of the sort? Otherwise it would be NNN. If more peeps would have a think.....

krzysiek321 👍 2

for me it should be YNY

Valavanchandran 👍 3

First device is not enrolled or not run via autopilot. so reseting this device wont help, device 2 in Group2 thats in exclusion group, device3 restarting wont deploy only reseting so NNN

mp34 👍 2

Device 2 is in group 2 so will not be deployed. Device 3 is in Azure and intune so will be deployed. Device 1 I suppose not, as it doesn not say the csv has been uploaded with the hardware hash

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Device 1 answers No because 'Convert all targeted devices to Autopilot' only makes Intune request and upload the hardware hash from a device that is already enrolled in Intune; Device 1 is Entra ID joined but not Intune enrolled, so no hash is ever collected and no Autopilot deployment can occur. Device 2 answers No because it belongs to Group 2, which is configured in the profile's Exclude group box, so it is never targeted and is never converted. Device 3 answers No because the statement concerns a Restart, and rebooting an existing OS session performs no Autopilot provisioning action. Autopilot deployment only occurs during initial OOBE setup or after a Reset that re-enters that flow, so all three statements resolve to No.

Why Other Candidate Answers Are Wrong

Marking Device 1 Yes relies on the false idea that Entra ID join already imports the hardware hash, but hashes must be bulk-imported or gathered through Intune enrollment, not created by joining the directory. Reading 'all targeted devices' as unconditional also ignores that 'targeted' is bounded by the Include and Exclude group selections, which is why Device 2 in the exclusion group stays out. A Y for Device 3 would require the statement to say Reset on an eligible, enrolled, included device — a Restart performs no provisioning, reset, or conversion at all. Selectors such as YNN or YNY therefore contradict both the exclusion scope and the hash-collection requirement.

Community Comment Notes

Merrybob, with the highest like count, concluded that only Intune-enrolled devices can be used with Autopilot and that a restart yields No, which aligns with the configuration-requirements behavior. oopspruu and Meek_Learner both stressed that conversion means Intune must ask the device for its HWID, noting "Device1 is simple Entra Joined and not Intune enrolled so this setting doesn't take effect." OyYaGotta pushed back on the join-equals-hash idea, stating "You're confusing PRT tokens with device hashes." MR_Eliot and 665d390 argued the opposite (Y), treating Entra ID join as proof the hash exists, while krzysiek321 offered YNY; NoursBear and Valavanchandran converged on NNN, which the analysis supports.

Official Reference

https://learn.microsoft.com/en-us/autopilot/configuration-requirements

Exam Strategy

When a profile wording contains 'all targeted devices', first confirm the Include and Exclude group scope, then confirm the device's actual state (Entra joined vs. Intune enrolled). Treat only Reset/OOBE, never Restart, as an Autopilot trigger.

Frequently Asked Questions

Why doesn't Entra ID joining Device 1 convert it to Windows Autopilot?

Conversion requires Intune to read the device's hardware hash, which only happens on an Intune-enrolled device. An Entra ID join records directory identity, not the hardware hash, so no Autopilot profile applies.

Does restarting a device ever start a Windows Autopilot deployment?

No. Autopilot runs only during the out-of-box experience or after a Reset that re-enters setup; a Restart of an already-provisioned OS performs no Autopilot action.

More MD-102 FAQ →

Related Analysis

Practice All MD-102 Questions

Access 92 questions with complete answers and detailed explanations.

View Full MD-102 Practice Test →

← Back to MD-102 Study Guide