Skip to content

Commit 27a77c9

Browse files
authored
Merge branch 'public' into patch-3
2 parents 237fdbb + 546e116 commit 27a77c9

26 files changed

+412
-246
lines changed

defender-endpoint/android-configure-mam.md

Lines changed: 27 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
- mde-android
1515
ms.topic: conceptual
1616
ms.subservice: android
17-
ms.date: 08/08/2024
17+
ms.date: 08/26/2024
1818
---
1919

2020
# Configure Microsoft Defender for Endpoint on Android risk signals using App Protection Policies (MAM)
@@ -44,27 +44,27 @@ End users also need to take steps to install Microsoft Defender for Endpoint on
4444

4545
- **Validate that the Microsoft Defender for Endpoint-Intune connector is enabled**.
4646

47-
a. Go to security.microsoft.com.
47+
1. Go to security.microsoft.com.
4848

49-
b. Select **Settings > Endpoints > Advanced Features > Microsoft Intune Connection** is turned on.
49+
1. Select **Settings > Endpoints > Advanced Features > Microsoft Intune Connection** is turned on.
5050

51-
c. If the connection isn't turned on, select the toggle to turn it on and then select **Save Preferences**.
51+
1. If the connection isn't turned on, select the toggle to turn it on and then select **Save Preferences**.
5252

5353
:::image type="content" source="media/enable-intune-connection.png" alt-text="The Advanced features section in the Microsoft Defender portal." lightbox="media/enable-intune-connection.png":::
5454

55-
d. Go to the **Microsoft Intune admin center** and Validate whether Microsoft Defender for Endpoint-Intune connector is enabled.
55+
1. Go to the **Microsoft Intune admin center** and Validate whether Microsoft Defender for Endpoint-Intune connector is enabled.
5656

5757
:::image type="content" source="media/validate-intune-connector.png" alt-text="The intune-connector status pane in the Microsoft Defender portal." lightbox="media/validate-intune-connector.png":::
5858

5959
- **Enable Microsoft Defender for Endpoint on Android Connector for App Protection Policy (APP)**.
6060

6161
Configure the connector on Microsoft Intune for App protection policies:
6262

63-
a. Go to **Tenant Administration > Connectors and Tokens > Microsoft Defender for Endpoint**.
63+
1. Go to **Tenant Administration > Connectors and Tokens > Microsoft Defender for Endpoint**.
6464

65-
b. Turn on the toggle for the app protection policy for Android (as seen in the following screenshot).
65+
1. Turn on the toggle for the app protection policy for Android (as seen in the following screenshot).
6666

67-
c. Select **Save**.
67+
1. Select **Save**.
6868

6969
:::image type="content" source="media/app-settings.png" alt-text="The application settings pane in the Microsoft Defender portal." lightbox="media/app-settings.png":::
7070

@@ -82,13 +82,13 @@ End users also need to take steps to install Microsoft Defender for Endpoint on
8282

8383
2. Add apps.
8484

85-
a. Choose how you want to apply this policy to apps on different devices. Then add at least one app.
85+
1. Choose how you want to apply this policy to apps on different devices. Then add at least one app.
8686

8787
Use this option to specify whether this policy applies to unmanaged devices. In Android, you can specify the policy applies to Android Enterprise, Device Admin, or Unmanaged devices. You can also choose to target your policy to apps on devices of any management state.
8888

8989
Because mobile app management doesn't require device management, you can protect company data on both managed and unmanaged devices. The management is centered on the user identity, which removes the requirement for device management. Companies can use app protection policies with or without MDM at the same time. For example, consider an employee that uses both a phone issued by the company, and their own personal tablet. The company phone is enrolled in MDM and protected by app protection policies while the personal device is protected by app protection policies only.
9090

91-
b. Select Apps.
91+
1. Select Apps.
9292

9393
A managed app is an app that has app protection policies applied to it, and can be managed by Intune. Any app that has been integrated with the [Intune SDK](/mem/intune/developer/app-sdk) or wrapped by the [Intune App Wrapping Tool](/mem/intune/developer/apps-prepare-mobile-application-management) can be managed using Intune app protection Policies. See the official list of [Microsoft Intune protected apps](/mem/intune/apps/apps-supported-intune-apps) that have been built using these tools and are available for public use.
9494

