Skip to content

Commit 4de9402

Browse files
Merge branch 'main' into docs-editor/advanced-hunting-cloudappevent-1720336825
2 parents eb66920 + 2d85cef commit 4de9402

File tree

70 files changed

+850
-497
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

70 files changed

+850
-497
lines changed

.openpublishing.redirection.defender.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -194,6 +194,11 @@
194194
"source_path": "defender-endpoint/collect-diagnostic-data-update-compliance.md",
195195
"redirect_url": "/defender-endpoint/collect-diagnostic-data",
196196
"redirect_document_id": false
197+
},
198+
{
199+
"source_path": "defender-endpoint/attack-simulations.md",
200+
"redirect_url": "/defender-endpoint/defender-endpoint-demonstrations",
201+
"redirect_document_id": true
197202
}
198203
]
199204
}

defender-business/mdb-offboard-devices.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ audience: Admin
99
ms.topic: overview
1010
ms.service: defender-business
1111
ms.localizationpriority: medium
12-
ms.date: 06/19/2024
12+
ms.date: 07/08/2024
1313
ms.reviewer: nehabha
1414
f1.keywords: NOCSH
1515
ms.collection:
@@ -21,21 +21,26 @@ ms.collection:
2121

2222
# Offboard a device from Microsoft Defender for Business
2323

24-
As devices are replaced or retired, or your business needs change, you can offboard devices from Defender for Business. Offboarding a device causes the device to stop sending data to Defender for Business. However, data received prior to offboarding is retained for up to six (6) months.
24+
As devices are replaced or retired, or your business needs change, you can offboard devices from Defender for Business. Offboarding a device causes the device to stop sending data to Defender for Business, and its status changes to `Inactive` within seven days. You don't have to offboard devices that are already listed as `Inactive`.
25+
26+
Data from a device, such as alerts, vulnerabilities, and detected threats, remains visible in the Microsoft Defender portal until the [configured retention period](/defender-endpoint/data-storage-privacy#how-long-will-microsoft-store-my-data-what-is-microsofts-data-retention-policy) expires (usually 180 days).
27+
28+
Devices that weren't active within the last 30 days aren't factored into your organization's [exposure score](mdb-view-tvm-dashboard.md).
2529

2630
> [!IMPORTANT]
2731
> The procedures in this article describe how to remove a device from monitoring by Defender for Business. If you're using Microsoft Intune to manage devices, and you prefer to remove the device from Intune, see [Remove devices by using wipe, retire, or manually unenrolling the device](/mem/intune/remote-actions/devices-wipe).
2832
2933
## What to do
3034

31-
1. Select a tab:
35+
1. Select one of the following tabs:
3236

3337
- **Windows 10 or 11**
3438
- **Mac**
3539
- **Servers** (Windows Server or Linux Server)
3640
- **Mobile** (for iOS/iPadOS or Android devices)
3741

3842
2. Follow the guidance on the selected tab.
43+
3944
3. Proceed to your next steps.
4045

4146
## [**Windows 10 or 11**](#tab/Windows1011)

defender-endpoint/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -321,8 +321,6 @@
321321
items:
322322
- name: Integration with Microsoft Defender for Cloud
323323
href: azure-server-integration.md
324-
- name: Run simulated attacks on devices
325-
href: attack-simulations.md
326324
- name: Create an onboarding or offboarding notification rule
327325
href: onboarding-notification.md
328326
- name: Manage Microsoft Defender for Endpoint configuration settings on devices with Microsoft Intune

defender-endpoint/android-whatsnew.md

Lines changed: 22 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
ms.topic: reference
1515
ms.subservice: android
1616
search.appverid: met150
17-
ms.date: 03/04/2024
17+
ms.date: 07/15/2024
1818
---
1919

2020
# What's new in Microsoft Defender for Endpoint on Android
@@ -27,6 +27,12 @@ ms.date: 03/04/2024
2727

2828
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)
2929

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).
3036
3137
## Device Tagging
3238

@@ -36,7 +42,7 @@ This configuration is available for both the enrolled (MDM) devices and unenroll
3642

3743
## Microsoft Defender for Endpoint on Company-owned personally enabled devices
3844

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:
4046

4147
- Phishing and web protection.
4248
- Malware scanning.
@@ -51,28 +57,26 @@ Microsoft Defender for Endpoint on Android enables Privacy Controls for both the
5157

5258
## Optional Permissions and Disable Web Protection
5359

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).
5561

5662
## Microsoft Defender on Android enterprise BYOD personal profile
5763

5864
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).
5965

60-
## Network protection
6166

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
6568

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.
6970

7071
To update, users can use the following steps:
7172

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).
7680

7781
## Microsoft Defender for Endpoint is now Microsoft Defender in the Play store
7882

@@ -84,19 +88,19 @@ On January 25, 2022, we announced the general availability of Vulnerability mana
8488

8589
## Upcoming permission changes for Microsoft Defender for Endpoint running Android 11 or later (Nov 2021)
8690

87-
Release Build: 1.0.3501.0301
91+
Release Build: `1.0.3501.0301`
8892
Release month: Nov 2021
8993
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.
9094

9195
**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.
9296

9397
> [!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.
9599
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.
97101

98102
> [!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.
100104
101105
**What you need to do to prepare:**
102106

defender-endpoint/attack-simulations.md

Lines changed: 0 additions & 71 deletions
This file was deleted.

defender-endpoint/configure-advanced-scan-types-microsoft-defender-antivirus.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.custom: nextgen
99
ms.reviewer: pahuijbr
1010
manager: deniseb
1111
ms.subservice: ngp
12-
ms.date: 05/30/2024
12+
ms.date: 07/10/2024
1313
ms.collection:
1414
- m365-security
1515
- tier2
@@ -64,7 +64,7 @@ For details on configuring Microsoft Configuration Manager (current branch), see
6464
|Scan [reparse points](/windows/win32/fileio/reparse-points) <br/> **Scan** \> **Turn on reparse point scanning**|Disabled|Not available <br/>See [Reparse points](/windows/win32/fileio/reparse-points)|
6565
|Scan mapped network drives<br/>**Scan** \> **Run full scan on mapped network drives**|Disabled|`-DisableScanningMappedNetworkDrivesForFullScan`|
6666
|Scan archive files (such as .zip or .rar files). <br/>**Scan** \> **Scan archive files**|Enabled|`-DisableArchiveScanning` <br/><br/>The [extensions exclusion list](configure-extension-file-exclusions-microsoft-defender-antivirus.md) will take precedence over this setting.|
67-
|Scan files on the network <br/>**Scan** \> **Scan network files**|Enabled|`-DisableScanningNetworkFiles`|
67+
|Scan files on the network <br/>**Scan** \> **Scan network files**|Disabled|`-DisableScanningNetworkFiles`|
6868
|Scan packed executables<br/>**Scan** \> **Scan packed executables**|Enabled|Not available <br/><br/>Scan packed executables were removed from the following templates:<br/>- Administrative Templates (.admx) for Windows 11 2022 Update (22H2)<br/>- Administrative Templates (.admx) for Windows 11 October 2021 Update (21H2)|
6969
|Scan removable drives during full scans only<br/>**Scan** \> **Scan removable drives**|Disabled|`-DisableRemovableDriveScanning`|
7070
|Specify the level of subfolders within an archive folder to scan <p>**Scan** \> **Specify the maximum depth to scan archive files**|0|Not available|

0 commit comments

Comments
 (0)