Skip to content

Commit 00aa4a0

Browse files
authored
Merge branch 'main' into patch-1
2 parents 555a82c + a4af5e8 commit 00aa4a0

File tree

87 files changed

+665
-171
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

87 files changed

+665
-171
lines changed
-19 KB
Loading

ATPDocs/okta-integration.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -100,9 +100,8 @@ After assigning both roles, you can remove the Super Admin role. This ensures th
100100
1. Select **Create new role**.
101101
1. Set the role name to **Microsoft Defender for Identity**.
102102
1. Select the permissions you want to assign to this role. Include the following permissions:
103-
- **Suspend users**
104-
- **Unsuspend users**
105-
- **Clear users’ session**
103+
- **Edit user's lifecycle states**
104+
- **Edit user's authenticator operations**
106105
- **View roles, resources, and admin assignments**
107106
1. Select **Save role**.
108107

ATPDocs/sensor-settings.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,8 @@ The sensors page provides the following information about each sensor:
5858

5959
* **Standalone sensor**
6060

61+
* **Entra Connect sensor**. If your sensor is installed on a domain controller server with Entra Connect configured, such as in a testing environment, the sensor type is shown as **Domain controller sensor** instead.
62+
6163
* **ADCS sensor** (Active Directory Certificate Services). If your sensor is installed on a domain controller server with AD CS configured, such as in a testing environment, the sensor type is shown as **Domain controller sensor** instead.
6264

6365
* **Domain**: Displays the fully qualified domain name of the Active Directory domain where the sensor is installed.
@@ -186,9 +188,9 @@ Every few minutes, Defender for Identity sensors check whether they have the lat
186188

187189
1. Sensors selected for **Delayed update** start their update process 72 hours after the Defender for Identity cloud service is updated. These sensors will then use the same update process as automatically updated sensors.
188190

189-
For any sensor that fails to complete the update process, a relevant [health alert](health-alerts.md#sensor-outdated) is triggered, and is sent as a notification.
191+
For any sensor that fails to complete the update process, a relevant [health alert](health-alerts.md#sensor-outdated) is triggered, and is sent as a notification.
190192

191-
![Sensor update failure.](media/sensor-outdated.png)
193+
![Sensor update failure.](media/sensor-outdated.png)
192194

193195
### Silently update the Defender for Identity sensor
194196

CloudAppSecurityDocs/anomaly-detection-policy.md

Lines changed: 66 additions & 29 deletions
Large diffs are not rendered by default.

CloudAppSecurityDocs/cloud-discovery-anonymizer.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,12 @@ Key points:
1717
- Resolving usernames is done ad-hoc, per-username by deciphering a given encrypted username.
1818
- Anonymization capabilities aren't supported when using the "Defender for Cloud Apps Proxy" stream.
1919

20+
## Prerequisites
21+
22+
To resolve (deanonymize) usernames in Cloud Discovery data:
23+
24+
- You must have the [Cloud Discovery global admin](manage-admins.md#built-in-admin-roles-in-defender-for-cloud-apps) role with anonymization permissions enabled during role assignment.
25+
2026
## How data anonymization works
2127

2228
1. There are three ways to apply data anonymization:

CloudAppSecurityDocs/discovered-apps-api-graph.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,16 @@
22
title: Work with discovered apps via Graph API | Microsoft Defender for Cloud Apps
33
description: Learn how to work with apps discovered by Microsoft Defender for Cloud Apps via Graph API.
44
ms.topic: how-to #Don't change
5-
ms.date: 06/24/2024
6-
5+
ms.date: 06/18/2025
76
#customer intent: As a security engineer, I want to work with discovered apps via API so that I can customize and automate the Microsoft Defender for Cloud Apps **Discovered apps** page functionality.
8-
97
---
108

119
# Work with discovered apps via Graph API (Preview)
1210

1311
Microsoft Defender for Cloud Apps supports a Microsoft Graph API that you can use to work with discovered cloud apps, to customize and automate the **Discovered apps** page functionality in the Microsoft Defender portal.
1412

15-
This article provides sample procedures for using the [uploadedStreams API](/graph/api/security-datadiscoveryreport-list-uploadedstreams?view=graph-rest-beta) for common purposes.
13+
This article provides sample procedures for using the [uploadedStreams API](/graph/api/security-datadiscoveryreport-list-uploadedstreams?view=graph-rest-beta&preserve-view=true&tabs=http) for common purposes.
14+
1615

1716
## Prerequisites
1817

@@ -22,7 +21,7 @@ Before you start using the Graph API, make sure to create an app and get an acce
2221

2322
- Take note of your app secret and copy its value to use later on in your scripts.
2423

25-
You'll also need cloud app data streaming into Microsoft Defender for Cloud Apps.
24+
- You need cloud app data streaming into Microsoft Defender for Cloud Apps.
2625

2726
For more information, see:
2827

@@ -36,7 +35,7 @@ For more information, see:
3635
To get a high level summary of all the data available on your **Discovered apps** page, run the following GET command:
3736

3837
```http
39-
GET https://graph.microsoft.com/beta/dataDiscovery/cloudAppDiscovery/uploadedStreams
38+
GET https://graph.microsoft.com/beta/security/dataDiscovery/cloudAppDiscovery/uploadedStreams
4039
```
4140

4241
To drill down to data for a specific stream:
@@ -88,4 +87,4 @@ GET  https://graph.microsoft.com/beta/security/dataDiscovery/cloudAppDiscovery
8887

8988
## Related content
9089

91-
For more information, see [Working with discovered apps](discovered-apps.md) and the [Microsoft Graph API reference](/graph/api/resources/security-cloudappdiscovery-overview?view=graph-rest-beta).
90+
For more information, see [Working with discovered apps](discovered-apps.md) and the [Microsoft Graph API reference](/graph/api/resources/security-cloudappdiscovery-overview?view=graph-rest-beta&preserve-view=true).

CloudAppSecurityDocs/governance-actions.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,9 @@ The following governance actions can be taken for connected apps either on a spe
5959

6060
- **Trash** – Move the file to the trash folder. (Box, Dropbox, Google Drive, OneDrive, SharePoint, Cisco Webex)
6161

62-
![policy_create alerts.](media/policy_create-alerts.png)
62+
:::image type="content" source="media/governance-actions/governance-actions-box.png" alt-text="Screenshot that shows the available file governance actions for Box and Dropbox." lightbox="media/governance-actions/governance-actions-box.png":::
63+
64+
6365

6466
## Malware governance actions (Preview)
6567

@@ -81,7 +83,7 @@ The following governance actions can be taken for connected apps either on a spe
8183

8284
- **Trash** – Move the file to the trash folder. (Box, Dropbox, Google Drive, OneDrive, SharePoint)
8385

84-
:::image type="content" source="media/governance-actions/image1.png" alt-text="Malware governance actions.":::
86+
:::image type="content" source="media/governance-actions/governance-actions-dropbox-google-workspace.png" alt-text="Screenshot that shows malware governance actions." lightbox="media/governance-actions/governance-actions-dropbox-google-workspace.png":::
8587

8688
> [!NOTE]
8789
> In SharePoint and OneDrive, Defender for Cloud Apps supports user quarantine only for files in Shared Documents libraries (SharePoint Online) and files in the Documents library (OneDrive for Business).
245 KB
Loading
File renamed without changes.
-41.7 KB
Binary file not shown.

0 commit comments

Comments
 (0)