Skip to content

Commit 6a3840f

Browse files
Merge pull request #576 from MicrosoftDocs/main
publish main to live 10:30 AM 5/29/24
2 parents b1013a6 + 45ee56e commit 6a3840f

12 files changed

+97
-30
lines changed

defender-endpoint/attack-surface-reduction-rules-reference.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,9 +42,8 @@ This article provides information about Microsoft Defender for Endpoint attack s
4242
- [Per-rule-descriptions](#per-rule-descriptions)
4343

4444
[!Include[Prerelease information](../includes/prerelease.md)]
45+
[!Include [defender-endpoint-setup-guide.md](../includes/mde-automated-setup-guide.md)]
4546

46-
> [!TIP]
47-
> 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).
4847
## Attack surface reduction rules by type
4948

5049
Attack surface reduction rules are categorized as one of two types:

defender-endpoint/detect-block-potentially-unwanted-apps-microsoft-defender-antivirus.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,8 +64,8 @@ Potentially unwanted applications can increase the risk of your network being in
6464

6565
[Learn more about Windows Enterprise subscriptions](https://www.microsoft.com/microsoft-365/windows/windows-11-enterprise).
6666

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).
67+
[!Include [defender-endpoint-setup-guide.md](../includes/mde-automated-setup-guide.md)]
68+
6969
## Microsoft Edge
7070

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

defender-endpoint/device-control-overview.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,8 @@ This list is intended to provide some examples. It's not an exhaustive list; the
3939

4040
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.
4141

42+
[!Include [defender-endpoint-setup-guide.md](../includes/mde-automated-setup-guide.md)]
43+
4244
## Microsoft device control capabilities
4345

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

defender-endpoint/linux-whatsnew.md

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,27 @@ This article is updated frequently to let you know what's new in the latest rele
3131

