You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ATPDocs/investigate-security-alerts.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,7 @@ Investigate alerts that are affecting your environment, understand what they mea
11
11
12
12
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.
13
13
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
+
17
15
18
16
## Investigate using the alert story
19
17
@@ -25,6 +23,10 @@ The Important information section includes additional technical details that sup
25
23
26
24
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.
27
25
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
+
28
30
## Take action from the details pane
29
31
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.
30
32
@@ -35,6 +37,10 @@ Once you're done investigating, go back to the alert you started with, mark the
35
37
36
38
To get more details on a security alert, select **Export** on an alert details page to download the detailed Excel alert report.
37
39
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
+
38
44
39
45
The downloaded file includes summary details about the alert on the first tab, including:
Copy file name to clipboardExpand all lines: ATPDocs/sensor-settings.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,6 +58,8 @@ The sensors page provides the following information about each sensor:
58
58
59
59
***Standalone sensor**
60
60
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
+
61
63
***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.
62
64
63
65
***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
186
188
187
189
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.
188
190
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.
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/cas-compliance-trust.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Microsoft Defender for Cloud Apps – privacy
3
3
description: Learn about how Microsoft Defender for Cloud Apps manages user privacy.
4
-
ms.date: 11/24/2024
4
+
ms.date: 06/17/2025
5
5
ms.topic: concept-article
6
6
---
7
7
# Privacy with Microsoft Defender for Cloud Apps
@@ -22,7 +22,7 @@ Microsoft Defender for Cloud Apps collects information from your configured clou
22
22
- User and group configurations
23
23
24
24
> [!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.
26
26
27
27
## Data storage location
28
28
@@ -31,7 +31,7 @@ Defender for Cloud Apps operates in the Microsoft Azure data centers in the foll
|**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.|
35
35
|**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. |
36
36
37
37
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
52
52
53
53
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.
54
54
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.
56
62
57
63
## Data retention
58
64
@@ -62,7 +68,7 @@ Your data is kept and is available to you while the license is under grace perio
62
68
63
69
## Data sharing for Microsoft Defender for Cloud Apps
64
70
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.
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/cloud-discovery-anonymizer.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,12 @@ Key points:
17
17
- Resolving usernames is done ad-hoc, per-username by deciphering a given encrypted username.
18
18
- Anonymization capabilities aren't supported when using the "Defender for Cloud Apps Proxy" stream.
19
19
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
+
20
26
## How data anonymization works
21
27
22
28
1. There are three ways to apply data anonymization:
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/discovered-apps-api-graph.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,16 @@
2
2
title: Work with discovered apps via Graph API | Microsoft Defender for Cloud Apps
3
3
description: Learn how to work with apps discovered by Microsoft Defender for Cloud Apps via Graph API.
4
4
ms.topic: how-to #Don't change
5
-
ms.date: 06/24/2024
6
-
5
+
ms.date: 06/18/2025
7
6
#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
-
9
7
---
10
8
11
9
# Work with discovered apps via Graph API (Preview)
12
10
13
11
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.
14
12
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
+
16
15
17
16
## Prerequisites
18
17
@@ -22,7 +21,7 @@ Before you start using the Graph API, make sure to create an app and get an acce
22
21
23
22
- Take note of your app secret and copy its value to use later on in your scripts.
24
23
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.
26
25
27
26
For more information, see:
28
27
@@ -36,7 +35,7 @@ For more information, see:
36
35
To get a high level summary of all the data available on your **Discovered apps** page, run the following GET command:
37
36
38
37
```http
39
-
GET https://graph.microsoft.com/beta/dataDiscovery/cloudAppDiscovery/uploadedStreams
38
+
GET https://graph.microsoft.com/beta/security/dataDiscovery/cloudAppDiscovery/uploadedStreams
40
39
```
41
40
42
41
To drill down to data for a specific stream:
@@ -88,4 +87,4 @@ GET https://graph.microsoft.com/beta/security/dataDiscovery/cloudAppDiscovery
88
87
89
88
## Related content
90
89
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).
:::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
+
63
65
64
66
## Malware governance actions (Preview)
65
67
@@ -81,7 +83,7 @@ The following governance actions can be taken for connected apps either on a spe
81
83
82
84
-**Trash** – Move the file to the trash folder. (Box, Dropbox, Google Drive, OneDrive, SharePoint)
:::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":::
85
87
86
88
> [!NOTE]
87
89
> 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).
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/investigate-anomaly-alerts.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,17 @@ ms.topic: how-to
11
11
12
12
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.
13
13
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
+
14
25
## MITRE ATT\&CK
15
26
16
27
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
52
63
53
64
### Activity from anonymous IP address
54
65
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
+
55
69
**Description**
56
70
57
71
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
101
115
102
116
### Activity from suspicious IP addresses
103
117
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
+
104
121
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.
105
122
106
123
**TP**, **B-TP**, or **FP**?
@@ -317,6 +334,9 @@ Activities in a single session indicating that, a user performed suspicious chan
317
334
318
335
### Suspicious email deletion activity (by user)
319
336
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
+
320
340
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.
321
341
322
342
**TP**, **B-TP**, or **FP**?
@@ -340,6 +360,10 @@ Activities in a single session indicating that, a user performed suspicious emai
340
360
341
361
### Suspicious inbox manipulation rule
342
362
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
+
343
367
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.
344
368
345
369
**TP**, **B-TP**, or **FP**?
@@ -538,6 +562,9 @@ This section describes alerts indicating that a malicious actor might be attempt
538
562
539
563
### Suspicious inbox forwarding
540
564
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
+
541
568
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.
0 commit comments