HomeServicesManaged IT ServicesAI DeploymentAccredOneInsightsAnswersAboutFree Consultation
Windows Security & Endpoint Engineering

Windows 11 26H2 Security Baseline: Stage It Safely

TL;DR

Microsoft’s Windows 11, version 26H2 security baseline changes four settings from 25H2: Windows Ready Print driver ranking, the TLS 1.2/1.3 encryption recommendation, and two User Account Control settings that turn on Administrator protection (added in the v2 package on Oct 8, 2026). Existing Intune baseline profiles do not move to 26H2 on their own, and Administrator protection is not a safe default everywhere: Microsoft says not to enable it on LAPS-managed devices, Hyper-V hosts, Windows 365 Cloud PCs, or Azure Virtual Desktop session hosts.

  • Download the v2 package from the Security Compliance Toolkit and diff it against your current posture with Policy Analyzer.
  • In Intune, use Update Version on a copy of your Windows baseline profile and assign it to a pilot group only.
  • Pilot Administrator protection separately through a Settings catalog policy, and exclude LAPS-managed, Hyper-V, Cloud PC, and AVD devices.
  • Test printing and any appliance that still needs TLS 1.1 before broad rollout.
  • Move assignments off the old profile once the new one is clean, so the two don’t conflict.

Microsoft published the Windows 11, version 26H2 security baseline on September 29, 2026, then released an updated v2 package on October 8, 2026 to reflect the general availability of Administrator protection. The Intune version of the 26H2 baseline arrived the week of October 5, 2026.

A baseline is a starting point, not a compliance certificate. It is a versioned set of Microsoft recommendations that still needs conflict checks, application testing, named exceptions, and a staged rollout. This guide covers what changed, how to stage it in Intune and Group Policy, and how to prove it worked.

Why this matters for small and mid-sized businesses

Most small and mid-sized businesses that use Intune deploy the Windows security baseline close to its defaults, because there is no dedicated team to tune each setting. That makes the 26H2 changes land directly on users:

  • Administrator protection changes how every admin elevation works. Admins approve each elevation with Windows Hello or credentials, and elevated apps run in a separate profile. Microsoft documents that SSO from the normal session isn’t available in the elevated session and that network drives aren’t reachable from elevated apps. Help-desk and line-of-business install workflows are where this shows up first.
  • Many SMBs use Windows LAPS for local admin accounts. Microsoft lists LAPS-managed devices under “when not to enable” Administrator protection, so applying the v2 defaults blindly can conflict with a control you already rely on.
  • Old printers and appliances are common in small offices. Driver ranking and dropping TLS 1.1 from the IE encryption setting can surface as “printing broke” or “the admin page won’t load” tickets.
  • Doing nothing has a cost too. Your existing Intune profile stays on its old version, its settings become read-only, and you can’t edit them until you update to 26H2.

What changed

  • Sep 29, 2026: Microsoft published the Windows 11, version 26H2 security baseline in the Security Compliance Toolkit (Microsoft Security Baselines blog).
  • Week of Oct 5, 2026: The Windows 11, version 26H2 security baseline became available in Intune. Existing profiles don’t update automatically, and Configure NetBIOS settings is left out because it’s only supported on Windows Insider builds (Intune what’s new).
  • Oct 8, 2026: Microsoft updated the 26H2 baseline to a v2 package that enables Administrator protection through two UAC settings (Microsoft Security Baselines blog).
  • Oct 13, 2026: Message Center MC1506291 confirmed that, for organizations using the Windows security baselines, Administrator protection is enabled by default starting with the October 2026 Windows security update, across the 26H2, 25H2, and 24H2 baselines (MC1506291; Administrator protection on Learn).
  • Oct 21, 2026: Guide reviewed against current Microsoft Learn documentation.

What changed from Windows 11 25H2

Microsoft lists four policy changes between the 25H2 and 26H2 (v2) baselines. Setting names below are the Group Policy names Microsoft uses in its announcement.

Setting26H2 baseline valueWhat to test
Printers > Configure Windows Ready Print driver rankingEnabled. Microsoft says this reduces reliance on third-party print drivers and the attack surface they bring.Printer discovery, queue creation, driver features (finishing, trays), print servers, and label or receipt printers.
Internet Explorer > Internet Control Panel > Advanced Page > Turn off encryption supportChanged from TLS 1.1 and TLS 1.2 to TLS 1.2 and TLS 1.3 only.Old appliances, embedded browser controls, and management consoles that still negotiate TLS 1.1.
User Account Control: Configure type of Admin Approval Mode (v2)Admin Approval Mode with Administrator protection.Installers, elevation-heavy apps, remote support tools, LAPS, Hyper-V, and RDP.
User Account Control: Behavior of the elevation prompt for administrators running with Administrator protection (v2)Prompt for credentials on the secure desktop.Windows Hello enrollment for admins, and how often admins see prompts during normal support work.

