Skip to content

Commit 0dca780

Browse files
authored
Merge pull request #6513 from MicrosoftDocs/main
1/11/2021 AM Publish
2 parents e18d1f8 + 470d6c6 commit 0dca780

2 files changed

Lines changed: 6 additions & 6 deletions

File tree

memdocs/configmgr/compliance/deploy-use/create-configuration-baselines.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Create configuration baselines
33
titleSuffix: Configuration Manager
44
description: Create configuration baselines in Configuration Manager that you can deploy to a collection.
5-
ms.date: 11/29/2019
5+
ms.date: 01/10/2022
66
ms.prod: configuration-manager
77
ms.technology: configmgr-compliance
88
ms.topic: conceptual
@@ -76,17 +76,17 @@ To create a configuration baseline by using the **Create Configuration Baseline*
7676
7777
## <a name="bkmk_CAbaselines"></a> Include custom configuration baselines as part of compliance policy assessment
7878
<!--3608345-->
79-
*(Introduced in version 1910)*
8079

81-
Starting in version 1910, you can add evaluation of custom configuration baselines as a compliance policy assessment rule. When you create or edit a configuration baseline, you have an option to **Evaluate this baseline as part of compliance policy assessment**. When adding or editing a compliance policy rule, you have a condition called **Include configured baselines in compliance policy assessment**. For co-managed devices, and when you configure Intune to take Configuration Manager compliance assessment results as part of the overall compliance status, this information is sent to Azure AD. You can then use it for conditional access to your Microsoft 365 Apps resources. For more information, see [Conditional access with co-management](../../comanage/quickstart-conditional-access.md).
80+
You can add evaluation of custom configuration baselines as a compliance policy assessment rule. When you create or edit a configuration baseline, you have an option to **Evaluate this baseline as part of compliance policy assessment**. When adding or editing a compliance policy rule, you have a condition called **Include configured baselines in compliance policy assessment**. For co-managed devices, and when you configure Intune to take Configuration Manager compliance assessment results as part of the overall compliance status, this information is sent to Azure AD. You can then use it for conditional access to your Microsoft 365 Apps resources. For more information, see [Conditional access with co-management](../../comanage/quickstart-conditional-access.md).
8281

8382
To include custom configuration baselines as part of compliance policy assessment, do the following:
8483

8584
- Create and deploy a compliance policy to a user collection with a rule to [**Include configured baselines in compliance policy assessment**](#bkmk_CA).
8685
- Select [**Evaluate this baseline as part of compliance policy assessment**](#bkmk_eval-baseline) in a configuration baseline deployed to a device collection.
8786

8887
> [!IMPORTANT]
89-
> When targeting devices that are co-managed, ensure you meet the [co-management prerequisites](../../comanage/overview.md#prerequisites).
88+
> - When targeting devices that are co-managed, ensure you meet the [co-management prerequisites](../../comanage/overview.md#prerequisites). Co-managed clients ignore service windows for remediation when their compliance policies workload is managed by Intune. <!--12439085, 12412748-->
89+
> - For devices managed by Configuration Manager, the client honors the service window for compliance policy remediation. To ignore the service window and remediate immediately, select **Check compliance** in the **Software Center**. <!--12439085, 12412748-->
9090
9191
### Example evaluation scenario
9292

memdocs/configmgr/protect/deploy-use/endpoint-protection-group-policies.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ You can manage Endpoint Protection in such devices using Group Policy settings,
3636
- [Local device](#load-endpoint-protection-group-policy-settings-into-your-local-device)
3737

3838
> [!NOTE]
39-
> For information on how to use Group Policy settings to manage Microsoft Defender Antivirus in Windows 10, Windows Server 2019, Windows Server 2016, or later see [Use Group Policy settings to configure and manage Microsoft Defender Antivirus](/windows/security/threat-protection/microsoft-defender-antivirus/use-group-policy-microsoft-defender-antivirus).
39+
> For information on how to use Group Policy settings to manage Microsoft Defender Antivirus in Windows 10, Windows Server 2019, Windows Server 2016, or later as well as [on Windows Server 2012 R2 after installing Microsoft Defender for Endpoint using the modern, unified solution](/microsoft-365/security/defender-endpoint/configure-server-endpoints#windows-server-2012-r2-and-windows-server-2016) see [Use Group Policy settings to configure and manage Microsoft Defender Antivirus](/windows/security/threat-protection/microsoft-defender-antivirus/use-group-policy-microsoft-defender-antivirus).
4040
4141
## Copy Endpoint Protection policy definitions
4242

@@ -100,4 +100,4 @@ Instead of using Central Store for loading Endpoint Protection policy definition
100100

101101
## Next steps
102102
- For an overview on Endpoint Protection, see [Endpoint Protection](endpoint-protection.md).
103-
- For information on configuring Endpoint Protection on a standalone client manually, see [Configure Endpoint Protection on a standalone client](endpoint-protection-configure-standalone-client.md).
103+
- For information on configuring Endpoint Protection on a standalone client manually, see [Configure Endpoint Protection on a standalone client](endpoint-protection-configure-standalone-client.md).

0 commit comments

Comments
 (0)