You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/android-whatsnew.md
+22-18Lines changed: 22 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.collection:
14
14
ms.topic: reference
15
15
ms.subservice: android
16
16
search.appverid: met150
17
-
ms.date: 03/04/2024
17
+
ms.date: 07/15/2024
18
18
---
19
19
20
20
# What's new in Microsoft Defender for Endpoint on Android
@@ -27,6 +27,12 @@ ms.date: 03/04/2024
27
27
28
28
Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.](https://signup.microsoft.com/create-account/signup?products=7f379fee-c4f9-4278-b0a1-e4c8c2fcdf7e&ru=https://aka.ms/MDEp2OpenTrial?ocid=docs-wdatp-exposedapis-abovefoldlink)
29
29
30
+
## Network protection
31
+
32
+
Network protection on Microsoft Defender for Endpoint is now available. Network protection provides protection against rogue Wi-Fi related threats, rogue hardware like pineapple devices, and rogue certificates. It notifies the user if a related threat is detected. Users also see a guided experience to connect to secure networks and change networks when they're connected to an unsecure connection.
33
+
34
+
> [!IMPORTANT]
35
+
> Network protection feature will soon be enabled by default for all users. The update will be rolled out in a phased manner. As a result, users will be able to see a network protection card in the Defender for Endpoint app, along with App Protection and Web Protection. Users are also required to provide location permission to complete the set up. Admins can change the default value for network protection if they decide not to use it via the Intune App Configuration policies. There are also several admin controls to offer flexibility, including privacy controls to configure the data that's sent by Defender for Endpoint from Android devices. For more information, see [network protection](android-configure.md).
30
36
31
37
## Device Tagging
32
38
@@ -36,7 +42,7 @@ This configuration is available for both the enrolled (MDM) devices and unenroll
36
42
37
43
## Microsoft Defender for Endpoint on Company-owned personally enabled devices
38
44
39
-
MDE is now generally available on AE COPE devices. Enterprises can onboard devices on COPE mode and push MDE to user's devices through the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). With this support, Android Enterprise COPE devices get the full capabilities of our offering on Android, including:
45
+
Defender for Endpoint is now generally available on AE COPE devices. Enterprises can onboard devices on COPE mode and push Defender for Endpoint to user's devices through the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431). With this support, Android Enterprise COPE devices get the full capabilities of our offering on Android, including:
40
46
41
47
- Phishing and web protection.
42
48
- Malware scanning.
@@ -51,28 +57,26 @@ Microsoft Defender for Endpoint on Android enables Privacy Controls for both the
51
57
52
58
## Optional Permissions and Disable Web Protection
53
59
54
-
Microsoft Defender for Endpoint on Android enables **Optional Permissions** in the onboarding flow. Currently the permissions required by MDE are mandatory in the onboarding flow. With this feature, admin can deploy MDE on devices without enforcing the mandatory **VPN** and **Accessibility** permissions during onboarding. End Users can onboard the app without the mandatory permissions and can later review these permissions. This feature is currently present only for unenrolled devices (MAM). For more information, see [optional permissions](android-configure-mam.md#optional-permissions).
60
+
Microsoft Defender for Endpoint on Android enables **Optional Permissions** in the onboarding flow. Currently the permissions required by Defender for Endpoint are mandatory in the onboarding flow. With this feature, admin can deploy Defender for Endpoint on devices without enforcing the mandatory **VPN** and **Accessibility** permissions during onboarding. End Users can onboard the app without the mandatory permissions and can later review these permissions. This feature is currently present only for unenrolled devices (MAM). For more information, see [optional permissions](android-configure-mam.md#optional-permissions).
55
61
56
62
## Microsoft Defender on Android enterprise BYOD personal profile
57
63
58
64
Microsoft Defender for Endpoint is now supported on Android Enterprise personal profile (BYOD only) with all the key features including malware scanning, protection from phishing links, network protection and vulnerability management. This support is coupled with [privacy controls](android-configure.md#privacy-controls) to ensure user privacy on personal profile. For more information, read the [announcement](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/announcing-the-public-preview-of-defender-for-endpoint-personal/ba-p/3370979) and the [deployment guide](android-intune.md#set-up-microsoft-defender-in-personal-profile-on-android-enterprise-in-byod-mode).
59
65
60
-
## Network protection
61
66
62
-
Network Protection on Microsoft Defender for Endpoint is now available. Network protection provides protection against rogue Wi-Fi related threats, rogue hardware like pineapple devices and notifies the user if a related threat is detected. Users also see a guided experience to connect to secure networks and change networks when they're connected to an unsecure connection.
63
-
> [!IMPORTANT]
64
-
> Network protection feature will soon be enabled by default for all users. The update will be rolled out in a phased manner. As a result, users will be able to see Network Protection Card in the Defender for Endpoint iOS app along with App Protection and Web Protection. Users are also required to provide Location permission to complete the set up. Admins can change the default value for the Network Protection feature if they decide not to use it via the Intune App Configuration policies. There are also several admin controls to offer flexibility, including privacy controls to configure the data that's sent by Defender for Endpoint from Android devices. For more information, see [network protection](android-configure.md).
67
+
## Microsoft Defender on Android app updates
65
68
66
-
67
-
> [!NOTE]
68
-
> Microsoft Defender is no longer supported for versions 1.0.3011.0302 or earlier. Users are requested to upgrade to latest versions to keep their devices secure.
69
+
Microsoft Defender is no longer supported for versions 1.0.3011.0302 or earlier. Users are requested to upgrade to latest versions to keep their devices secure.
69
70
70
71
To update, users can use the following steps:
71
72
72
-
> 1. On your work profile, go to Managed Play Store.
73
-
> 2. Tap on the profile icon on the top right corner and select "Manage apps and device".
74
-
> 3. Locate MDE under updates available and select update.
75
-
> If you encounter any issues, [submit in-app feedback](android-support-signin.md#send-in-app-feedback).
73
+
1. On your work profile, go to Managed Play Store.
74
+
75
+
2. Tap on the profile icon on the top right corner and select **Manage apps and device**.
76
+
77
+
3. Locate Defender for Endpoint under updates available and select **Update**.
78
+
79
+
If you encounter any issues, [submit in-app feedback](android-support-signin.md#send-in-app-feedback).
76
80
77
81
## Microsoft Defender for Endpoint is now Microsoft Defender in the Play store
78
82
@@ -84,19 +88,19 @@ On January 25, 2022, we announced the general availability of Vulnerability mana
84
88
85
89
## Upcoming permission changes for Microsoft Defender for Endpoint running Android 11 or later (Nov 2021)
86
90
87
-
Release Build: 1.0.3501.0301
91
+
Release Build: `1.0.3501.0301`
88
92
Release month: Nov 2021
89
93
Microsoft Defender for Endpoint has released this update required by [Google](https://developer.android.com/distribute/play-policies#APILevel30) to upgrade to Android API 30. This change prompts users seeking access to [new storage permission](https://developer.android.com/training/data-storage/manage-all-files#all-files-access-google-play), for devices running Android 11 or later. Users need to accept this new storage permission once they update Defender app with the release build 1.0.3501.0301 or later. This update ensures that Defender for Endpoint's app security feature to function without any disruption. For more information, review the following sections.
90
94
91
95
**How will this affect your organization:** These changes take effect if you're using Microsoft Defender for Endpoint on devices running Android 11 or later and updated Defender for Endpoint to release build 1.0.3501.0301 or later.
92
96
93
97
> [!NOTE]
94
-
> The new storage permissions cannot be configured by admin to 'Auto Approve' through Microsoft Intune. User will need to take action to provide access to this permission.
98
+
> The new storage permissions cannot be configured by admin to auto approve through Microsoft Intune. User will need to take action to provide access to this permission.
95
99
96
-
-**User experience:** Users receive a notification indicating a missing permission for app security. If the user denies this permission, the 'App security' functionality is turned off on the device. If user doesn't accept or deny permission, they'll continue to receive the prompt when unlocking their device or opening the app, until it has been approved.
100
+
-**User experience:** Users receive a notification indicating a missing permission for app security. If the user denies this permission, app security functionality is turned off on the device. If user doesn't accept or deny permission, they continue to receive the prompt when unlocking their device or opening the app, until it's approved.
97
101
98
102
> [!NOTE]
99
-
> If your organization is previewing 'Tamper protection' feature and if the new storage permissions are not granted by the user within 7 days of updating to the latest version, the user might lose access to corporate resources.
103
+
> If your organization is previewing the tamper protection feature and if the new storage permissions are not granted by the user within 7 days of updating to the latest version, the user might lose access to corporate resources.
- Support phase: **Security and Critical Updates**
108
108
@@ -116,6 +116,8 @@ All our updates contain
116
116
- Fixed potentially packet loss due to [network protection](network-protection.md) shutdown that could lead to deadlock.
117
117
- Implemented performance improvements for scenarios where WDAC is enabled with Intelligent Security Graph.
118
118
- Fixed an issue where an Outlook exclusion for the ASR rule [Block Office applications from injecting code into other processes](/defender-endpoint/attack-surface-reduction-rules-reference#block-office-applications-from-injecting-code-into-other-processes) was not honored.
119
+
- Fixed a race condition during the startup of [endpoint data loss prevention](/purview/endpoint-dlp-getting-started), such that in certain environments, some system files could be corrupted.
- Improved health monitoring and telemetry for [attack surface rules](overview-attack-surface-reduction.md) exclusions.
149
151
- Updated inaccurate information in [Configure exclusions for files opened by processes](configure-process-opened-file-exclusions-microsoft-defender-antivirus.md) regarding wildcard usage with contextual exclusions.
- Support phase: **Security and Critical Updates**
158
-
159
-
#### What's new
160
-
161
-
- Added manageability settings to opt out for One Collector telemetry channel and Experimentation and Configuration Service (ECS).
162
-
- Microsoft Defender Core Service will be disabled when 3rd party Antivirus is installed (except when Defender for Endpoint is running in Passive mode).
163
-
- The known issue in [4.18.24020.7](msda-updates-previous-versions-technical-upgrade-support.md#february-2024-engine-11240209--platform-418240207) where enforcement of device level access policies wasn't working as expected no longer occurs.
164
-
- Fixed high CPU issue caused by redetection done during Sense originating scans.
165
-
- Fixed an issue with Security Intelligence Update disk cleanup.
166
-
- Fixed an issue where the Signature date information on the Security Health report wasn't accurate.
167
-
- Introduced performance improvements when processing paths for exclusions.
168
-
- Added improvements to allow recovering from erroneously added [Indicators of compromise (IoC)](manage-indicators.md).
169
-
- Improved resilience in processing [attack surface reduction](attack-surface-reduction.md) exclusions for Anti Malware Scan Interface (AMSI) scans.
170
-
- Fixed a high memory issue related to the [Behavior Monitoring](behavior-monitor.md) queue that occurred when MAPS is disabled.
171
-
- A possible deadlock when receiving a [Tamper protection](prevent-changes-to-security-settings-with-tamper-protection.md) configuration change from the [Microsoft Defender portal](https://security.microsoft.com) no longer occurs.
172
-
173
153
### Previous version updates: Technical upgrade support only
174
154
175
155
After a new package version is released, support for the previous two versions is reduced to technical support only. For more information about previous versions, see [Microsoft Defender Antivirus updates: Previous versions for technical upgrade support](msda-updates-previous-versions-technical-upgrade-support.md).
Copy file name to clipboardExpand all lines: defender-endpoint/msda-updates-previous-versions-technical-upgrade-support.md
+23-1Lines changed: 23 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: siosulli
6
6
author: siosulli
7
7
ms.localizationpriority: medium
8
8
ms.reviewer: pahuijbr
9
-
ms.date: 06/07/2024
9
+
ms.date: 07/15/2024
10
10
manager: deniseb
11
11
audience: ITPro
12
12
ms.collection:
@@ -27,6 +27,28 @@ search.appverid: met150
27
27
28
28
Microsoft regularly releases [security intelligence updates and product updates for Microsoft Defender Antivirus](microsoft-defender-antivirus-updates.md). It's important to keep Microsoft Defender Antivirus up to date. When a new package version is released, support for the previous two versions is reduced to technical support only. Versions that are older than the previous two versions are listed in this article and are provided for technical upgrade support only.
- Support phase: **Technical upgrade support (only)**
37
+
38
+
### What's new
39
+
40
+
- Added manageability settings to opt out for One Collector telemetry channel and Experimentation and Configuration Service (ECS).
41
+
- Microsoft Defender Core Service will be disabled when 3rd party Antivirus is installed (except when Defender for Endpoint is running in Passive mode).
42
+
- The known issue in [4.18.24020.7](msda-updates-previous-versions-technical-upgrade-support.md#february-2024-engine-11240209--platform-418240207) where enforcement of device level access policies wasn't working as expected no longer occurs.
43
+
- Fixed high CPU issue caused by redetection done during Sense originating scans.
44
+
- Fixed an issue with Security Intelligence Update disk cleanup.
45
+
- Fixed an issue where the Signature date information on the Security Health report wasn't accurate.
46
+
- Introduced performance improvements when processing paths for exclusions.
47
+
- Added improvements to allow recovering from erroneously added [Indicators of compromise (IoC)](manage-indicators.md).
48
+
- Improved resilience in processing [attack surface reduction](attack-surface-reduction.md) exclusions for Anti Malware Scan Interface (AMSI) scans.
49
+
- Fixed a high memory issue related to the [Behavior Monitoring](behavior-monitor.md) queue that occurred when MAPS is disabled.
50
+
- A possible deadlock when receiving a [Tamper protection](prevent-changes-to-security-settings-with-tamper-protection.md) configuration change from the [Microsoft Defender portal](https://security.microsoft.com) no longer occurs.
0 commit comments