One gap to know about: as of this review, the Intune Version 26H2 baseline settings reference lists the existing UAC settings but not the two Administrator protection settings. Microsoft has not published an Intune baseline update for v2. In Intune, manage Administrator protection with a Settings catalog policy (steps below) rather than expecting the baseline profile to carry it.

Licensing and prerequisites

RequirementDetails
Intune licenseMicrosoft Intune Plan 1 (included in Microsoft 365 Business Premium, E3, and E5). Required to deploy security baselines through Intune.
Intune rolePolicy and Profile Manager is the least-privileged built-in Intune role that can manage security baselines. A custom role needs Organization: Read and Security baselines: Assign, Create, Delete, Read, Update.
Group Policy pathSecurity Compliance Toolkit download (Windows 11, version 26H2 baseline, plus Policy Analyzer and LGPO tools) and rights to create and link GPOs in Active Directory.
Administrator protectionAvailable since KB5120998 (August 2026). Supported on Windows 11 Home, Pro, Enterprise, and Education. Not supported on Windows 365 Cloud PCs, Azure Virtual Desktop session hosts, or Windows Server. A restart is required to turn it on or off.
Co-managed devicesSwitch the Configuration Manager Device configuration workload to Intune before relying on Intune baselines.
Graph PowerShell (optional)Microsoft Graph PowerShell SDK (Microsoft.Graph.Authentication for Invoke-MgGraphRequest). Delegated permission DeviceManagementConfiguration.Read.All to read policies. The configurationPolicies endpoint is in Graph beta.

Step-by-step: stage the 26H2 baseline

1. Compare the package against what you run today

  1. Download the Windows 11, version 26H2 v2 baseline and Policy Analyzer from the Security Compliance Toolkit.
  2. In Policy Analyzer, load the 26H2 baseline and your current GPOs (or the 25H2 baseline you approved) and export the differences to Excel.
  3. For Intune, note which settings you customized in your current Windows baseline profile. The update wizard can keep them, but you should know what they are.

2. Create a pilot copy of the Intune baseline on 26H2

  1. Microsoft Intune admin center > Endpoint security > Security baselines > Security Baseline for Windows 10 and later > Profiles.
  2. Select the checkbox for your current profile, then select Update Version.
  3. Choose Accept baseline changes but keep my existing setting customizations (or discard them if you want a clean default), then select Create.
  4. On Basics, give the new profile a clear name, for example “Win baseline 26H2 – pilot”.
  5. On Configuration settings, review the four changed settings and any setting you customized.
  6. On Assignments, assign only a pilot device group. Scope tags and assignments are not copied from the old profile.
  7. Select Create. The original profile stays unchanged and keeps its assignments, so exclude the pilot group from it to avoid conflicts.

No existing profile yet? Use Endpoint security > Security baselines > Security Baseline for Windows 10 and later > Create policy; new profiles always use the latest version.

3. Pilot Administrator protection separately

Because the Intune 26H2 baseline reference doesn’t list the Administrator protection settings, use the Settings catalog so you can scope it on its own:

  1. Microsoft Intune admin center > Devices > Manage devices > Configuration > Create > New policy > Platform Windows 10 and later, Profile type Settings catalog.
  2. Add settings from the Local Policies Security Options category: User Account Control Type Of Admin Approval Mode and User Account Control Behavior Of the Elevation Prompt for Administrator Protection.
  3. Assign to a small pilot device group. Exclude LAPS-managed devices, Hyper-V hosts, Windows 365 Cloud PCs, and AVD session hosts.
  4. Restart pilot devices; the change doesn’t apply until reboot.

Group Policy equivalent: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options, then set User Account Control: Configure type of Admin Approval Mode to Admin Approval Mode with Administrator protection. To turn it off, set it back to Legacy Admin Approval Mode (Default) and restart. If you import the v2 GPO baseline, this is already set, so adjust it for any excluded device groups.

4. Inventory baseline profiles with Graph PowerShell

Use this read-only script to list every Intune baseline profile, its template version, and whether it’s assigned. It uses the Graph beta configurationPolicies endpoint, where baseline profiles report templateFamily as baseline.

Connect-MgGraph -Scopes "DeviceManagementConfiguration.Read.All"

$uri = "https://graph.microsoft.com/beta/deviceManagement/configurationPolicies"
$policies = @()
do {
    $page = Invoke-MgGraphRequest -Method GET -Uri $uri -OutputType PSObject
    $policies += $page.value
    $uri = $page.'@odata.nextLink'
} while ($uri)

$policies |
    Where-Object { $_.templateReference.templateFamily -eq "baseline" } |
    Select-Object name,
        @{n = "Baseline"; e = { $_.templateReference.templateDisplayName }},
        @{n = "Version";  e = { $_.templateReference.templateDisplayVersion }},
        isAssigned, lastModifiedDateTime |
    Sort-Object Baseline, Version |
    Format-Table -AutoSize

