4.1.4. Security Baselines
💡 First Principle: Hardening Windows from scratch means making hundreds of decisions, and the Microsoft teams that build each product already have recommended answers. A baseline lets you start from their answers and record only your deviations. Because a baseline is a snapshot of one version of those recommendations, keeping it current is a deliberate act — nothing upgrades behind your back.
What a baseline is. Security baselines live at Endpoint security > Security baselines. Each is a group of preconfigured settings recommended by the relevant product security team, and creating a profile from one deploys many settings at once. Windows baselines apply to Windows 11 and Windows 10 version 1809 and later. The current versions you should recognize:
| Baseline | Latest version | Note |
|---|---|---|
| Security Baseline for Windows 10 and later | 26H2 | The core Windows hardening baseline |
| Microsoft Defender for Endpoint baseline | 24H1 | Optimized for physical devices; not recommended for VMs or VDI |
| Microsoft 365 Apps for Enterprise | Version 2512 | Office app hardening |
| Microsoft Edge Baseline | Version 139 | Browser hardening |
| Windows 365 Security Baseline | 24H1 | Cloud PCs; a separate Windows 365 for Agents baseline also exists |
| HoloLens 2 | Advanced and Standard security, Version 1 | Mixed-reality devices |
A Local AI Agent Baseline (preview) and an audit-only STIG baseline for GCC High tenants also appear in the list. Microsoft doesn't recommend preview baseline versions for production.
Licensing and permissions. Baselines need Intune Plan 1. A baseline doesn't license the product it configures: assigning the Defender for Endpoint baseline doesn't grant Defender rights. The least-privileged built-in role that can manage baselines is Policy and Profile Manager.
Creating one. Select the baseline, then Create policy, and walk through Basics, Configuration settings (with Settings insight hints), Scope tags and Assignments. Intune pushes the profile as soon as it's created. Assign to user or device groups to match the scope of the settings, which can mean splitting user and device settings across profiles.
Conflicts. Baselines are a common source of conflicts, because they set non-default values while endpoint security and configuration policies default to Not configured. Different baselines can also include the same setting with different default values, and Intune can't choose between them. You can deploy multiple baselines and multiple instances of one baseline, so review them against each other and against your other policies. Baselines interact with other policies in less obvious ways too: the Defender baseline can enable a TPM startup PIN that blocks silent BitLocker (4.1.2).
Versions and updates. This is where most exam questions land:
- Only the most recent version of a baseline can create new profiles.
- When Microsoft releases a new version, existing profiles stay on their version and their settings become read-only. You can still edit the name, description and assignments.
- To move a profile forward, select it and choose Update Version, then either Accept baseline changes but keep my existing setting customizations or Accept baseline changes and discard existing setting customizations.
- The update always targets the latest version and creates a side-by-side copy. The original is untouched, and the copy has no assignments and no scope tags. You assign the copy, remove the old profile's assignments to avoid conflicts, and delete the old profile once it's unassigned.
Microsoft recommends testing a version update on a duplicate first; duplicating copies settings and scope tags but not assignments, so the test copy doesn't reach production by accident. You can't convert one baseline type into another, such as Defender into Windows.
Removing a baseline doesn't necessarily undo it. Unassigning a profile, or setting a value to Not configured, might not revert the device setting: each CSP handles removal differently, and the old value can remain until something else changes it. And on co-managed devices, the Device configuration workload must be switched to Intune for baselines to apply.
⚠️ Exam Trap: It's natural to assume a Microsoft-maintained baseline profile upgrades itself when a new version ships. It doesn't. The profile stays on the version it was created from. Update Version creates a new side-by-side profile on the latest version — without the original's assignments or scope tags — and until you assign that copy and retire the original, devices keep receiving the old version's settings.
Reflection Question: You updated your Windows baseline profile to the 26H2 version last week, yet devices still report the old settings and nothing new appears in reporting. What step did you most likely skip, and what should you do with the original profile afterward?