Skip to content

Commit 8a8f79c

Browse files
authored
Merge pull request #3351 from MicrosoftDocs/main
Published main to live, Wednesday 10:30 AM PST, 04/02
2 parents 2bdd150 + ec80797 commit 8a8f79c

10 files changed

+97
-74
lines changed

CloudAppSecurityDocs/get-started.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,11 @@ After you connect an app, you can gain deeper visibility so you can investigate
6161

6262
**How to page**: [Protect sensitive information with DLP policies](policies-information-protection.md)
6363

64-
**Recommended task**: Enable file monitoring and create file policies
64+
**Recommended tasks**
65+
66+
- Enable file monitoring and create file policies
67+
68+
- To enable File monitoring of Microsoft 365 files, you are required to use a relevant Entra Admin ID, such as Application Administrator or Cloud Application Administrator. For more details, see [Microsoft Entra built-in roles](/entra/identity/role-based-access-control/permissions-reference).
6569

6670
1. In the Microsoft Defender Portal, select **Settings**. Then choose **Cloud Apps**.
6771
1. Under **Information Protection**, select **Files**.
@@ -70,8 +74,6 @@ After you connect an app, you can gain deeper visibility so you can investigate
7074
1. Select the required settings and then select **Save**.
7175
1. In [Step 3](#step-3-control-cloud-apps-with-policies), create [File policies](data-protection-policies.md) to meet your organizational requirements.
7276

73-
> [!TIP]
74-
> You can view files from your connected apps by browsing to **Cloud Apps** > **Files** in the Microsoft Defender Portal.
7577

7678
**Migration recommendation**
7779
We recommend using Defender for Cloud Apps sensitive information protection in parallel with your current Cloud Access Security Broker (CASB) solution. Start by [connecting the apps you want to protect](enable-instant-visibility-protection-and-governance-actions-for-your-apps.md) to Microsoft Defender for Cloud Apps. Since API connectors use out-of-band connectivity, no conflict will occur. Then progressively migrate your [policies](control-cloud-apps-with-policies.md) from your current CASB solution to Defender for Cloud Apps.

CloudAppSecurityDocs/manage-admins.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ Microsoft Defender for Cloud Apps supports role-based access control. This artic
2020
>
2121
> - Microsoft 365 and Microsoft Entra roles aren't listed in the Defender for Cloud Apps **Manage admin access** page. To assign roles in Microsoft 365 or Microsoft Entra ID, go to the relevant RBAC settings for that service.
2222
> - Defender for Cloud Apps uses Microsoft Entra ID to determine the user's [directory level inactivity timeout setting](/azure/azure-portal/set-preferences#change-the-directory-timeout-setting-admin). If a user is configured in Microsoft Entra ID to never sign out when inactive, the same setting will apply in Defender for Cloud Apps as well.
23+
> - Defender for Cloud Apps Information Protection enablement requires an Entra Admin ID, such as: Application Administrator or Cloud Application Administrator. For more details, see [Microsoft Entra built-in roles](/entra/identity/role-based-access-control/permissions-reference) and [Protect your Microsoft 365 environment](/defender-cloud-apps/protect-office-365)
2324
2425
By default, the following Microsoft 365 and [Microsoft Entra ID](/azure/active-directory/roles/permissions-reference) admin roles have access to Defender for Cloud Apps:
2526

CloudAppSecurityDocs/release-notes.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,16 +19,25 @@ For more information on what's new with other Microsoft Defender security produc
1919

2020
For news about earlier releases, see [Archive of past updates for Microsoft Defender for Cloud Apps](release-note-archive.md).
2121

22+
2223
## April 2025
2324

24-
### New Applications page in Defender XDR
25+
26+
### OAuthAppInfo table added to Defender XDR advanced hunting (Preview)
27+
28+
The [OAuthAppInfo](/defender-xdr/advanced-hunting-oauthappinfo-table) table is now available in Defender XDR advanced hunting, enabling security teams to explore and analyze OAuth app-related metadata with enhanced visibility.
29+
30+
This table provides details on Microsoft 365-connected OAuth applications that are registered with Microsoft Entra ID and accessible through the Defender for Cloud Apps app governance capability.
31+
32+
### New Applications page in Defender XDR (Preview)
2533

2634
The new Applications page consolidates all SaaS and connected OAuth applications into a single, unified inventory. This centralized view streamlines application discovery, monitoring, and management, providing greater visibility and control across your environment.
2735

2836
The page surfaces key insights such as risk scores, usage patterns, publisher verification status, and privilege levels. These insights help you quickly identify and address high-risk or untagged applications.
2937

3038
For more information, see [Application inventory overview](applications-inventory.md)
3139

40+
3241
## March 2025
3342

3443
### Enhanced Identity Inventory (Preview)

defender-endpoint/linux-preferences.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Set preferences for Microsoft Defender for Endpoint on Linux
2+
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.
55
ms.service: defender-endpoint
66
ms.author: deniseb
77
author: denisebmsft
88
ms.localizationpriority: medium
9-
ms.date: 03/12/2025
9+
ms.date: 03/28/2025
1010
manager: deniseb
1111
audience: ITPro
1212
ms.collection:
@@ -18,7 +18,7 @@ ms.subservice: linux
1818
search.appverid: met150
1919
---
2020

21-
# Configure security settings and policies for Microsoft Defender for Endpoint on Linux
21+
# Configure security settings in Microsoft Defender for Endpoint on Linux
2222

2323
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
2424

@@ -29,9 +29,9 @@ search.appverid: met150
2929

3030
> Want to experience Defender for Endpoint? [Sign up for a free trial.](https://go.microsoft.com/fwlink/p/?linkid=2225630)
3131
32-
## Overview of settings and policies to configure
32+
## Configure your security settings
3333

34-
Microsoft Defender for Endpoint on Linux includes antivirus, anti-malware protection, endpoint detection, and response capabilities. This article summarizes important settings to configure, with links to additional resources.
34+
Microsoft Defender for Endpoint on Linux includes antivirus, anti-malware protection, endpoint detection, and response capabilities. This article summarizes important security settings to configure and includes links to additional resources.
3535

3636
| Settings | Description|
3737
|--|--|
@@ -44,22 +44,22 @@ Microsoft Defender for Endpoint on Linux includes antivirus, anti-malware protec
4444
| 7. Deploy updates. | Microsoft regularly publishes software updates to improve performance, security, and to deliver new features. <br/><br/>See [Deploy updates for Microsoft Defender for Endpoint on Linux](linux-updates.md). |
4545
| 8. Configure network protection (preview) | Network protection helps prevent employees from using any application to access dangerous domains that might host phishing scams, exploits, and other malicious content on the Internet. <br/><br/>See [Network protection for Linux](network-protection-linux.md). |
4646

47-
## Options for configuring security policies and settings
47+
## Options for configuring security settings
4848

49-
To configure your security policies and settings for Defender for Endpoint on Linux, you have two main options:
49+
To configure your security settings in Defender for Endpoint on Linux, you have two main options:
5050

5151
- Use the Microsoft Defender portal (Defender for Endpoint Security Settings Management); or
5252
- Use a configuration profile
5353

54-
If you prefer to use command line to configure your security settings, you can use that to configure certain settings, gather diagnostics, run scans, and more. See [Resources](linux-resources.md#configure-from-the-command-line).
54+
If you prefer to use command line, you can use that to configure certain settings, gather diagnostics, run scans, and more. See [Linux resources: Configure using command line](linux-resources.md#configure-from-the-command-line).
5555

5656
### Defender for Endpoint Security Settings Management
5757

58-
You can configure Defender for Endpoint on Linux in the Microsoft Defender portal ([https://security.microsoft.com](https://security.microsoft.com)) through functionality known as Security Settings Management. For more information, including how to create, edit, and verify your security policies, see [Use Microsoft Defender for Endpoint Security Settings Management to manage Microsoft Defender Antivirus](mde-security-settings-management.md).
58+
You can configure Defender for Endpoint on Linux in the Microsoft Defender portal ([https://security.microsoft.com](https://security.microsoft.com)) through functionality known as Defender for Endpoint Security Settings Management. For more information, including how to create, edit, and verify security policies, see [Use Microsoft Defender for Endpoint Security Settings Management to manage Microsoft Defender Antivirus](mde-security-settings-management.md).
5959

6060
### Configuration profile
6161

62-
You can configure Defender for Endpoint on Linux through a configuration profile that uses a `.json` file. After you have set up your profile, you can deploy it by using your management tool of choice. Preferences managed by the enterprise take precedence over the ones set locally on the device. In other words, users in your enterprise aren't able to change preferences that are set through this configuration profile. If exclusions were added through the managed configuration profile, they can only be removed through the managed configuration profile. The command line works for exclusions that were added locally.
62+
You can configure settings in Defender for Endpoint on Linux through a configuration profile that uses a `.json` file. After you have set up your profile, you can deploy it by using your management tool of choice. Preferences managed by the enterprise take precedence over the ones set locally on the device. In other words, users in your enterprise aren't able to change preferences that are set through this configuration profile. If exclusions were added through the managed configuration profile, they can only be removed through the managed configuration profile. The command line works for exclusions that were added locally.
6363

6464
This article describes the structure of this profile (including a recommended profile that you can use to get started) and instructions on how to deploy the profile.
6565

@@ -456,6 +456,7 @@ By default, NFS and Fuse are unmonitored from RTP, Quick, and Full scans. Howeve
456456
}
457457
}
458458
```
459+
459460
To remove both NFS and Fuse from unmonitored list of filesystems, use the following snippet:
460461

461462
```JSON

defender-endpoint/linux-support-connectivity.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: linux
1717
search.appverid: met150
18-
ms.date: 03/12/2025
18+
ms.date: 03/28/2025
1919
---
2020

2121
# Troubleshoot cloud connectivity issues for Microsoft Defender for Endpoint on Linux
@@ -56,7 +56,7 @@ Testing connection with https://uk-v20.events.data.microsoft.com/ping ... [OK]
5656
Testing connection with https://v20.events.data.microsoft.com/ping ... [OK]
5757
```
5858

59-
If the connectivity test fails, check if the device has Internet access and if [network connections](mde-linux-prerequisites.md#network-connections) are blocked by a proxy or firewall.
59+
If the connectivity test fails, check if the device has Internet access. Also check to see if network connections are blocked by a proxy or firewall. For more information, see [Verify that devices can connect to Defender for Endpoint cloud services](mde-linux-prerequisites.md#verify-that-devices-can-connect-to-defender-for-endpoint-cloud-services).
6060

6161
Failures with curl error 35 or 60, indicate certificate pinning rejection. Check to see if the connection is under SSL or HTTPS inspection. If so, add Microsoft Defender for Endpoint to the allowlist.
6262

@@ -96,7 +96,6 @@ To set the proxy for mdatp, use the following command:
9696
mdatp config proxy set --value http://address:port
9797
```
9898

99-
10099
Upon success, attempt another connectivity test from the command line:
101100

102101
```bash

defender-endpoint/mde-linux-deployment-on-sap.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: linux
1717
search.appverid: met150
18-
ms.date: 02/04/2025
18+
ms.date: 03/28/2025
1919
ms.custom:
2020
- partner-contribution
2121
---
@@ -65,7 +65,7 @@ Here are some important point about SAP applications on Linux Server:
6565

6666
- Microsoft Defender for Endpoint [Build: 101.24082.0004 | Release version: 30.124082.0004.0](/defender-endpoint/linux-whatsnew#oct-2024-build-101240820004--release-version-3012408200040) or later must be deployed.
6767
- Microsoft Defender for Endpoint on Linux supports [Linux releases](/defender-endpoint/mde-linux-prerequisites) used by SAP applications.
68-
- Microsoft Defender for Endpoint on Linux requires connectivity to specific Internet endpoints from VMs to update antivirus definitions. For more information, see [Network connections](mde-linux-prerequisites.md#network-connections).
68+
- Microsoft Defender for Endpoint on Linux requires connectivity to specific Internet endpoints from VMs to update antivirus definitions. For more information, see [Verify that devices can connect to Defender for Endpoint cloud services](mde-linux-prerequisites.md#verify-that-devices-can-connect-to-defender-for-endpoint-cloud-services).
6969
- Microsoft Defender for Endpoint on Linux requires some `crontab` (or other task scheduler) entries to schedule scans, log rotation, and Microsoft Defender for Endpoint updates. Enterprise security teams normally manage these entries. For more information, see [How to schedule an update for Microsoft Defender for Endpoint on Linux](linux-update-mde-linux.md).
7070

7171
As of December 2024, Defender for Endpoint on Linux can safely be configured with real-time protection enabled.

0 commit comments

Comments
 (0)