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
> As a companion to this article, we recommend using the [Microsoft Defender for Endpoint automated setup guide](https://go.microsoft.com/fwlink/?linkid=2268088), which helps you utilize essential tools and automated features such as attack surface reduction and next-generation protection. When signed in to the Microsoft 365 admin center, this guide will customize your experience based on your environment. To review best practices without signing in and activating automated setup features, go to the [Microsoft 365 setup guide](https://go.microsoft.com/fwlink/?linkid=2268087).
48
47
## Attack surface reduction rules by type
49
48
50
49
Attack surface reduction rules are categorized as one of two types:
Copy file name to clipboardExpand all lines: defender-endpoint/detect-block-potentially-unwanted-apps-microsoft-defender-antivirus.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,8 +64,8 @@ Potentially unwanted applications can increase the risk of your network being in
64
64
65
65
[Learn more about Windows Enterprise subscriptions](https://www.microsoft.com/microsoft-365/windows/windows-11-enterprise).
66
66
67
-
> [!TIP]
68
-
> As a companion to this article, we recommend using the [Microsoft Defender for Endpoint automated setup guide](https://go.microsoft.com/fwlink/?linkid=2268088), which helps you utilize essential tools and automated features such as attack surface reduction and next-generation protection. When signed in to the Microsoft 365 admin center, this guide will customize your experience based on your environment. To review best practices without signing in and activating automated setup features, go to the [Microsoft 365 setup guide](https://go.microsoft.com/fwlink/?linkid=2268087).
The [new Microsoft Edge](https://support.microsoft.com/microsoft-edge/get-to-know-microsoft-edge-3f4bb0ff-58de-2188-55c0-f560b7e20bea), which is Chromium-based, blocks potentially unwanted application downloads and associated resource URLs. This feature is provided via [Microsoft Defender SmartScreen](/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview).
Copy file name to clipboardExpand all lines: defender-endpoint/device-control-overview.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,8 @@ This list is intended to provide some examples. It's not an exhaustive list; the
39
39
40
40
Device control helps protect your organization from potential data loss, malware, or other cyberthreats by allowing or preventing certain devices to be connected to users' computers. With device control, your security team can determine whether and what peripheral devices users can install and use on their computers.
Device control capabilities from Microsoft can be organized into three main categories: device control in Windows, device control in Defender for Endpoint, and Endpoint Data Loss Prevention (Endpoint DLP).
There are multiple fixes and new changes in this release:
49
+
50
+
- In version 24032.0007, there was a known issue where the enrollment of devices to MDE Security Management failed when using the "Device Tagging" mechanism via the mdatp_managed.json file. This issue has been resolved in the current release.
@@ -67,11 +87,12 @@ There are multiple fixes and new changes in this release:
67
87
68
88
**Known Issues**
69
89
70
-
- There's a known issue with enrolling devices to MDE Security Management using "Device Tagging" mechanism in 24032.007 using mdatp_managed.json. To mitigate this issue, use the following mdatp CLI command to tag devices:
90
+
- There's a known issue where enrolling devices to MDE Security Management via "Device Tagging" mechanism using mdatp_managed.json is failing in 24032.0007. To mitigate this issue, use the following mdatp CLI command to tag devices:
71
91
72
92
```bash
73
93
sudo mdatp edr tag set --name GROUP --value MDE-Management
74
94
```
95
+
**The issue has been fixed in Build: 101.24042.0002**
Copy file name to clipboardExpand all lines: defender-endpoint/mac-support-perf-overview.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,15 @@
1
1
---
2
2
title: Overview for how to troubleshoot performance issues for Microsoft Defender for Endpoint on macOS
3
-
description: Troubleshoot performance issues overview for Microsoft Defender for Endpoint on macOS
3
+
description: Troubleshoot performance issues overview for Microsoft Defender for Endpoint on macOS.
4
4
author: YongRhee-MSFT
5
5
ms.author: yongrhee
6
6
ms.service: defender-endpoint
7
7
ms.topic: overview
8
-
ms.date: 03/01/2024
9
-
ms.subservice: ngp
8
+
ms.localizationpriority: medium
9
+
ms.date: 05/29/2024
10
+
ms.subservice: macos
10
11
manager: dansimp
12
+
ms.custom: partner-contribution
11
13
---
12
14
13
15
# Overview for how to troubleshoot performance issues for Microsoft Defender for Endpoint on macOS
@@ -23,21 +25,23 @@ This article provides general guidelines to identify performance issues related
23
25
24
26
Depending on the applications that you're running and your device characteristics, you might experience suboptimal performance when running Microsoft Defender for Endpoint on macOS. In particular, applications or system processes that access many resources over a short timespan can lead to performance issues in Microsoft Defender for Endpoint on macOS.
25
27
28
+
> [!TIP]
29
+
> As a general best practice, it is recommended to [update the Microsoft Defender for Endpoint agent to latest available version](/defender-endpoint/mac-whatsnew) and confirming that the issue still persists before investigating further.
30
+
26
31
> [!CAUTION]
27
32
> Running other third-party endpoint protection products alongside Microsoft Defender for Endpoint on MacOS is likely to lead to performance problems and unpredictable side effects. If non-Microsoft endpoint protection is an absolute requirement in your environment, you can configure Microsoft Defender Antivirus to run in **[Passive mode](mac-preferences.md)**. After you configure Passive mode, you can use Defender for Endpoint on Mac EDR functionality.
28
33
29
34
> [!WARNING]
30
35
> Before starting, make sure that other security products are not currently running on the device. Multiple security products might conflict and impact system performance.
31
36
32
37
> [!TIP]
33
-
> If you're running other third-party security products, make sure that the Microsoft Defender for Endpoint on macOS processes and paths are excluded from that 3rd party security product and that security product is excluded from Microsoft Defender for Endpoint on macOS.
34
-
35
-
When troubleshooting performance issues for Microsoft Defender for Endpoint on macOS, you should review the **Activity Monitor** to see which of the three (3) processes is leading the high cpu utilization
38
+
> If you're running other third-party security products, make sure that the Microsoft Defender for Endpoint on macOS processes and paths are excluded from that 3rd party security product and that security product is excluded from Microsoft Defender for Endpoint on macOS. And vice-versa.
39
+
When troubleshooting performance issues for Microsoft Defender for Endpoint on macOS, you should review the **Activity Monitor** or run **top** to see which of the three (3) processes is leading the high cpu utilization
36
40
37
41
|Daemon name|Component|Troubleshooting guide|
38
42
| -------- | -------- |-------- |
39
43
|wdavdaemon| Core (privileged)|Open a [Microsoft support case](contact-support.md).|
40
-
|wdavdaemon_unpriviliged| Antimalware (AV, EPP)|Review [Troubleshoot performance issues for Microsoft Defender for Endpoint on macOS](mac-support-perf.md).|
44
+
|wdavdaemon_unprivileged| Antimalware (AV, EPP)|Review [Troubleshoot performance issues for Microsoft Defender for Endpoint on macOS](mac-support-perf.md).|
41
45
|wdavdaemon_enterprise| Endpoint Detection and Response (EDR)|Open a [Microsoft support case](contact-support.md).|
42
46
43
47
Additionally, gather [Defender for Endpoint Client Analyzer](run-analyzer-macos-linux.md) files while the issue occurs. This will be used by the support team to investigate the issue.
Copy file name to clipboardExpand all lines: defender-endpoint/microsoft-defender-endpoint-antivirus-performance-mode.md
+3-3Lines changed: 3 additions & 3 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
- m365-security
15
15
- tier2
16
16
search.appverid: met150
17
-
ms.date: 05/02/2024
17
+
ms.date: 05/29/2024
18
18
---
19
19
20
20
# Protect Dev Drive using performance mode
@@ -32,8 +32,8 @@ ms.date: 05/02/2024
32
32
33
33
- Windows 11
34
34
35
-
> [!TIP]
36
-
> As a companion to this article, we recommend using the [Microsoft Defender for Endpoint automated setup guide](https://go.microsoft.com/fwlink/?linkid=2268088), which helps you utilize essential tools and automated features such as attack surface reduction and next-generation protection. When signed in to the Microsoft 365 admin center, this guide will customize your experience based on your environment. To review best practices without signing in and activating automated setup features, go to the [Microsoft 365 setup guide](https://go.microsoft.com/fwlink/?linkid=2268087).
Performance mode is now available on Windows 11 as a new Microsoft Defender Antivirus capability. Performance mode reduces the performance impact of Microsoft Defender Antivirus scans for files stored on designated _Dev Drive_. The goal of performance mode is to improve functional performance for developers who use Windows 11 devices.
Copy file name to clipboardExpand all lines: defender-endpoint/troubleshoot-onboarding.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,8 +36,7 @@ This page provides detailed steps to troubleshoot onboarding issues that might o
36
36
37
37
Before you start troubleshooting issues with onboarding tools, it's important to check if the minimum requirements are met for onboarding devices to the services. [Learn about the licensing, hardware, and software requirements to onboard devices to the service](minimum-requirements.md).
38
38
39
-
> [!TIP]
40
-
> As a companion to this article, we recommend using the [Microsoft Defender for Endpoint automated setup guide](https://go.microsoft.com/fwlink/?linkid=2268088) when signed in to the Microsoft 365 admin center. This guide will customize your experience based on your environment. To review best practices without signing in and activating automated setup features, go to the [Microsoft 365 setup guide](https://go.microsoft.com/fwlink/?linkid=2268087).
0 commit comments