Skip to content

Commit 69dbdb9

Browse files
authored
Merge pull request #8140 from BalaDelli/patch-3
Update create-deploy-application-guard-policy.md
2 parents b728a93 + 0f2e4f5 commit 69dbdb9

2 files changed

Lines changed: 19 additions & 38 deletions

File tree

memdocs/configmgr/core/plan-design/changes/whats-new-in-version-1906.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -516,12 +516,12 @@ For more information on the dashboard, prerequisites, and using this data, see [
516516
## <a name="bkmk_protect"></a> Protection
517517

518518
### Windows Defender Application Guard file trust criteria
519-
519+
_Applies to version 2203 or earlier_
520520
<!--3555858-->
521521

522522
There's a new policy setting that enables users to trust files that normally open in Windows Defender Application Guard (WDAG). Upon successful completion, the files will open on the host device instead of in WDAG.
523523

524-
For more information, see [Create and deploy Windows Defender Application Guard policy](../../../protect/deploy-use/create-deploy-application-guard-policy.md#bkmk_FM).
524+
For more information, see [Create and deploy Windows Defender Application Guard policy](../../../protect/deploy-use/create-deploy-application-guard-policy.md#bkmk_ABS).
525525

526526

527527
## <a name="bkmk_admin"></a> Configuration Manager console

memdocs/configmgr/protect/deploy-use/create-deploy-application-guard-policy.md

Lines changed: 17 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -2,20 +2,20 @@
22
title: Manage Application Guard policies
33
titleSuffix: Configuration Manager
44
description: Learn how to create and deploy Microsoft Defender Application Guard policies
5-
ms.date: 10/05/2021
5+
ms.date: 08/01/2022
66
ms.prod: configuration-manager
77
ms.technology: configmgr-protect
88
ms.topic: conceptual
9-
author: mestew
10-
ms.author: mstewart
11-
manager: dougeby
9+
author: baladelli
10+
ms.author: baladell
11+
manager: apoorvseth
1212
ms.localizationpriority: medium
1313
---
1414

1515
# Create and deploy Microsoft Defender Application Guard policy
1616

1717
*Applies to: Configuration Manager (current branch)*
18-
<!-- 1351960 -->
18+
<!-- 1351960, 14059872 -->
1919
You can create and deploy [Microsoft Defender Application Guard (Application Guard)](/windows/security/threat-protection/microsoft-defender-application-guard/md-app-guard-overview) policies by using the Configuration Manager endpoint protection. These policies help protect your users by opening untrusted web sites in a secure isolated container that isn't accessible by other parts of the operating system.
2020

2121
## Prerequisites
@@ -25,12 +25,12 @@ To create and deploy a Microsoft Defender Application Guard policy, you must use
2525
## Create a policy, and to browse the available settings
2626

2727
1. In the Configuration Manager console, choose **Assets and Compliance**.
28-
2. In the **Assets and Compliance** workspace, choose **Overview** > **Endpoint Protection** > **Windows Defender Application Guard**.
29-
3. In the **Home** tab, in the **Create** group, click **Create Windows Defender Application Guard Policy**.
28+
2. In the **Assets and Compliance** workspace, choose **Overview** > **Endpoint Protection** > **Microsoft Defender Application Guard**.
29+
3. In the **Home** tab, in the **Create** group, click **Create Microsoft Defender Application Guard Policy**.
3030
4. Using the [article](/windows/security/threat-protection/microsoft-defender-application-guard/configure-md-app-guard) as a reference, you can browse and configure the available settings. Configuration Manager allows you to set certain policy settings:
31-
- [Host interaction settings](#bkmk_HIS)
3231
- [Application behavior](#bkmk_ABS)
33-
- [File management](#bkmk_FM)
32+
- [Host interaction settings](#bkmk_HIS)
33+
3434
5. On the **Network Definition** page, specify the corporate identity, and define your corporate network boundary.
3535

3636
> [!NOTE]
@@ -43,7 +43,7 @@ To create and deploy a Microsoft Defender Application Guard policy, you must use
4343
4444
6. When you're finished, complete the wizard, and deploy the policy to one or more Windows 10 1709 or later devices.
4545

46-
### <a name="bkmk_HIS"></a> Host interaction settings
46+
### <a name="bkmk_ABS"></a> Application behavior
4747

4848
Configures interactions between host devices and the Application Guard container. Before Configuration Manager version 1802, both application behavior and host interaction were under the **Settings** tab.
4949

@@ -60,46 +60,27 @@ Configures interactions between host devices and the Application Guard container
6060
- Virtual graphics processor access
6161
- **Files:** (starting with Configuration Manager version 1802)
6262
- Save downloaded files to host
63+
- **Policies:** (starting with Configuration Manager version 2207)
64+
- Enable or disable cameras and microphones
65+
- Certificate matching the thumbprints to the isolated container
6366

64-
### <a name="bkmk_ABS"></a> Application behavior settings
67+
### <a name="bkmk_HIS"></a> Host interaction settings
6568

6669
Configures application behavior inside the Application Guard session. Before Configuration Manager version 1802, both application behavior and host interaction were under the **Settings** tab.
6770

68-
- **Content:**
69-
- Enterprise sites can load non-enterprise content, such as third-party plug-ins.
70-
> [!NOTE]
71-
> This policy setting is no longer supported in the new Microsoft Edge browser. Webpages that contain mixed content, both enterprise and non-enterprise, may load incorrectly or fail completely if this feature is enabled. See the setting [Windows Defender Application Guard](/windows/client-management/mdm/windowsdefenderapplicationguard-csp) documentation for more information.
72-
7371
- **Other:**
7472
- Retain user-generated browser data
7573
- Audit security events in the isolated application guard session
7674

77-
### <a name="bkmk_FM"></a> File management
78-
<!--3555858-->
79-
Starting in Configuration Manager version 1906, There's a policy setting that enables users to trust files that normally open in Application Guard. Upon successful completion, the files will open on the host device instead of in Application Guard. For more information about the Application Guard policies, see [Configure Microsoft Defender Application Guard policy settings](/windows/security/threat-protection/microsoft-defender-application-guard/configure-md-app-guard).
80-
81-
- **Allow users to trust files that open in Windows Defender Application Guard** - Enable the user to mark files as trusted. When a file is trusted, it opens on the host rather than in Application Guard. Applies to Windows 10 version 1809 or later clients.
82-
- **Prohibited:** Don't allow users to mark files as trusted (default).
83-
- **File checked by antivirus:** Allow users to mark files as trusted after an antivirus check.
84-
- **All files:** Allow users to mark any file as trusted.
85-
86-
When you enable file management, you may see errors logged in the client's DCMReporting.log. The errors below typically don't effect functionality: <!--4619457-->
87-
88-
- On compatible devices:
89-
- FileTrustCriteria_condition not found
90-
- On non-compatible devices:
91-
- FileTrustCriteria_condition not found
92-
- FileTrustCriteria_condition could not be located in the map
93-
- FileTrustCriteria_condition not found in digest
94-
95-
To edit Application Guard settings, expand **Endpoint Protection** in the **Assets and Compliance** workspace, then click on the **Windows Defender Application Guard** node. Right-click on the policy you want to edit, then select **Properties**.
75+
To edit Application Guard settings, expand **Endpoint Protection** in the **Assets and Compliance** workspace, then click on the **Microsoft Defender Application Guard** node. Right-click on the policy you want to edit, then select **Properties**.
9676

9777
## Known issues
78+
_Applies to version 2203 or earlier_
9879

9980
Devices running Windows 10, version 2004 will show failures in compliance reporting for Microsoft Defender Application Guard File Trust Criteria. This issue occurs because some subclasses were removed from the WMI class `MDM_WindowsDefenderApplicationGuard_Settings01` in Windows 10, version 2004. All other Microsoft Defender Application Guard settings will still apply, only File Trust Criteria will fail. Currently, there are no workarounds to bypass the error. <!--7099444,5946790-->
10081

10182
## Next steps
10283

10384
For more information about Microsoft Defender Application Guard, see
10485
- [Microsoft Defender Application Guard overview](/windows/security/threat-protection/microsoft-defender-application-guard/md-app-guard-overview).
105-
- [Microsoft Defender Application Guard FAQ](/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard).
86+
- [Microsoft Defender Application Guard FAQ](/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard).

0 commit comments

Comments
 (0)