Blog Post

Azure Governance and Management Blog
3 MIN READ

[Public Preview] Introducing Security Baseline Remediation in Machine Configuration

sydneykarimi's avatar
sydneykarimi
Icon for Microsoft rankMicrosoft
Nov 17, 2026

Security baselines help organizations define and assess their server security posture. But identifying configuration drift is only part of the work—correcting it usually requires custom remediation policies or additional management tools. 

Today, we’re announcing Public Preview support for security baseline remediation in Azure Policy and Machine Configuration. You can now configure supported baseline settings, audit machines against your organization’s standards, and continuously correct drift—all through an integrated policy experience. 

The approach is simple: organization-wide auditing, with targeted remediation. 

What’s New? 

Baseline remediation builds on the existing baseline customization experience. Alongside defining your organization’s desired values, you can now choose which supported settings Machine Configuration should actively remediate. 

This brings assessment and correction together: instead of identifying a baseline gap and building a separate remediation solution, you can use Machine Configuration to maintain your selected settings over time. 

Public Preview includes remediation support for: 

Baseline 

Supported settings 

Azure Security Baselines for Windows and Linux 

70 settings 

CIS baselines for Linux 

40–70 settings, depending on the operating system 

STIG baselines 

40–70 settings, depending on the operating system 

Organization-Wide Auditing, Targeted Remediation 

Organizations need visibility across their environments without making every configuration change everywhere at once. Baseline remediation lets you retain broad auditing while targeting configuration changes to the settings and locations you choose. 

Remediation requires three explicit choices: 

Control 

How you opt in 

Behavior without opt-in 

Policy effect 

Assign the policy with DeployIfNotExists. 

The default AuditIfNotExists effect audits without changing configuration. 

Individual settings 

Set each desired setting’s Mode to Remediate in the security baseline catalog. 

Settings left in Audit mode are assessed without being changed. 

Machine locations 

Populate the RemediationLocations policy assignment parameter. 

An empty list means all machines remain audit-only. Machines outside the selected locations also remain audit-only. 

All three controls must permit remediation before a selected setting can be changed. Policy scope and exemptions are respected, and devices must meet the Machine Configuration prerequisites. 

This enables a gradual rollout: audit your organization’s standards broadly, begin remediation in selected locations, and expand as you validate the results. Stopping remediation does not restore a machine’s previous configuration, and settings already applied remain in place. 

Customize Your Baseline 

Start in the Azure portal under Machine Configuration > Security Baseline, then select your desired baseline. 

Use the security baseline catalog to: 

  • Customize setting values to match your organization’s requirements. 
  • Leave settings in Audit mode when you want compliance visibility without configuration changes. 
  • Change supported settings to Remediate when you want continuous drift correction. 
  • Uncheck settings you do not want included in the baseline. 

You can combine auditing and remediation within the same baseline, keeping control over which settings are enforced. 

 

 

Assign and Continuously Maintain Your Standards 

Assign the Azure Policy at your chosen scope with your baseline configuration. 

To enable remediation, select the DeployIfNotExists effect and populate RemediationLocations with the locations you want to target. Your catalog configuration is deployed automatically to the Machine Configuration agent on devices covered by the assignment. 

For eligible devices in those locations, Machine Configuration continuously corrects drift for settings marked Remediate. Settings marked Audit, and machines outside the selected remediation locations, continue to be audited without configuration changes. 

Compliance evaluation follows the existing Machine Configuration schedules. 

 

 

 

Prerequisites and Availability 

Before getting started: 

  • Assign the Machine Configuration prerequisite policy initiative to enable the required Machine Configuration agent. 
  • Ensure devices meet the minimum supported agent versions: 

OS Type 

Release Date 

Version 

Notes 

Linux 

October 30, 2026 

1.26.121 

Notes 

Windows 

October 30, 2026 

1.29.122.0 

Notes 

 

Baseline remediation is available in Public Preview, with no additional charge for the remediation capability, across all Azure public cloud regions. It will also be available for sovereign clouds, including US Gov Clouds by 11/20/26. 

Get Started 

Bring baseline assessment and correction into a single workflow. Customize your baseline, choose the settings you want to remediate, and target your rollout while maintaining organization-wide compliance visibility. 

Learn more: Remediate Security Baselines 

Updated Nov 17, 2026
Version 1.0
No CommentsBe the first to comment