Skip to content

Commit 9e6f9f8

Browse files
authored
Merge branch 'main' into WI425757-release-note-executive-summary-report
2 parents 739342a + fac0d39 commit 9e6f9f8

File tree

111 files changed

+1356
-332
lines changed

Some content is hidden

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

111 files changed

+1356
-332
lines changed

ATPDocs/investigate-security-alerts.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,7 @@ Investigate alerts that are affecting your environment, understand what they mea
1111

1212
Begin your investigation by selecting an alert from the **Alerts** page in the Microsoft Defender portal. The alerts page displays a list of all security alerts generated by Defender for Identity, including their severity, status, and impacted assets. Selecting an alert opens the alert page, which contains the alert title, the affected assets, the details side pane, and in some cases, an alert story.
1313

14-
> [!NOTE]
15-
> The **alert story** and **export to Excel** options are only available for alerts that use the classic Defender for Identity structure.
16-
> For more information about differences in how alerts are presented in the Defender portal, see [View and manage alerts](understanding-security-alerts.md).
14+
1715

1816
## Investigate using the alert story
1917

@@ -25,6 +23,10 @@ The Important information section includes additional technical details that sup
2523

2624
Together, the alert story, alert graph, and Important information give you a complete picture of the alert. They help you understand what triggered the alert, which entities were involved, and whether the activity requires further investigation or action.
2725

26+
> [!NOTE]
27+
> The **alert story** is only visible for alerts that use the classic Defender for Identity structure.
28+
> For more information about differences in how alerts are presented in the Defender portal, see [View and manage alerts](understanding-security-alerts.md).
29+
2830
## Take action from the details pane
2931
Once you've selected an alert of interest, the details pane changes to display information about the selected alert, historic information when it's available, and offer recommended actions to take action on this alert.
3032

@@ -35,6 +37,10 @@ Once you're done investigating, go back to the alert you started with, mark the
3537

3638
To get more details on a security alert, select **Export** on an alert details page to download the detailed Excel alert report.
3739

40+
> [!NOTE]
41+
> The **export to Excel** option is also only available for alerts that use the classic Defender for Identity structure.
42+
> For more information about differences in how alerts are presented in the Defender portal, see [View and manage alerts](understanding-security-alerts.md).
43+
3844

3945
The downloaded file includes summary details about the alert on the first tab, including:
4046

-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/cas-compliance-trust.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Microsoft Defender for Cloud Apps – privacy
33
description: Learn about how Microsoft Defender for Cloud Apps manages user privacy.
4-
ms.date: 11/24/2024
4+
ms.date: 06/17/2025
55
ms.topic: concept-article
66
---
77
# Privacy with Microsoft Defender for Cloud Apps
@@ -22,7 +22,7 @@ Microsoft Defender for Cloud Apps collects information from your configured clou
2222
- User and group configurations
2323

2424
> [!NOTE]
25-
> The data collected from the various applications is dependent on the customer-provided data from the various applications and may include personal information.
25+
> The data collected from the various applications is dependent on the customer-provided data from the various applications and might include personal information.
2626
2727
## Data storage location
2828

@@ -31,7 +31,7 @@ Defender for Cloud Apps operates in the Microsoft Azure data centers in the foll
3131
|Customer provisioning location |Data storage location |
3232
|---------|---------|
3333
|**Customers whose tenants are provisioned in the United States** | United States |
34-
|**Customers whose tenants are provisioned in the European Union or the United Kingdom** | Either the European Union and/or the United Kingdom |
34+
|**Customers whose tenants are provisioned in the European Union or the United Kingdom** | The European Union or the United Kingdom, depending on service availability. |
3535
|**Customers whose tenants are provisioned in any other region** | The United States and/or a data center in the region that's nearest to the location of where the customer's Microsoft Entra tenant has been provisioned. |
3636

3737
In addition to the locations above, the App Governance features within Defender for Cloud Apps operate in the Microsoft Azure data centers in the following geographical regions listed below. Customer with App Governance enabled will have data stored within the data storage location the customer provisions in above, and in a second data storage location as described below:
@@ -52,7 +52,13 @@ In addition to the locations above, the App Governance features within Defender
5252

5353
Customer data collected by Defender for Cloud Apps is either stored in your tenant location, as described in the previous tables, or in the geographic location of another online service that Defender for Cloud Apps shares data with, as defined by the data storage rules of that online service.
5454

55-
If Defender for Cloud Apps data is stored in your tenant location, your tenant isn't movable after having been created. To view your Defender for Cloud Apps tenant location in the Microsoft Defender portal, go to **Settings > Cloud Apps > About > Region**.
55+
56+
### View your data storage location
57+
58+
To view your Defender for Cloud Apps tenant location in the Microsoft Defender portal, go to **Settings > Cloud Apps > About > Region**.
59+
60+
> [!NOTE]
61+
> If Defender for Cloud Apps data is stored in your tenant location, your tenant isn't movable after having been created.
5662
5763
## Data retention
5864

@@ -62,7 +68,7 @@ Your data is kept and is available to you while the license is under grace perio
6268

6369
## Data sharing for Microsoft Defender for Cloud Apps
6470

65-
Defender for Cloud Apps shares data, including customer data, among the following Microsoft products also licensed by the customer. For customers in the Government Community Cloud (GCC), data sharing between government and commercial cloud environments may occur, depending on the location of the service offering.
71+
Defender for Cloud Apps shares data, including customer data, among the following Microsoft products also licensed by the customer. For customers in the Government Community Cloud (GCC), data sharing between government and commercial cloud environments might occur, depending on the location of the service offering.
6672

6773
- Microsoft Defender XDR
6874
- Microsoft Defender for Cloud

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).

