Skip to content

Commit 7df14d0

Browse files
Merge branch 'main' into martin77s-patch-2
2 parents b1c5c2d + 8b57369 commit 7df14d0

File tree

3 files changed

+30
-6
lines changed

3 files changed

+30
-6
lines changed

defender-endpoint/linux-preferences.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -446,17 +446,18 @@ Configure filesystems to be unmonitored/excluded from real-time protection (RTP)
446446
> [!NOTE]
447447
> Configured filesystem is unmonitored only if it's present in Microsoft's list of permitted unmonitored filesystems.
448448
449-
By default, NFS and Fuse are unmonitored from RTP, Quick, and Full scans. However, they can still be scanned by a custom scan. For example, to remove NFS from the list of unmonitored filesystems list, update the managed config file as shown below. This will automatically add NFS to the list of monitored filesystems for RTP.
449+
By default, `cifs`, `fuse`, `nfs`, `nfs4` and `smb` are unmonitored from RTP, Quick, and Full scans. However, they can still be scanned by a custom scan. For example, to remove `nfs` and `nfs4` from the list of unmonitored filesystems list, update the managed config file as shown below. This will add `nfs`/`nfs4` to the list of monitored filesystems for RTP.
450+
Currently monitoring `nfs4`, `cifs` and `smb` filesystems is in preview mode for RTP mode.
450451

451452
```JSON
452453
{
453454
"antivirusEngine":{
454-
"unmonitoredFilesystems": ["Fuse"]
455+
"unmonitoredFilesystems": ["cifs","fuse","smb"]
455456
}
456457
}
457458
```
458459

459-
To remove both NFS and Fuse from unmonitored list of filesystems, use the following snippet:
460+
To remove all entries from unmonitored list of filesystems, use the following snippet:
460461

461462
```JSON
462463
{
@@ -1126,4 +1127,4 @@ To verify that your `/etc/opt/microsoft/mdatp/managed/mdatp_managed.json` is wor
11261127

11271128
Once you've built the configuration profile for your enterprise, you can deploy it through the management tool that your enterprise is using. Defender for Endpoint on Linux reads the managed configuration from `/etc/opt/microsoft/mdatp/managed/mdatp_managed.json`.
11281129

1129-
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
1130+
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

defender-for-identity/deploy/deploy-defender-identity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,8 @@ Once you've completed the steps to prepare your environment, and assigned roles
2121
Identify your architecture and your requirements, and then use the table below to select the appropriate deployment for the servers in your environment.
2222

2323
|Server configuration |Server Operating System |Recommended deployment |
24-
|---------|---------|---------|---------|
25-
|Domain controller | Windows Server 2019 or later with the [March 2024 Cumulative Update](https://support.microsoft.com/topic/march-12-2024-kb5035857-os-build-20348-2340-a7953024-bae2-4b1a-8fc1-74a17c68203c) or later.<br> * **See Note**.|[Defender for Identity sensor v3.x (Preview)](prerequisites-sensor-version-3.md)<br> * **See Note**. |
24+
|---------|---------|---------|
25+
|Domain controller | Windows Server 2019 or later with the [June 2025 Cumulative Update](https://support.microsoft.com/en-us/topic/june-10-2025-kb5060526-os-build-20348-3807-4e9453c4-6602-48ea-b349-689cd66dfdb9) or later.<br> * **See Note**.|[Defender for Identity sensor v3.x (Preview)](prerequisites-sensor-version-3.md)<br> * **See Note**. |
2626
|Domain controller |Windows Server 2016 or later |[Defender for Identity sensor v2.x](prerequisites-sensor-version-2.md) |
2727
|[Active Directory Federation Services (AD FS)](active-directory-federation-services.md) | Windows Server 2016 or later |[Defender for Identity sensor v2.x](prerequisites-sensor-version-2.md) |
2828
|[Active Directory Certificate Services (AD CS)](active-directory-federation-services.md) | Windows Server 2016 or later |[Defender for Identity sensor v2.x](prerequisites-sensor-version-2.md) |

defender-xdr/phishing-triage-agent.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -413,6 +413,29 @@ Administrators configure the agent’s identity and access levels during install
413413

414414
The Phishing Triage Agent operates within a zero-trust environment. The system enforces organizational policies on every agent action by evaluating the intent and scope of each operation. All decisions, reasoning, and actions taken by the agent are transparently documented as a decision tree within Defender and recorded in Microsoft Purview audit logs for traceability and compliance.
415415

416+
417+
### I want to try the Phishing Triage Agent - how do I set it up in Microsoft Defender?
418+
419+
To try the agent, you must first have access to **Security Copilot in Microsoft Defender**. If you don’t yet have Security Copilot, see [Get started with Security Copilot](/security-copilot/get-started-security-copilot) or contact your Microsoft representative.
420+
421+
After you enable Security Copilot, the agent setup option appears in the Microsoft Defender portal if your environment meets the necessary [prerequisites](#prerequisites). For more information on agent setup, see [Set up the Phishing Triage Agent](#set-up-the-phishing-triage-agent):
422+
423+
424+
### I've tried the Phishing Triage Agent - how can I estimate the SCU capacity needed for the agent in my organization?
425+
426+
If you joined the limited-time trial, the agent automatically starts consuming SCUs provisioned for the workspace when the trial period ends.
427+
428+
It's important to ensure that your organization has sufficient SCUs for healthy agent operation. To evaluate SCU usage and plan capacity going forward, see the [Usage monitoring dashboard in the Security Copilot portal](https://securitycopilot.microsoft.com/usage-monitoring). The dashboard shows:
429+
430+
- **Cost per email processed**
431+
- **Capacity consumption over time**
432+
433+
You can also export the dashboard data into Excel for more detailed analysis.
434+
435+
For more information about managing SCUs, see [Manage security compute unit usage in Security Copilot](/copilot/security/manage-usage).
436+
437+
If the agent is already running and you have sufficient capacity in your organization, no further action is required and the agent will keep running. If you choose to discontinue use, follow the [offboarding steps](#remove-the-agent) in the documentation.
438+
416439
## Related content
417440

418441
- [Microsoft Security Copilot agents](/copilot/security/agents-overview)

0 commit comments

Comments
 (0)