3232
- [What's new in Defender for Endpoint on macOS](mac-whatsnew.md)
3333
- [What's new in Defender for Endpoint on iOS](ios-whatsnew.md)
34+
<details>
35+
<summary> May-2024 (Build: 101.24042.0002 | Release version: 30.24042.0002.0)</summary>
36+
37+
## May-2024 Build: 101.24042.0002 | Release version: 30.124042.0002.0
38+
39+
&ensp;Released: **May 29, 2024**<br/>
40+
&ensp;Published: **May 29, 2024**<br/>
41+
&ensp;Build: **101.24042.0002**<br/>
42+
&ensp;Release version: **30.24042.0002.0**<br/>
43+
&ensp;Engine version: **1.1.24030.4**<br/>
44+
&ensp;Signature version: **1.407.521.0**<br/>
3445

46+
**What's new**
47+
48+
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.
51+
- Stability and performance improvements.
52+
- Other bug fixes.
53+
54+
</details>
3555
<details>
3656
<summary> May-2024 (Build: 101.24032.0007 | Release version: 30.124032.0007.0)</summary>
3757

@@ -67,11 +87,12 @@ There are multiple fixes and new changes in this release:
6787

6888
**Known Issues**
6989

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

7292
```bash
7393
sudo mdatp edr tag set --name GROUP --value MDE-Management
7494
```
95+
**The issue has been fixed in Build: 101.24042.0002**
7596

7697
</details>
7798

defender-endpoint/mac-support-perf-overview.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,15 @@
11
---
22
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.
44
author: YongRhee-MSFT
55
ms.author: yongrhee
66
ms.service: defender-endpoint
77
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
1011
manager: dansimp
12+
ms.custom: partner-contribution
1113
---
1214

1315
# 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
2325

2426
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.
2527

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+
2631
> [!CAUTION]
2732
> 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.
2833
2934
> [!WARNING]
3035
> Before starting, make sure that other security products are not currently running on the device. Multiple security products might conflict and impact system performance.
3136
3237
> [!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
3640

3741
|Daemon name|Component|Troubleshooting guide|
3842
| -------- | -------- |-------- |
3943
|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).|
4145
|wdavdaemon_enterprise| Endpoint Detection and Response (EDR)|Open a [Microsoft support case](contact-support.md).|
4246

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

defender-endpoint/microsoft-defender-endpoint-antivirus-performance-mode.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
- m365-security
1515
- tier2
1616
search.appverid: met150
17-
ms.date: 05/02/2024
17+
ms.date: 05/29/2024
1818
---
1919

2020
# Protect Dev Drive using performance mode
@@ -32,8 +32,8 @@ ms.date: 05/02/2024
3232

3333
- Windows 11
3434

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).
35+
[!Include [defender-endpoint-setup-guide.md](../includes/mde-automated-setup-guide.md)]
36+
3737
## What is performance mode
3838

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

defender-endpoint/review-detected-threats.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.collection:
1212
- tier2
1313
- mde-edr
1414
ms.topic: conceptual
15-
ms.date: 02/02/2024
15+
ms.date: 05/29/2024
1616
ms.subservice: edr
1717
search.appverid: met150
1818
---
@@ -101,8 +101,8 @@ DeviceInfo
101101
AlertEvidence
102102
| where Timestamp > ago(15d)
103103
| where ServiceSource == "Microsoft Defender for Endpoint"
104-
| where DetectionSource == "Antivirus"
105-
DeviceName
104+
| where DetectionSource == "Antivirus")
105+
on DeviceName
106106
| distinct DeviceName, DeviceId, Title, AlertId, Timestamp
107107
```
108108

defender-endpoint/troubleshoot-onboarding.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,7 @@ This page provides detailed steps to troubleshoot onboarding issues that might o
3636

3737
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).
3838

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).
39+
[!Include [defender-endpoint-setup-guide.md](../includes/mde-automated-setup-guide.md)]
4140

4241
## Troubleshoot issues with onboarding tools
4342

defender-for-cloud/breadcrumb/defender-for-cloud/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,4 @@
44
items:
55
- name: 'Microsoft Defender for Cloud'
66
tocHref: /defender-for-cloud/
7-
topicHref: /defender-for-cloud/index
7+
topicHref: /defender-for-cloud/index

defender-for-cloud/docfx.json

Lines changed: 25 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,9 @@
2525
{
2626
"files": [
2727
"**/*.png",
28-
"**/*.jpg"
28+
"**/*.jpg",
29+
"**/*.gif",
30+
"**/*.svg"
2931
],
3032
"exclude": [
3133
"**/obj/**",
@@ -40,11 +42,30 @@
4042
"overwrite": [],
4143
"externalReference": [],
4244
"globalMetadata": {
43-
"breadcrumb_path": "~/breadcrumb/defender-for-cloud/toc.yml",
45+
"breadcrumb_path": "/breadcrumb/defender-for-cloud/toc.json",
4446
"feedback_system": "Standard",
45-
"permissioned-type": "public"
47+
"permissioned-type": "public",
48+
"feedback_product_url": "https://techcommunity.microsoft.com/t5/security-compliance-and-identity/ct-p/MicrosoftSecurityandCompliance",
49+
"uhfHeaderId": "MSDocsHeader-MicrosoftDefender",
50+
"titleSuffix": "Microsoft Defender for Cloud",
51+
"searchScope": [
52+
"Microsoft Defender for Cloud"
53+
],
54+
"contributors_to_exclude": [
55+
"dstrome",
56+
"shdyas",
57+
"rjagiewich",
58+
"American-Dipper",
59+
"claydetels19",
60+
"jborsecnik",
61+
"v-stchambers",
62+
"Stacyrch140",
63+
"garycentric",
64+
"alekyaj"
65+
]
4666
},
4767
"fileMetadata": {},
48-
"template": []
68+
"template": [],
69+
"dest": "defender-for-cloud"
4970
}
5071
}

0 commit comments

Comments
 (0)