CloudAppSecurityDocs/investigate-anomaly-alerts.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,17 @@ ms.topic: how-to
1111

1212
Microsoft Defender for Cloud Apps provides security detections and alerts for malicious activities. The purpose of this guide is to provide you with general and practical information on each alert, to help with your investigation and remediation tasks. Included in this guide is general information about the conditions for triggering alerts. However, it's important to note that since anomaly detections are nondeterministic by nature, they're only triggered when there's behavior that deviates from the norm. Finally, some alerts might be in preview, so regularly review the official documentation for updated alert status.
1313

14+
> [!IMPORTANT]
15+
> Starting June 2025, Microsoft Defender for Cloud Apps began transitioning anomaly detection policies to a dynamic threat detection model. This model automatically adapts detection logic to the evolving threat landscape, keeping detections current without manual configuration or policy updates. As part of these improvements to overall security, and to provide more accurate and timely alerts, several legacy policies have been disabled:
16+
>
17+
> - Activity from suspicious IP addresses
18+
> - Suspicious inbox manipulation rules
19+
> - Suspicious email deletion activity
20+
> - Activity from anonymous IP addresses
21+
> - Suspicious inbox forwarding
22+
>
23+
> You will continue to receive the same standard of protection without disruption to your existing security coverage. No action is required from your side.
24+
1425
## MITRE ATT\&CK
1526

1627
To explain and make it easier to map the relationship between Defender for Cloud Apps alerts and the familiar MITRE ATT\&CK Matrix, we've categorized the alerts by their corresponding MITRE ATT\&CK tactic. This extra reference makes it easier to understand the suspected attacks technique potentially in use when a Defender for Cloud Apps alert is triggered.
@@ -52,6 +63,9 @@ This section describes alerts indicating that a malicious actor might be attempt
5263

5364
### Activity from anonymous IP address
5465

66+
> [!NOTE]
67+
> As part of ongoing improvements to Defender for Cloud Apps alert threat protection capabilities, this policy has been disabled, migrated to the new dynamic model and renamed to **Activity from a TOR IP address** and **Anonymous proxy activity**.
68+
5569
**Description**
5670

5771
Activity from an IP address that has been identified as an anonymous proxy IP address by Microsoft Threat Intelligence or by your organization. These proxies can be used to hide a device's IP address and might be used for malicious activities.
@@ -101,6 +115,9 @@ Detecting anomalous locations requires an initial learning period of seven days
101115

102116
### Activity from suspicious IP addresses
103117

118+
> [!NOTE]
119+
> As part of ongoing improvements to Defender for Cloud Apps alert threat protection capabilities, this policy has been disabled, migrated to the new dynamic model and renamed to **Successful logon from a suspicious IP address**.
120+
104121
Activity from an IP address that has been identified as risky by Microsoft Threat Intelligence or by your organization. These IP addresses were identified as being involved in malicious activities, such as performing password spray, botnet command and control (C&C), and might indicate a compromised account.
105122

106123
**TP**, **B-TP**, or **FP**?
@@ -317,6 +334,9 @@ Activities in a single session indicating that, a user performed suspicious chan
317334

318335
### Suspicious email deletion activity (by user)
319336

337+
> [!NOTE]
338+
> As part of ongoing improvements to Defender for Cloud Apps alert threat protection capabilities, this policy has been disabled, migrated to the new dynamic model and renamed to **Suspicious email deletion activity**.
339+
320340
Activities in a single session indicating that, a user performed suspicious email deletions. The deletion type was the "hard delete" type, which makes the email item deleted and not available in the user's mailbox. The deletion was made from a connection that includes uncommon preferences such as ISP, country/region, and user agent. This can indicate an attempted breach of your organization, such as attackers attempting to mask operations by deleting emails related to spam activities.
321341

322342
**TP**, **B-TP**, or **FP**?
@@ -340,6 +360,10 @@ Activities in a single session indicating that, a user performed suspicious emai
340360

341361
### Suspicious inbox manipulation rule
342362

363+
> [!NOTE]
364+
> As part of ongoing improvements to Defender for Cloud Apps alert threat protection capabilities, this policy has been disabled, migrated to the new dynamic model.
365+
> If you previously configured governance actions or email notifications for this policy, you can re-enable it at any time in the Microsoft Defender portal > Cloud Apps > Policy management page.
366+
343367
Activities indicating that an attacker gained access to a user's inbox and created a suspicious rule. Manipulation rules, such as deleting or moving messages, or folders, from a user's inbox might be an attempt to exfiltrate information from your organization. Similarly, they can indicate an attempt to manipulate information that a user sees or to use their inbox to distribute spam, phishing emails, or malware. Defender for Cloud Apps profiles your environment and triggers alerts when suspicious inbox manipulation rules are detected on a user's inbox. This might indicate that the user's account is compromised.
344368

345369
**TP**, **B-TP**, or **FP**?
@@ -538,6 +562,9 @@ This section describes alerts indicating that a malicious actor might be attempt
538562

539563
### Suspicious inbox forwarding
540564

565+
> [!NOTE]
566+
> As part of ongoing improvements to Defender for Cloud Apps alert threat protection capabilities, this policy has been disabled, migrated to the new dynamic model and renamed to **Suspicious email forwarding rule created by third-party app**.
567+
541568
Activities indicating that an attacker gained access to a user's inbox and created a suspicious rule. Manipulation rules, such as forward all or specific emails to another email account might be an attempt to exfiltrate information from your organization. Defender for Cloud Apps profiles your environment and triggers alerts when suspicious inbox manipulation rules are detected on a user's inbox. This might indicate that the user's account is compromised.
542569

543570
**TP**, **B-TP**, or **FP**?

0 commit comments

Comments
 (0)