Skip to content

Windows baseline comparison

Documented below are the results of some tests of other baseline configurations available for Intune-managed devices. I documented the experience seen during an Autopilot deployment, the general post-provisioning user experience, and any policy or security issues identified.

To conduct the tests I took an approach that is widely seen in this space, that being:

  • Baselines were imported “as-is” with no modifications made.
  • All policies were targeted at devices, rather than users.

OIB data has been presented from direct feedback from community members who have implemented the baseline in their own environments. Other baseline tests have been conducted to map against those same feedback points to provide a reasonable and unbiased comparison.

  • No reboot seen between Device and User phase.
  • User required to pass a 2nd MFA challenge to configure WHfB (not seen if skipping user ESP or ESP takes less than 15 minutes).
  • Edge automatically configured and signed-in.
  • Great productivity experience:
    • Outlook auto sign-in using primary SMTP address
    • OneDrive KFM automatically configured and signed-in
    • Office apps do not prompt first-run wizard
  • UAC allowed within the user session, able to use LAPS to diagnose or resolve issues.
  • Two transient policy errors due to Defender Additional Configuration and Defender Tamper Protection (see known issues). Resolved after reboot.
  • None
  • Simple and quick implementation of a secure, “known-good” baseline.
  • Known issues are well documented.
  • Policies are granular and easy to understand and expand on.
  • Community-driven feedback and support available.

In blogs, documentation, and presentations, Microsoft regularly states that the Intune Security Baseline is the recommended starting point for securing Windows devices.

  • Reboot seen between Device and User phase:
    • User needs to re-input user credentials.
    • User required to re-pass MFA (if not skipping user ESP).
  • User required to pass a 3rd MFA challenge to configure WHfB (or 2nd if skipping user ESP).
  • Default password length of 14, which also impacts the WHfB PIN.
  • You’ve been forced to use a 14 character PIN which you’ve probably set the same as your password.
  • Poor initial Edge user experience:
    • Account automatically identified but user asked to sign in
    • Large number of initial setup wizard prompts
  • Suboptimal productivity experience:
    • Outlook identifies the user account but does not get automatically configured
    • No OneDrive configuration, user has to sign in and configure manually
    • Prompted by Office first-run wizard to set file types
  • UAC blocked within the user session, making it difficult to diagnose or resolve issues.
  • Windows and Defender Security Baselines (still) conflict with each other.
  • No BitLocker configuration, leaving the device unencrypted.
  • Applying other policies is difficult due to the monolithic nature of the security baseline.
  • Tracking down and resolving conflicts between the security baselines is time-consuming.
  • Support relies on Microsoft documentation or available paid support channels.

Center for Internet Security (CIS) Benchmark

Section titled “Center for Internet Security (CIS) Benchmark”

The CIS Benchmarks are widely used across the industry and are considered a “gold standard” for device security configuration.

  • Reboot seen between Device and User phase:
    • User had to press CTRL+ALT+DEL.
    • User needs to re-input user credentials.
    • User required to re-pass MFA (if not skipping user ESP).
  • User required to pass a 3rd MFA challenge to configure WHfB (or 2nd if skipping user ESP).
  • Configured to not remember user credentials, so every logon requires full credential input even if WHfB is configured.
  • Poor initial Edge user experience:
    • Account automatically identified but user asked to sign in
    • Large number of initial setup wizard prompts
  • Suboptimal productivity experience:
    • Outlook identifies the user account but does not get automatically configured
    • No OneDrive configuration, user has to sign in and configure manually
    • Prompted by Office first-run wizard to set file types
  • UAC blocked within the user session, making it difficult to diagnose or resolve issues.
  • CIS (L1) Section 1 - 3.9.1.1 - Windows 11 Intune 3.0 - (L1) Ensure ‘MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)’ is set to ‘Disabled’
    • Setting completely breaks Autopilot if not removed.
  • CIS (L1) Windows Update - Windows 11 Intune 3.0.1
    • Conflicted with pre-existing Windows Update for Business ring settings.
  • BitLocker policy does not function, leaving the device unencrypted.
  • Some security gaps without implementing additional benchmarks (e.g. Edge, Internet Explorer).
  • Conflicts in Windows Update settings lead to unpredictable update behaviour.
  • Does not work out-of-the-box with Autopilot!
  • Applying other policies potentially difficult due to haphazard existing policy groupings.
  • Tracking down and resolving conflicts between the security baselines is time-consuming.
  • Support relies on vendor documentation or available paid support channels.