@@ -106,7 +106,7 @@ End users also need to take steps to install Microsoft Defender for Endpoint on
106106

107107
Select **Included groups**. Then add the relevant groups.
108108

109-
:::image type="content" source="media/assignment.png" alt-text="The Included groups pane in the Microsoft Defender portal." lightbox="media/assignment.png":::
109+
:::image type="content" source="media/assignment.png" alt-text="The Included groups pane in the Microsoft Defender portal." lightbox="media/assignment.png":::
110110

111111
> [!NOTE]
112112
> If a config policy is to be targeted at unenrolled devices (MAM), the recommendation is to deploy the general app configuration settings in Managed Apps instead of using Managed Devices.
@@ -130,7 +130,7 @@ End users also need to take steps to install Microsoft Defender for Endpoint on
130130

131131
4. Install the Microsoft Defender: Antivirus (Mobile) app and go back to the managed app onboarding screen.
132132

133-
:::image type="content" source="media/mam-flow.png" alt-text="Shows the procedure of downloading Microsoft Defender: Antivirus (Mobile) app." lightbox="media/mam-flow.png":::
133+
:::image type="content" source="media/mam-flow.png" alt-text="Shows the procedure of downloading Microsoft Defender: Antivirus (Mobile) app." lightbox="media/mam-flow.png":::
134134

135135
5. Click **Continue > Launch**. The Microsoft Defender for Endpoint app onboarding/activation flow is initiated. Follow the steps to complete onboarding. You'll automatically be redirected back to Managed app onboarding screen, which now indicates that the device is healthy.
136136

@@ -149,14 +149,14 @@ Web protection helps to secure devices against web threats and protect users fro
149149
3. Under **Select Public Apps**, choose **Microsoft Defender for Endpoint** as the target app.
150150

151151
4. In the **Settings** page, under the **General Configuration Settings**, add the following keys and set their value as required.
152-
- **antiphishing**
153-
- **vpn**
152+
- **antiphishing**
153+
- **vpn**
154154

155155
To disable web protection, enter 0 for the antiphishing and VPN values.
156156

157157
To disable only the use of VPN by web protection, enter these values:
158-
- 0 for vpn
159-
- 1 for antiphishing
158+
- 0 for vpn
159+
- 1 for antiphishing
160160

161161
Add **DefenderMAMConfigs** key and set the value as 1.
162162

@@ -170,22 +170,24 @@ Web protection helps to secure devices against web threats and protect users fro
170170

171171
2. Provide a name and description to uniquely identify the policy. Target the policy to **'Selected apps'** and search for **'Microsoft Defender Endpoint for Android'**. Click the entry and then click **Select** and then **Next**.
172172

173-
3. Add the key and value from the following table. Ensure that the **"DefenderMAMConfigs"** key is present in every policy that you create using Managed Apps route. For Managed Devices route, this key shouldn't exist. When you're done, click **Next**.
173+
1. Add the key and value from the following table. Ensure that the **"DefenderMAMConfigs"** key is present in every policy that you create using Managed Apps route. For Managed Devices route, this key shouldn't exist. When you're done, click **Next**.
174174

