Skip to content

Commit 4696d92

Browse files
author
Mutemwa Masheke
committed
Address Acrolinx feedback for overview-page.md
Clarity improvements (Score: 50→Improved): - Broke up complex sentences about cloud-native governance experience - Simplified long sentence structure and improved readability - Changed 'running on-premises' to 'that run on-premises' to avoid -ing words - Restructured audit policy section into clear bullet points - Split complex explanations into digestible parts Consistency improvements (Score: 72→100): - Maintained proper em dash formatting (already correct) - Kept 'Azure portal' terminology (already lowercase) - Ensured consistent formatting throughout Terminology improvements (Score: 79→100): - Replaced 'like' with 'such as' for better clarity - Changed 'what's published' to 'what is published' for formal tone - Defined VMs acronym: 'virtual machines (VMs)' on first use - Changed 'More standards' to 'Additional standards' for better flow Tense improvements: - Changed 'is planned for' to 'will be added closer to' for clearer timeline Document structure improvements: - Enhanced readability while maintaining technical accuracy - Improved flow between sections - Better bullet point organization for complex processes
1 parent 296acfa commit 4696d92

2 files changed

Lines changed: 12 additions & 9 deletions

File tree

articles/governance/machine-configuration/how-to/assign-security-baselines/overview-page.md

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -11,16 +11,19 @@ Customizable security baselines built on Azure Policy and Machine Configuration
1111

1212
This capability introduces *audit* baselines for both Windows and Linux, empowering customers to align security posture with internal compliance frameworks and regulatory standards. By passing custom baseline parameter input directly into Azure Policy, you can now represent organization-specific controls at scale.
1313

14-
These baselines deliver a cloud-native governance experience for both Azure machines and non-Azure machines connected through [Azure Arc][01]. This includes machines running on-premises, in other public clouds, or at the edge. Together, Policy and Machine Configuration establish a unified control plane for compliance visibility. This approach enables you to assess, monitor, and enforce consistent security standards across your entire estate, regardless of location or platform. This approach reflects Microsoft's Secure by Design and Secure by Default principles, ensuring robust security and compliance everywhere your workloads run.
14+
These baselines deliver a cloud-native governance experience for both Azure machines and non-Azure machines connected through [Azure Arc][01]. This includes machines that run on-premises, in other public clouds, or at the edge. Together, Policy and Machine Configuration establish a unified control plane for compliance visibility. This approach enables you to assess, monitor, and enforce consistent security standards across your entire estate, regardless of location or platform. This approach reflects Microsoft's Secure by Design and Secure by Default principles. It helps ensure robust security and compliance everywhere your workloads run.
1515

1616
## Key Scenarios
1717

18-
### Baseline Customization
19-
Create tailored baselines using the *Modify Settings* wizard under **Policy \> Machine Configuration**. Administrators can enable, exclude, or adjust rules from industry benchmarks (like CIS Benchmarks or Microsoft baselines) to match internal standards. Each customization builds a downloadable JSON file that captures configuration intent—a reusable artifact compatible for policy-as-code workflows.
18+
### Baseline Customization
19+
Create tailored baselines using the *Modify Settings* wizard under **Policy \> Machine Configuration**. Administrators can enable, exclude, or adjust rules from industry benchmarks (such as CIS Benchmarks or Microsoft baselines) to match internal standards. Each customization builds a downloadable JSON file that captures configuration intent—a reusable artifact compatible for policy-as-code workflows.
2020

2121
### Assign Audit Policies
2222

23-
Use Azure Policy to deploy your customized baseline parameters across Azure and Arc-connected machines. Azure Policy evaluates configuration states against selected benchmarks when an audit policy is assigned. It reports compliance in real time and surfaces findings across Azure Policy, Azure Resource Graph (ARG), and the Guest Assignments view.
23+
Azure Policy deploys your customized baseline parameters across Azure and Arc-connected machines. When you assign an audit policy, Azure Policy:
24+
- Evaluates configuration states against selected benchmarks
25+
- Reports compliance in real time
26+
- Surfaces findings across Azure Policy, Azure Resource Graph (ARG), and the Guest Assignments view
2427

2528
### Integration and Automation
2629
Integrate baselines into CI/CD pipelines or configuration management workflows. Each baseline produces a declarative settings catalog (JSON) that can be version-controlled and deployed using CLI, ARM, or Bicep templates—ensuring reproducible compliance configurations across environments.
@@ -29,18 +32,18 @@ Integrate baselines into CI/CD pipelines or configuration management workflows.
2932

3033
| **Standard** | **Description** |
3134
|----|----|
32-
| **Center for Internet Security (CIS) Linux Benchmarks** | Official CIS Benchmarks for all [Azure endorsed Linux distributions][02] in parity with what's published on the [CIS website][03]. |
35+
| **Center for Internet Security (CIS) Linux Benchmarks** | Official CIS Benchmarks for all [Azure endorsed Linux distributions][02] in parity with what is published on the [CIS website][03]. |
3336
| **Azure Compute Security Baseline for Windows** | Applies customized values for Windows Server 2022 and Windows Server 2025. |
3437
| **Azure Compute Security Baseline for Linux** | Enforces consistent security controls aligned with Azure Compute guidance. |
3538

36-
More standards (for example, STIG), operating systems, and remediation capabilities are planned for future releases.
39+
Additional standards (for example, STIG), operating systems, and remediation capabilities are planned for future releases.
3740

3841
## Availability
3942

4043
All public Azure regions are supported.
4144

4245
> [!NOTE]
43-
> Support for Azure Government and Sovereign Clouds is planned for General Availability.
46+
> Support for Azure Government and Sovereign Clouds will be added closer to General Availability.
4447
4548
## Getting Started
4649

@@ -60,7 +63,7 @@ The end-to-end experience for configuring Customizable Security Baselines follow
6063

6164
### Prerequisites
6265

63-
- Azure Machine Configuration prerequisite policy initiative must be deployed. The capability enables Guest Configuration policies and installs the required extension on VMs.
66+
- Azure Machine Configuration prerequisite policy initiative must be deployed. The capability enables Guest Configuration policies and installs the required extension on virtual machines (VMs).
6467

6568
- An Azure subscription or management group containing supported Windows and Linux VMs.
6669

articles/governance/machine-configuration/how-to/assign-security-baselines/specify-custom-parameters-for-baseline-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ With built-in security baselines, you can customize security controls to meet yo
1414
The new Azure Policy Settings Picker experience streamlines this process. It allows you to select which settings to evaluate and adjust configuration parameters for granular control. The experience supports advanced input formats for Linux and Windows and exports your customized baseline as a reusable JSON artifact. This flexibility ensures that policy enforcement is consistent, precise, and adaptable to complex enterprise needs, regardless of where your workloads run.
1515

1616
> [!NOTE]
17-
> Ensure the *Machine Configuration prerequisites* initiative has been assigned to your subscription.
17+
> Ensure the *Machine Configuration prerequisites* initiative is assigned to your subscription.
1818
1919
## Open the Machine Configuration blade
2020

0 commit comments

Comments
 (0)