Continue your lesson
Trace device identity, enrollment, assignment, policy evaluation, deployment, and reporting as separate stages.
Block 1 of 2Compare Settings catalog · Device configuration template · Custom OMA-URI profile · Administrative Templates profile
Current · 18 min
Compare Settings catalog · Device configuration template · Custom OMA-URI profile · Administrative Templates profile
Optional concept notes
Settings catalog
Provides searchable Intune settings that can be combined in a custom configuration profile.
Device configuration template
Groups settings for a common platform feature or management scenario.
Custom OMA-URI profile
Delivers a CSP setting that is not exposed through a standard Intune profile.
Administrative Templates profile
Configures supported Windows policy settings backed by ADMX definitions.
Complete one provider lesson, then answer four related questions. That is enough for today; more practice is optional.
Your lesson stays open here while the provider opens in another tab. Choose one source; the notes above are optional.
Block 2 of 2Compare Applicability rule · Configuration policy conflict · Per-setting status · Configuration profile assignment
18 min
Compare Applicability rule · Configuration policy conflict · Per-setting status · Configuration profile assignment
Optional concept notes
Applicability rule
Applies a profile only to devices that meet configured operating-system edition or version conditions.
Configuration policy conflict
Occurs when multiple assigned policies set the same device setting to incompatible values.
Per-setting status
Shows whether each configuration value succeeded failed conflicted or is pending.
Configuration profile assignment
Targets a device configuration to selected user or device groups.
Complete one provider lesson, then answer four related questions. That is enough for today; more practice is optional.
Your lesson stays open here while the provider opens in another tab. Choose one source; the notes above are optional.
Practice the reasoning here
Build a small fictional pilot. Map each user, device, group, policy, and report before deciding where a failed deployment should be repaired.
- State the expected result before changing or testing anything.
- Name the observation, command, log, or report that would confirm it.
- Explain why the closest alternative does not fit the same requirement.
Check the whole objective
This unlocks objective 2.2 for recall. The latest checkpoint needs 70% or higher; a lower result puts the lesson back near the front of your timeline.