A Windows baseline change is a workplace change. Its success depends on whether people can still sign in, connect, print and run approved applications while the intended security controls take effect. For October’s architecture column, I would use the new baseline as a reason to review the full service journey.
The October trigger
Microsoft’s 6 October update states that the Windows 11 version 26H2 security baseline is available in Intune. The accompanying Settings Catalog guidance covers new and updated management settings and recommends checking version and edition applicability before deployment. The post also distinguishes newly manageable settings from features that are genuinely new to Windows 26H2. [1]
This article proposes a rollout method. It does not claim that a particular fleet, application or existing Windows build has been validated against the new baseline.
Start with policy ownership
Before assigning anything, build a comparison of the current configuration, the proposed setting and the reason for each difference. Record whether the setting is already controlled through another profile or management system. A baseline should not become another unexplained source of configuration.
Give exceptions an owner and review date. “Required for application X” is incomplete without the affected version, business process, evidence of the failure and compensating controls. Keep the exception narrow enough that a future application upgrade can remove it.
Use business journeys as test cases
| Journey | Evidence to collect | Suggested owner |
|---|---|---|
| New starter device | Provisioning, first sign-in, required apps and usable desktop | Endpoint engineering |
| Remote employee | Normal proxy/VPN path, certificates and access to core services | Network and identity teams |
| Specialist application | Launch, document export, printing and approved integrations | Application owner |
| Service desk recovery | Approved support access and recovery from a failed policy change | Operations |
Include representative hardware and actual working conditions. A clean test laptop on an unrestricted connection provides limited evidence for a managed device behind a secure web gateway. Where application control is enforced, retain it during testing so the result represents the intended production configuration.
Promote a known configuration through rings
My suggested sequence is engineering validation, a small business pilot, then controlled expansion. Keep the candidate configuration stable while evaluating a ring. Changing the operating-system version, baseline and application packages together makes the cause of a failure harder to establish.
Choose promotion criteria before deployment. These could include successful critical workflows, no unresolved high-impact incidents and documented acceptance from the application owner. Review the sample size and business coverage as well as the percentage of successful devices.
Design recovery before approval
Record the previous policy values and assignment scope. For each changed setting, establish the supported reversal method and whether a restart, sign-out or explicit configuration change is needed. Do not assume removing an assignment immediately restores every prior value.
The change record should name who can stop expansion, who communicates with users and who verifies recovery. Test the recovery procedure on the pilot group before relying on it during a broader incident.
Finish with an operational handover
Provide support teams with the expected user experience, known exceptions and a short diagnostic decision tree. Record residual risks explicitly. The architecture decision is complete when the organisation can explain what changed, demonstrate the intended outcome and support it after the project closes.
Continue with the Application Control policy guide and October Intune operational review.
Microsoft references
Sources checked 2 November 2026. Coverage focuses on October announcements through 31 October. Recommendations are proposed implementation practices; validate availability, licensing and requirements in your tenant before rollout.