A company is using Microsoft Intune to manage its Windows 11 devices. The IT department needs to deploy a custom security baseline that includes settings not found in Microsoft's default security baselines or the Settings Catalog. These settings are derived from a specific industry compliance standard. Which Intune configuration profile type should be used to deploy these unique settings?
- ADevices -> Configuration profiles -> Device restrictions for Windows
- BDevices -> Configuration profiles -> Custom
- CDevices -> Configuration profiles -> Settings catalog
- DEndpoint security -> Security baselines
Show answer & explanationAnswer & explanation
Correct answer: B. Devices -> Configuration profiles -> Custom
For deploying unique or custom security settings not available in Microsoft's default security baselines, device restrictions, or the Settings Catalog, a 'Custom' device configuration profile is the appropriate choice. This allows administrators to use OMA-URI (Open Mobile Alliance Uniform Resource Identifier) to configure specific CSPs (Configuration Service Providers) on Windows devices.
Why the other options are wrong
- A. Device restrictions for Windows provide a set of common restrictions but may not include highly specific, custom security settings from industry standards.
- C. The Settings Catalog provides a comprehensive list of settings, but if a setting is truly 'not found' there, it cannot be used for that specific purpose.
- D. Endpoint security > Security baselines are Microsoft-curated security settings; they do not allow for custom, unique settings outside their scope.
Intune Custom Profile (OMA-URI)
A Microsoft Intune device configuration profile type that allows administrators to deploy highly specific or custom settings to devices by manually configuring OMA-URI paths and values, typically used for settings not exposed elsewhere in Intune.
- Provides maximum flexibility for device configuration.
- Requires knowledge of Windows CSPs and OMA-URI syntax.
- Often used for industry-specific compliance or unique organizational requirements.
Memory trick: When standard options fail, Custom OMA-URI prevails.