Skip to content

Commit b54e917

Browse files
authored
Merge branch 'main' into WI445254-remove-reference-to-investigation-priority-score
2 parents a7c044c + 6ae5d91 commit b54e917

10 files changed

+21
-19
lines changed

defender-endpoint/isolation-exclusions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
ms.topic: how-to
1515
ms.subservice: edr
1616
search.appverid: met150
17-
ms.date: 06/22/2025
17+
ms.date: 07/01/2025
1818
---
1919

2020
# Isolation exclusions (preview)
@@ -57,7 +57,7 @@ There are two steps to using isolation exclusion: defining isolation exclusion r
5757

5858
### Prerequisites
5959

60-
* Isolation exclusion is available on Windows (minimum client version 10.8470) and macOS (minimum client version 101.240902).
60+
* Isolation exclusion is available on Windows 11, Windows 10 version 1703 or later, Windows Server 2025, Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, and macOS.
6161
* Isolation exclusion must be enabled. Enabling isolation exclusion requires Security Admin or Manage Security settings permissions or above. To enable isolation exclusion, sign in to the [Microsoft Defender portal](https://security.microsoft.com) and go to **Settings** > **Endpoints** > **Advanced features** and enable **Isolation Exclusion Rules** feature.
6262

6363
:::image type="content" source="./media/isolation-exclusions/enable-exclusions.png" alt-text="Screenshot showing how to enable isolation exclusions." lightbox="./media/isolation-exclusions/enable-exclusions.png":::

defender-endpoint/mac-preferences.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: how-to
1616
ms.subservice: macos
1717
search.appverid: met150
18-
ms.date: 05/21/2025
18+
ms.date: 07/01/2025
1919
---
2020

2121
# Set preferences for Microsoft Defender for Endpoint on macOS
@@ -995,6 +995,8 @@ The following templates contain entries for all settings described in this docum
995995
<dict>
996996
<key>enforcementLevel</key>
997997
<string>real_time</string>
998+
<key>behaviorMonitoring</key>
999+
<string>enabled</string>
9981000
<key>scanAfterDefinitionUpdate</key>
9991001
<true/>
10001002
<key>scanArchives</key>

defender-endpoint/mde-plugin-wsl.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,16 +15,15 @@ ms.collection:
1515
ms.custom:
1616
- partner-contribution
1717
audience: ITPro
18-
ms.date: 11/11/2024
18+
ms.date: 07/01/2025
1919
search.appverid: MET150
2020
---
2121

2222
# Microsoft Defender for Endpoint plug-in for Windows Subsystem for Linux (WSL)
2323

2424
**Applies to:**
2525

26-
- Microsoft Defender for Endpoint for servers
27-
- Microsoft Defender for Servers Plan 1 or Plan 2
26+
- [Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
2827

2928
## Overview
3029

@@ -134,7 +133,7 @@ If your host machine contains multiple proxy settings, the plug-in selects the p
134133

135134
3. Network & Internet proxy settings.
136135

137-
For example, if your host machine has both `Winhttp proxy` and `Network & Internet proxy`, the plug-in selects `Winhttp proxy` as the proxy configuration.
136+
For example, if your host machine has both `Winhttp proxy` and `Network & Internet proxy`, the plug-in selects `Winhttp proxy` as the proxy configuration.
138137

139138
> [!NOTE]
140139
> The `DefenderProxyServer` registry key is no longer supported. Follow the steps described earlier in this article to configure proxy in plug-in.
@@ -294,7 +293,7 @@ Check the following things:
294293
- If your machine has a proxy setup, run the command `healthCheck --extendedProxy`. This will provide information on which proxy(s) is set on your machine and whether these configurations are invalid for WSL defender.
295294

296295
![Extend HealthCheck Proxy doc](media/mde-plugin-wsl/extend-healthcheck-proxy-doc.png)
297-
296+
298297
- If the steps mentioned above do not fix the problem, include the following configuration settings in the `.wslconfig` located in your `%UserProfile%` and restart WSL. Details about settings can be found in [WSL Settings](/windows/wsl/wsl-config#main-wsl-settings).
299298

300299
**In Windows 11**
15.7 KB
Loading
-1.47 KB
Loading

defender-endpoint/microsoft-defender-endpoint-mac.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Microsoft Defender for Endpoint on macOS overview
33
ms.reviewer: joshbregman
4-
description: An introducttion and overview of Microsoft Defender for Endpoint on macOS.
4+
description: An introduction and overview of Microsoft Defender for Endpoint on macOS.
55
ms.service: defender-endpoint
66
author: emmwalshh
77
ms.author: ewalsh
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: install-set-up-deploy
1616
ms.subservice: macos
1717
search.appverid: met150
18-
ms.date: 06/17/2025
18+
ms.date: 07/01/2025
1919
---
2020

2121
# Microsoft Defender for Endpoint on macOS
@@ -46,7 +46,7 @@ This article describes how to install, configure, update, and use Defender for E
4646
> [!TIP]
4747
> If you have any feedback that you would like to share, submit it by opening Microsoft Defender for Endpoint on Mac on your device and navigating to **Help** \> **Send feedback**.
4848
49-
To get the latest features, including preview capabilities (such as endpoint detection and response for your Mac devices), configure your macOS device running Defender for Endpoint to use the Beta channel (formerly `Insider-Fast`).
49+
To get the latest features, including preview capabilities, configure your macOS device running Defender for Endpoint to use the Beta channel (formerly `Insider-Fast`).
5050

5151
## How to install Microsoft Defender for Endpoint on Mac
5252

defender-endpoint/respond-machine-alerts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.service: defender-endpoint
55
ms.author: diannegali
66
author: diannegali
77
ms.localizationpriority: medium
8-
ms.date: 04/09/2025
8+
ms.date: 07/01/2025
99
manager: deniseb
1010
audience: ITPro
1111
ms.collection:
@@ -216,7 +216,7 @@ Depending on the severity of the attack and the sensitivity of the device, you m
216216
- `iptables`
217217
- `ip6tables`
218218
- Linux kernel with `CONFIG_NETFILTER`, `CONFID_IP_NF_IPTABLES`, and `CONFIG_IP_NF_MATCH_OWNER`
219-
- Selective isolation is available for devices running Windows 10, version 1709 or later, and Windows 11. For more information about selective isolation, see [Isolation exclusions](./isolation-exclusions.md).
219+
- Selective isolation is available for devices running on Windows 11, Windows 10 version 1703 or later, Windows Server 2025, Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, and macOS. For more information about selective isolation, see [Isolation exclusions](./isolation-exclusions.md).
220220
- When isolating a device, only certain processes and destinations are allowed. Therefore, devices that are behind a full VPN tunnel won't be able to reach the Microsoft Defender for Endpoint cloud service after the device is isolated. We recommend using a split-tunneling VPN for Microsoft Defender for Endpoint and Microsoft Defender Antivirus cloud-based protection-related traffic.
221221
- The feature supports VPN connection.
222222
- You must have at least the `Active remediation actions` role assigned. For more information, see [Create and manage roles](user-roles.md).

defender-endpoint/supported-capabilities-by-platform.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
ms.topic: article
1515
ms.subservice: onboard
1616
search.appverid: met150
17-
ms.date: 04/03/2025
17+
ms.date: 07/01/2025
1818
---
1919

2020
# Supported Microsoft Defender for Endpoint capabilities by platform
@@ -50,7 +50,7 @@ The following table gives information about the supported Microsoft Defender for
5050
|[Passive Mode](microsoft-defender-antivirus-compatibility.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|
5151
|Sense detection sensor|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|
5252
|[Endpoint & network device discovery](device-discovery.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg) <br/>(See note below) |![No](media/svg/check-no.svg)|![No](media/svg/check-no.svg)|
53-
|[Vulnerability management](/defender-vulnerability-management/defender-vulnerability-management)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg) <br/>(preview)|
53+
|[Vulnerability management](/defender-vulnerability-management/defender-vulnerability-management)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg) <br/>|
5454
|**Response** | | | ||
5555
|[Automated Investigation & Response (AIR)](automated-investigations.md) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![No](media/svg/check-no.svg) | ![No](media/svg/check-no.svg) |
5656
|[Device response capabilities: collect investigation package ](respond-machine-alerts.md) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) |
@@ -64,8 +64,8 @@ The following table gives information about the supported Microsoft Defender for
6464
> - For Windows Server 2012 R2 and Windows Server 2016, use the modern, unified solution. See [Onboard Windows Servers to the Defender for Endpoint service](onboard-server.md#functionality-in-the-modern-unified-solution-for-windows-server-2016-and-windows-server-2012-r2).
6565
> - On Linux Server, network protection, web protection, and custom network indicators are currently in preview.
6666
> - On Linux, network protection, web protection, and custom network indicators are currently in preview.
67-
> - Endpoint & network device discovery is supported on Windows Server 2019 or later, and on Windows 10 and Windows 11.
68-
> - Microsoft Defender Vulnerability Management is not supported on Rocky and Alma currently.
67+
> - Endpoint & network device discovery is supported on Windows Server 2019 or later, and on Windows 10 and Windows 11.
6968
> - For Windows 7, Windows 8.1, and Windows Server 2008 R2, use [MMA](/defender-endpoint/onboard-downlevel#install-and-configure-microsoft-monitoring-agent-mma) for the EDR sensor and [System Center Endpoint Protection](/defender-endpoint/onboard-downlevel#configure-and-update-system-center-endpoint-protection-clients) (SCEP) for antivirus protection.
7069
70+
7171
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

defender-office-365/defender-for-office-365-whats-new.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.author: chrisda
88
author: chrisda
99
manager: deniseb
1010
ms.localizationpriority: medium
11-
ms.date: 05/19/2025
11+
ms.date: 7/1/2025
1212
audience: ITPro
1313
ms.collection:
1414
- m365-security
@@ -47,6 +47,8 @@ For more information on what's new with other Microsoft Defender security produc
4747

4848
For more information, see [MC1096885](https://admin.microsoft.com/AdminPortal/Home?#/MessageCenter/:/messages/MC1096885).
4949

50+
- AI-powered Submissions Response introduces generative AI explanations for admin email submissions to Microsoft. For more information, see [Submission result definitions](submissions-result-definitions.md).
51+
5052
## May 2025
5153

5254
- In government cloud environments, :::image type="icon" source="media/m365-cc-sc-take-actions-icon.png" border="false"::: **Take action** replaces the **Message actions** drop down list on the **Email** tab (view) of the details area of the **All email**, **Malware**, or **Phish** views in [Threat Explorer (Explorer)](threat-explorer-real-time-detections-about.md):

unified-secops-platform/microsoft-threat-actor-naming.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,6 @@ The following table shows how the family names map to the threat actors that we
4646

4747
|Threat actor category|Type|Family name|
4848
|:---|:---|:---|
49-
|Nation-state|China<br>Iran<br>Lebanon<br>North Korea<br>Russia<br>South Korea<br>Türkiye<br>Vietnam|Typhoon<br>Sandstorm<br>Rain<br>Sleet<br>Blizzard<br>Hail<br>Dust<br>Cyclone|
5049
|Nation-state|China<br>Germany<br>India<br>Iran<br>North Korea<br>Lebanon<br>Pakistan<br>Palestinian Authority<br>Russia<br>Singapore<br>South Korea<br>Spain<br>Syria<br>Türkiye<br>Ukraine<br>United States<br>Vietnam|Typhoon<br>Gale<br>Monsoon<br>Sandstorm<br>Sleet<br>Rain<br>Whirlwind<br>Lightning<br>Blizzard<br>Squall<br>Hail<br>Derecho<br>Haze<br>Dust<br>Frost<br>Tornado<br>Cyclone|
5150
|Financially motivated|Financially motivated|Tempest|
5251
|Private sector offensive actors|PSOAs|Tsunami|

0 commit comments

Comments
 (0)