175-
| Key | Value Type | Default (true-enable, false-disable) | Description |
175+
| Key | Value Type | Default (1-enable, 0-disable) | Description |
176176
| --- | --- | --- | --- |
177-
| `DefenderNetworkProtectionEnable` | Integer | 0 | 1 - Enable, 0 - Disable; This setting is used by IT admins to enable or disable the network protection capabilities in the defender app.|
177+
| `DefenderNetworkProtectionEnable` | Integer | 1 | 1 - Enable, 0 - Disable; This setting is used by IT admins to enable or disable the network protection capabilities in the defender app.|
178178
|`DefenderAllowlistedCACertificates`| String | None | None-Disable; This setting is used by IT admins to establish trust for root CA and self-signed certificates.|
179179
|`DefenderCertificateDetection`|Integer| 0 |2-Enable, 1 - Audit mode, 0 - Disable; When this feature is enabled with value as 2, end user notifications are sent to the user when Defender detects a bad certificate. Alerts are also sent to SOC Admins. In audit mode (1), notification alerts are sent to SOC admins, but no end user notifications are displayed to the user when Defender detects a bad certificate. Admins can disable this detection with 0 as the value and enable full feature functionality by setting 2 as the value. |
180-
| `DefenderOpenNetworkDetection` | Integer | 0 |2-Enable, 1 - Audit mode, 0 - Disable; This setting is used by IT Admins to enable or disable open network detection. By default, the open network detection is disabled with value as 0 and defender does not send end user notifications or alerts to SOC admins in security portal. If switched to audit mode with value 1, notification alert is sent to SOC admin, but no end user notification is displayed to the user when defender detects an open network. If it's enabled with value 2, then end user notification is displayed and also alerts to SOC admins is sent.|
180+
| `DefenderOpenNetworkDetection` | Integer | 2 |2-Enable, 1 - Audit mode, 0 - Disable; This setting is used by IT Admins to enable or disable open network detection. If switched to audit mode with value 1, notification alert is sent to SOC admin, but no end user notification is displayed to the user when defender detects an open network. If it's enabled with value 2, then end user notification is displayed and also alerts to SOC admins is sent.|
181181
| `DefenderEndUserTrustFlowEnable` | Integer | 0 | 1 - Enable, 0 - Disable; This setting is used by IT admins to enable or disable the end user in-app experience to trust and untrust the unsecure and suspicious networks. |
182182
| `DefenderNetworkProtectionAutoRemediation` | Integer | 1 | 1 - Enable, 0 - Disable; This setting is used by IT admins to enable or disable the remediation alerts that are sent when a user performs remediation activities like switching to safer Wi-Fi access points or deleting suspicious certificates detected by Defender. |
183183
| `DefenderNetworkProtectionPrivacy` | Integer | 1 | 1 - Enable, 0 - Disable; This setting is used by IT admins to enable or disable privacy in network protection. If privacy is disabled with value 0, then user consent is shown to share the malicious wifi or certs data. If its in enabled state with value 1, then no user consent is shown and no app data is collected.|
184-
184+
185185
4. Include or exclude the groups you want the policy to apply to. Proceed to review and submit the policy.
186186

187187
> [!NOTE]
188-
> Users need to enable location permission (which is an optional permission); this enables Defender for Endpoint to scan their networks and alert them when there are WiFi-related threats. If the location permission is denied by the user, Defender for Endpoint will only be able to provide limited protection against network threats and will only protect the users from rogue certificates.
188+
> - The other config keys of Network Protection will only work if the parent key 'DefenderNetworkProtectionEnable' is enabled.
189+
> - Users need to enable location permission (which is an optional permission) and need to grant “Allow All the Time” permission to ensure protection against Wi-Fi threat, even when the app is not actively in use. If the location permission is denied by the user, Defender for Endpoint will only be able to provide limited protection against network threats and will only protect the users from rogue certificates.
190+
189191

190192
## Configure privacy controls
191193

@@ -252,12 +254,12 @@ Use the following steps to configure the Disable sign out:
252254
2. Provide the policy a **name**.
253255
3. Under **Select Public Apps**, choose **Microsoft Defender for Endpoint** as the target app.
254256
4. In the **Settings** page, under the **General Configuration Settings**, add **DisableSignOut** as the key and set the value as 1.
257+
255258
- By default, Disable Sign Out = 0.
256259
- Admin needs to make Disable Sign Out = 1 to disable the sign-out button in the app. Users will not see the sign out button once the policy is pushed to the device.
260+
257261
5. Select **Next** and assign this profile to targeted devices and users.
258262

259-
> [!IMPORTANT]
260-
> This feature is in Public Preview. The following information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
261263

262264
## Device Tagging
263265

@@ -269,6 +271,7 @@ Use the following steps to configure the Device tags:
269271
2. Provide the policy a **name**.
270272
3. Under **Select Public Apps**, choose **Microsoft Defender for Endpoint** as the target app.
271273
4. In Settings page, select Use configuration designer and add **DefenderDeviceTag** as the key and value type as **String**.
274+
272275
- Admin can assign a new tag by adding the key **DefenderDeviceTag** and setting a value for device tag.
273276
- Admin can edit an existing tag by modifying the value of the key **DefenderDeviceTag**.
274277
- Admin can delete an existing tag by removing the key **DefenderDeviceTag**.

0 commit comments

Comments
 (0)