Skip to content

Commit 2f1e5c9

Browse files
authored
Merge pull request #3728 from MicrosoftDocs/main
[AutoPublish] main to live - 05/12 04:29 PDT | 05/12 16:59 IST
2 parents 244fca0 + 628ab07 commit 2f1e5c9

File tree

3 files changed

+16
-10
lines changed

3 files changed

+16
-10
lines changed

ATPDocs/whats-new.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,12 @@ For more information, see also:
2222

2323
For updates about versions and features released six months ago or earlier, see the [What's new archive for Microsoft Defender for Identity](whats-new-archive.md).
2424

25+
## May 2025
26+
27+
### New Health Issue
28+
29+
New [health issue](health-alerts.md#network-configuration-mismatch-for-sensors-running-on-vmware) for cases where sensors running on VMware have network configuration mismatch.
30+
2531
## April 2025
2632

2733
### Privileged Identity Tag Now Visible in Defender for Identity Inventory
@@ -47,7 +53,6 @@ For more information, see: [Integrations Defender for Identity and PAM services.
4753

4854
### New Service Account Discovery page
4955

50-
5156
Microsoft Defender for Identity now includes a Service Account Discovery capability, offering you centralized visibility into service accounts across your Active Directory environment.
5257

5358
This update provides:
@@ -60,11 +65,6 @@ This update provides:
6065

6166
For more information, see: [Investigate and protect Service Accounts | Microsoft Defender for Identity](service-account-discovery.md).
6267

63-
64-
### New Health Issue
65-
66-
New [health issue](health-alerts.md#network-configuration-mismatch-for-sensors-running-on-vmware) for cases where sensors running on VMware have network configuration mismatch.
67-
6868
### Enhanced Identity Inventory
6969

7070
The Identities page under *Assets* has been updated to provide better visibility and management of identities across your environment.

CloudAppSecurityDocs/anomaly-detection-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,14 +64,14 @@ Use this detection to control file uploads and downloads in real time with sessi
6464

6565
By enabling file sandboxing, files that according to their metadata and based on proprietary heuristics to be potentially risky, will also be sandbox scanned in a safe environment. The Sandbox scan may detect files that were not detected based on threat intelligence sources.
6666

67-
Defender for Cloud Apps supports malware detection for the following apps:
67+
Defender for Cloud Apps supports "File Sandboxing" malware detection for the following apps:
6868

6969
* Box
7070
* Dropbox
7171
* Google Workspace
7272

7373
> [!NOTE]
74-
>* Proactively sandboxing will be done in third party applications (*Box*, *Dropbox* etc.). In *OneDrive* and *SharePoint* files are being scanned and sandboxed as part of the service itself.
74+
>* Proactively sandboxing will be done in third party applications (*Box*, *Dropbox* etc.). **In *OneDrive* and *SharePoint* files are being scanned and sandboxed as part of the service itself**.
7575
> * In *Box*, *Dropbox*, and *Google Workspace*, Defender for Cloud Apps doesn't automatically block the file, but blocking may be performed according to the app's capabilities and the app's configuration set by the customer.
7676
> * If you're unsure about whether a detected file is truly malware or a false positive, go to the Microsoft Security Intelligence page at [https://www.microsoft.com/wdsi/filesubmission](https://www.microsoft.com/wdsi/filesubmission) and submit the file for further analysis.
7777

defender-xdr/automatic-attack-disruption-exclusions.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.topic: conceptual
1818
search.appverid:
1919
- MOE150
2020
- MET150
21-
ms.date: 02/16/2025
21+
ms.date: 05/12/2025
2222
appliesto:
2323
- Microsoft Defender XDR
2424
---
@@ -116,8 +116,14 @@ To remove an exclusion:
116116

117117
- Device group exclusions can be configured in the **Device groups** tab. Select the device group you want to configure from the list and choose the appropriate exclusion from the flyout pane. Select **Save** to save the exclusion.
118118

119+
## Opt out of automatic attack disruption
120+
121+
If you must opt out of attack disruption, you can do so by opening a support case in the Microsoft Defender portal with the subject *Attack disruption opt-out*. In your request, please specify that you wish to opt out of attack disruption and include a brief explanation about your decision. This feedback helps us improve the feature and better understand customer needs. By opting out, you'll still receive alerts related to attack disruption but no automated actions are taken.
122+
123+
Opting out of attack disruption can greatly increase security risk. Consider [excluding specific entities](automatic-attack-disruption-exclusions.md#review-or-change-automated-response-exclusions-for-assets) instead.
124+
119125
## See also
120126

121127
- [View details and results of automated attack disruption actions](autoad-results.md)
122128

123-
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]
129+
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]

0 commit comments

Comments
 (0)