Microsoft 365 Endpoint AdministratorManage devices and apps (55-60%)Medium
A Microsoft 365 Endpoint Administrator needs to deploy a custom configuration profile to a specific group of Windows 11 devices. This configuration requires setting a custom registry value that is not directly available through standard Intune device configuration templates. Which profile type should the administrator choose, and what is its underlying mechanism for this scenario?
- ADevice configuration profile (Templates) using a custom OMA-URI.
- BDevice configuration profile (Settings catalog) using a custom OMA-URI.
- CDevice configuration profile (Custom) using a custom OMA-URI.
- DDevice configuration profile (Settings catalog) using a custom ADMX.
Show answer & explanationAnswer & explanation
Correct answer: C. Device configuration profile (Custom) using a custom OMA-URI.
To deploy a custom registry value not available in standard templates or the Settings Catalog, a 'Custom' device configuration profile is required. This profile type uses Open Mobile Alliance Uniform Resource Identifier (OMA-URI) settings to define custom configurations that Intune then pushes to devices.
Why the other options are wrong
- A. Templates use predefined settings; OMA-URI is used with the 'Custom' profile type.
- B. Settings Catalog does not directly use custom OMA-URI for configuring settings; it exposes predefined settings.
- D. Settings Catalog uses predefined settings; custom ADMX is for Group Policy-like settings, not direct OMA-URI.
Intune Custom OMA-URI Profile
A Custom device configuration profile in Intune allows administrators to deploy settings to devices using Open Mobile Alliance Uniform Resource Identifier (OMA-URI), useful for configurations not available in standard templates or the Settings Catalog.
- Uses OMA-URI strings to define settings.
- Provides granular control over device configuration.
- Often used for registry keys, custom security settings, or CSP settings.
Memory trick: OMA-URI: The 'Custom' route for unique settings.