Any assigned Windows baseline profile that isn’t on the 26H2 version is a candidate for update. Creating and updating baseline profiles is easiest in the admin center; the script is for inventory and evidence.

5. Expand in rings

  1. Once the pilot is clean for one to two weeks, add the next ring to the 26H2 profile and exclude it from the old one.
  2. Repeat until the old profile has no assignments, then delete it if you no longer need it as a record.
  3. For Group Policy, link the updated GPO to a pilot OU first, then widen the link.

Gotchas

  • Profiles don’t auto-upgrade. When a new version ships, older profiles keep working but their settings become read-only. Update Version creates a side-by-side copy; assignments and scope tags are not carried over.
  • Old and new profiles can collide. If both are assigned to the same device and a value differs, you get a Conflict status. Move assignments, don’t duplicate them.
  • Removing a baseline doesn’t reset settings. Settings no longer managed stay at their last value until something else changes them. Plan rollback as “assign the old values,” not “unassign.”
  • Administrator protection and LAPS. Microsoft lists LAPS-managed devices, devices that require Hyper-V, apps that share files across profiles, Windows 365 Cloud PCs, and AVD session hosts under “when not to enable.” The v2 GPO baseline turns it on, so exclude these devices deliberately.
  • RDP known issue. Microsoft documents that non-admin RDP logons can fail with error 0xC000000D on devices with Administrator protection enabled after KB5124010. The workaround is to turn off Administrator protection on affected devices.
  • Elevated sessions are isolated. SSO credentials, network drives, and app settings don’t carry into the elevated profile. Copy installers to a local drive before elevating.
  • Remote admin behavior changes. By default, domain users in the local Administrators group get non-elevated remote logons when Administrator protection is on. Use the documented UAC remote-logon policies if your support tools need elevated remote sessions.
  • NetBIOS isn’t in the Intune 26H2 baseline. Microsoft left out Configure NetBIOS settings because it only works on Windows Insider builds today. Its absence is expected, not a failed deployment.
  • Overlapping baselines. The Windows, Defender for Endpoint, and Edge baselines can manage the same settings with different defaults. Review them together.

How to verify it worked

  • Intune profile status: Microsoft Intune admin center > Endpoint security > Security baselines > Security Baseline for Windows 10 and later > Profiles > select the 26H2 profile. Check Device and user check-in status (select View report, then Generate report), Device assignment status, and Per setting status for Error or Conflict counts.
  • Per-device conflicts: Devices > All devices > select a device > Device configuration > select the baseline > select a setting to see every source profile that sets it.
  • Version inventory: run the Graph script above and confirm assigned Windows baseline profiles show the 26H2 version. Save the output with your change record.
  • On the device: Settings > Accounts > Access work or school > select the account > Info > Advanced Diagnostic Report > Create report to see which policies applied and from where.
  • Administrator protection elevations: Microsoft logs Event ID 15031 (elevation approved) and 15032 (denied or failed) under the Microsoft-Windows-LUA ETW provider. Capture a trace during pilot testing:
logman start AdminProtectionTrace -p {93c05d69-51a3-485e-877f-1806a8731346} -ets
rem ...reproduce the elevation...
logman stop AdminProtectionTrace -ets

Frequently asked questions

What changed in the Windows 11 26H2 security baseline? Four settings changed from 25H2: Windows Ready Print driver ranking is enabled, the Internet Explorer Turn off encryption support setting now allows only TLS 1.2 and TLS 1.3, and the Oct 8, 2026 v2 package sets two UAC policies that turn on Administrator protection with credential prompts on the secure desktop.

Should the baseline be deployed unchanged? No. Treat it as a tested starting point. Review conflicts, application dependencies, and business exceptions, and exclude devices where Microsoft says not to enable Administrator protection, such as LAPS-managed devices and Hyper-V hosts.

Can Intune manage the 26H2 baseline? Yes. The 26H2 baseline has been in Intune since the week of Oct 5, 2026, but existing profiles don’t update automatically. Use Update Version to create a 26H2 copy and pilot it. As of Oct 21, 2026, the Intune 26H2 baseline reference doesn’t list the Administrator protection settings, so manage those with a Settings catalog policy.

What evidence should an admin keep? Keep the package version (26H2 v2), the Policy Analyzer or Intune settings comparison, pilot group membership, Administrator protection test results, exception approvals, the Graph inventory output, and a rollback record.

Related: our Intune and endpoint consulting and Microsoft 365 security consulting services, plus quick answers on Intune vs Group Policy, managing Windows updates with Intune, and planning a Windows 11 upgrade.

Need a Windows hardening rollout?

Accred Consulting can compare your current Windows, Intune, Defender, and Group Policy controls with Microsoft’s baseline, then build a staged rollout with conflict testing, exception ownership, and evidence your team can reuse.

Plan a Security Baseline Review Take the 2-minute fit check