The answer is to configure enrollment restrictions in Microsoft Intune and set the 'Allow personally owned devices' option to 'No' for each platform. This is correct because enrollment restrictions are the native Intune policy that directly controls device ownership types, blocking personal device enrollment by preventing any device not marked as corporate-owned—via IMEI/MEID numbers or a corporate enrollment token—from joining the tenant. On the MS-102 exam, this scenario tests your understanding of the difference between enrollment restrictions, compliance policies, and device type filters; a common trap is confusing this with conditional access policies, which control access after enrollment, not the enrollment itself. The key is that enrollment restrictions gate the initial registration, making them the precise tool to block personal devices. Memory tip: think of enrollment restrictions as the bouncer at the door—set the policy to “corporate ID only” and personally owned devices are turned away before they even enter the system.
MS-102 Deploy and manage a Microsoft 365 tenant Practice Question
This MS-102 practice question tests your understanding of deploy and manage a microsoft 365 tenant. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your organization wants to use Microsoft Intune to manage devices. You need to ensure that only corporate-owned devices can enroll. What configuration should you use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure enrollment restrictions to block personally owned devices.
Option B is correct because enrollment restrictions in Microsoft Intune allow you to block personally owned devices by setting the 'Allow personally owned devices' option to 'No' for the platform. This ensures that only corporate-owned devices, which are identified by their corporate enrollment token or IMEI/MEID numbers, can enroll. This is the direct and intended method to restrict enrollment to corporate-owned devices only.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use a conditional access policy to require device compliance.
Why it's wrong here
Conditional access does not prevent enrollment.
✓
Configure enrollment restrictions to block personally owned devices.
Why this is correct
Enrollment restrictions can block personal devices.
Related concept
Read the scenario before looking for a memorised answer.
✗
Set a compliance policy requiring devices to be marked as corporate.
Why it's wrong here
Compliance policies apply after enrollment.
✗
Create a device type restriction for iOS and Android.
Why it's wrong here
Device type restrictions do not block personally owned devices.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse post-enrollment controls (like compliance policies or conditional access) with pre-enrollment restrictions, mistakenly thinking that requiring compliance or marking devices as corporate can block personal devices from enrolling, when in fact only enrollment restrictions can prevent the enrollment process itself.
Detailed technical explanation
How to think about this question
Under the hood, Intune enrollment restrictions are evaluated at the time of enrollment request, before the device is registered. When 'Allow personally owned devices' is set to 'No' for a platform, Intune checks the device's corporate enrollment token (e.g., Apple Business Manager token for iOS) or its IMEI/MEID numbers against a pre-uploaded list of corporate identifiers. If the device is not recognized as corporate, enrollment is denied immediately, preventing the device from ever appearing in Intune. This is distinct from compliance policies, which run after enrollment and can only mark a device as non-compliant but not block its initial registration.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this MS-102 question in full detail.
Deploy and manage a Microsoft 365 tenant — This question tests Deploy and manage a Microsoft 365 tenant — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure enrollment restrictions to block personally owned devices. — Option B is correct because enrollment restrictions in Microsoft Intune allow you to block personally owned devices by setting the 'Allow personally owned devices' option to 'No' for the platform. This ensures that only corporate-owned devices, which are identified by their corporate enrollment token or IMEI/MEID numbers, can enroll. This is the direct and intended method to restrict enrollment to corporate-owned devices only.
What should I do if I get this MS-102 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This MS-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MS-102 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.