Skip to content

Commit b952380

Browse files
authored
Merge branch 'main' into poliveria-ti-actors-10092025
2 parents abd2ec8 + 1d1ca17 commit b952380

17 files changed

+419
-18
lines changed

defender-endpoint/linux-preferences.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: Configure security settings in Microsoft Defender for Endpoint on Linux
33
ms.reviewer: gopkr, ardeshmukh
44
description: Describes how to configure Microsoft Defender for Endpoint on Linux in enterprises.
@@ -581,10 +581,8 @@ Specify the maximum number of entries to keep in the scan history. Entries inclu
581581
582582
### Exclusion setting preferences
583583

584-
**Exclusion setting preferences are currently in preview**.
585-
586584
> [!NOTE]
587-
> Global exclusions are currently in public preview, and are available in Defender for Endpoint beginning with version `101.23092.0012` or later in the Insiders Slow and Production rings.
585+
> Global exclusions are available in Defender for Endpoint beginning with version `101.24092.0001` or above.
588586
589587
The `exclusionSettings` section of the configuration profile is used to configure various exclusions for Microsoft Defender for Endpoint for Linux.
590588

defender-for-cloud-apps/governance-discovery.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,24 @@
11
---
22
title: Govern discovered apps
33
description: This article describes the procedure for governing your discovered apps by blocking their usage in your organization.
4-
ms.date: 01/29/2023
4+
ms.date: 09/30/2025
55
ms.topic: how-to
66
ms.reviewer: Mravela
77
---
88

99
# Govern discovered apps
1010

1111

12-
1312
After you review the list of discovered apps in your environment, you can secure your environment by approving safe apps (**Sanctioned**) or prohibiting unwanted apps (**Unsanctioned**) in the following ways.
1413

14+
## Prerequisites
15+
16+
Before you can block discovered cloud apps, you must meet the following requirements:
17+
18+
- [Turn on **Cloud Protection** in Microsoft Defender for Endpoint](/defender-endpoint/enable-cloud-protection-microsoft-defender-antivirus)
19+
- [Turn on **Network Protection** in Microsoft Defender for Endpoint.](/defender-endpoint/network-protection#required-browser-configuration)
20+
- Install the **Microsoft Defender Browser Protection** add-on across all non-Microsoft browsers in your organization.
21+
1522
## Sanctioning/unsanctioning an app
1623

1724
You can mark a specific risky app as unsanctioned by clicking the three dots at the end of the row. Then select **Unsanctioned**. Unsanctioning an app doesn't block use, but enables you to more easily monitor its use with the cloud discovery filters. You can then notify users of the unsanctioned app and suggest an alternative safe app for their use, or [generate a block script using the Defender for Cloud Apps APIs](api-discovery-script.md) to block all unsanctioned apps.

defender-for-identity/deploy/prerequisites-sensor-version-3.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -70,13 +70,13 @@ Applying the **Unified Sensor RPC Audit** tag enables a new, tested capability o
7070
**Steps to apply the configuration:**
7171

7272
1. In the **Microsoft Defender portal**, navigate to: **System > Settings > Microsoft Defender XDR > Asset Rule Management**.
73-
1. Create a new rule.
73+
1. Select **Create a new rule**
7474

7575
![Screenshot that shows how to add a new rule.](media/prerequisites-sensor-version-3/new-rule.png)
7676

7777
3. In the side panel:
7878

79-
1. Select a **name** for the rule.
79+
1. Enter a **Rule name** and **Description**.
8080

8181
1. Set **rule conditions** using `Device name`, `Domain`, or `Device tag` to target the desired machines.
8282

@@ -88,9 +88,15 @@ Applying the **Unified Sensor RPC Audit** tag enables a new, tested capability o
8888

8989
![Screenshot that shows the config tag.](media/prerequisites-sensor-version-3/tag.png)
9090

91-
5. Click **Submit** to save the rule.
91+
5. Select **Next** to review and finish creating the rule and then select **Submit**.
9292

93-
Offboarding a device from this configuration can be done by **deleting the asset rule** or **modifying the rule conditions** so the device no longer matches.
93+
### Updating rules
94+
Offboarding a device from this configuration can be done **only** from **deleting the asset rule** or **modifying the rule conditions** so the device no longer matches.
95+
96+
>[!NOTE]
97+
> It may take up to 1 hour for changes to be reflected in the portal.
98+
99+
Learn more about Asset Management Rule [here](/defender-xdr/configure-asset-rules)
94100

95101
## Configure Windows auditing
96102

defender-for-identity/remove-rbcd-microsoft-entra-seamless-single-sign-on-account.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,6 @@ ms.author: rlitinsky
66
ms.service: microsoft-defender-for-identity
77
ms.topic: article
88
ms.date: 08/22/2024
9-
ms.subservice: ''
109
ms.reviewer: LiorShapiraa
1110
---
1211

defender-office-365/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,8 @@
120120
href: mdo-sec-ops-guide.md
121121
- name: SecOps guide for Teams protection in Defender for Office 365
122122
href: mdo-support-teams-sec-ops-guide.md
123+
- name: SecOps guide for email authentication in Microsoft 365
124+
href: email-auth-sec-ops-guide.md
123125
- name: Threat classification
124126
href: mdo-threat-classification.md
125127
- name: Security recommendations for priority accounts

0 commit comments

Comments
 (0)