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/deploy/activate-capabilities.md
+27-15Lines changed: 27 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,20 +7,20 @@ ms.topic: how-to
7
7
8
8
# Activate Microsoft Defender for Identity capabilities directly on a domain controller
9
9
10
-
Microsoft Defender for Endpoint customers, who have already onboarded their domain controllers to Defender for Endpoint, can activate Microsoft Defender for Identity capabilities directly on a domain controller instead of using a [Microsoft Defender for Identity sensor](deploy-defender-identity.md).
10
+
Microsoft Defender for Endpoint customers, who have already onboarded their domain controllers to Defender for Endpoint, can activate Microsoft Defender for Identity capabilities directly on a domain controller instead of using [Microsoft Defender for Identity classic sensor](deploy-defender-identity.md).
11
11
12
12
This article describes how to activate and test Microsoft Defender for Identity capabilities on your domain controller.
13
13
14
14
> [!IMPORTANT]
15
-
> The new sensor is recommended for customers looking to deploy core identity protections to new domain controllers running Windows Server 2019 or newer. For all other identity infrastructure, or for customers looking to deploy the most robust identity protections available from Microsoft Defender for Identity today, we recommend deploying the classic sensor [here](https://learn.microsoft.com/defender-for-identity/deploy/quick-installation-guide)
15
+
> The new Defender for Identity sensor (version 3.x) is recommended for customers looking to deploy core identity protections to new domain controllers running Windows Server 2019 or newer. For all other identity infrastructure, or for customers looking to deploy the most robust identity protections available from Microsoft Defender for Identity today, we recommend deploying the classic sensor [here](quick-installation-guide.md).
16
16
17
17
## Prerequisites
18
18
19
19
Before activating the Defender for Identity capabilities on your domain controller, make sure that your environment complies with the prerequisites in this section.
20
20
21
21
### Defender for Identity sensor conflicts
22
22
23
-
The configuration described in this article doesn't support side-by-side installation with an existing Defender for Identity sensor, and isn't recommended as a replacement for the Defender for Identity sensor.
23
+
The configuration described in this article doesn't support side-by-side installation with an existing Defender for Identity sensor, and isn't recommended as a replacement for the Defender for Identity classic sensor.
24
24
25
25
Make sure that the domain controller where you're planning to activate Defender for Identity capabilities doesn't have a [Defender for Identity sensor](deploy-defender-identity.md) deployed.
26
26
@@ -43,7 +43,7 @@ Your domain controller must be onboarded to Microsoft Defender for Endpoint.
43
43
44
44
For more information, see [Onboard a Windows server](/microsoft-365/security/defender-endpoint/onboard-windows-server).
45
45
46
-
### Required permissions
46
+
### Permissions requirements
47
47
48
48
To access the Defender for Identity **Activation** page, you must either be a [Security Administrator](/entra/identity/role-based-access-control/permissions-reference), or have the following Unified RBAC permissions:
49
49
@@ -80,15 +80,31 @@ Set-MDIConfiguration -Mode Domain -Configuration All
80
80
81
81
## Activate Defender for Identity capabilities
82
82
83
-
After ensuring that your environment is completely configured, activate the Microsoft Defender for Identity capabilities on your domain controller.
83
+
After ensuring that your environment is completely configured, activate the Microsoft Defender for Identity capabilities on your domain controller.
84
84
85
-
1. In the [Defender portal](https://security.microsoft.com), select **Settings > Identities > [Activation](https://security.microsoft.com/settings/identities?tabid=onboarding)**.
85
+
Activate the Defender for Identity from the [Microsoft Defender portal](https://security.microsoft.com).
86
86
87
-
The**Activation**page lists any detected and eligible domain controllers.
87
+
1. Navigate to **System** >**Settings**> **Identities** > **Activation**.
88
88
89
-
1. Select the domain controller where you want to activate the Defender for Identity capabilities and then select **Activate**. Confirm your selection when prompted.
89
+
The Activation page lists servers discovered in Device Inventory and identified as eligible domain controllers.
90
90
91
-
When the activation is complete, a green success banner shows. In the banner, select **Click here to see the onboarded servers** to jump to the **Settings > Identities > Sensors** page, where you can check your sensor health.
91
+
2. Select the domain controller where you want to activate the Defender for Identity capabilities and then select **Activate**. Confirm your selection when prompted.
92
+
93
+
> [!NOTE]
94
+
> You can choose to activate eligible domain controllers either automatically, where Defender for Identity activates them as soon as they're discovered, or manually, where you select specific domain controllers from the list of eligible servers.
95
+
96
+
3. When the activation is complete, a green success banner shows. In the banner, select **Click here to see the onboarded servers** to jump to the **Settings > Identities > Sensors** page, where you can check your sensor health.
97
+
98
+
## Onboarding Confirmation
99
+
100
+
To confirm the sensor has been onboarded:
101
+
102
+
1. Navigate to **System** > **Settings** > **Identities** > **Sensors**.
103
+
104
+
2. Check that the onboarded domain controller is listed.
105
+
106
+
> [!NOTE]
107
+
> The activation doesn't require a restart/reboot. The first time you activate Defender for Identity capabilities on your domain controller, it may take up to an hour for the first sensor to show as **Running** on the **Sensors** page. Subsequent activations are shown within five minutes.
92
108
93
109
## Test activated capabilities
94
110
@@ -106,9 +122,9 @@ Use the following procedures to test your environment for Defender for Identity
106
122
107
123
### Check the ITDR dashboard
108
124
109
-
In the Defender portal, select **Identities > Dashboard** and review the details shown, checking for expected results from your environment.
125
+
In the Defender portal, select **Identities** > **Dashboard**, and review the details shown, checking for expected results from your environment.
110
126
111
-
For more information, see [Work with Defender for Identity's ITDR dashboard (Preview)](../dashboard.md).
127
+
For more information, see [Work with Defender for Identity's ITDR dashboard](../dashboard.md).
112
128
113
129
114
130
### Confirm entity page details
@@ -193,10 +209,6 @@ Test remediation actions on a test user. For example:
193
209
194
210
1. Check Active Directory for the expected activity.
195
211
196
-
> [!NOTE]
197
-
> The current version doesn't collect the User Account Control (UAC) flags correctly. So disabled users, would still appear as Enabled in the portal.
198
-
199
-
200
212
For more information, see [Remediation actions in Microsoft Defender for Identity](../remediation-actions.md).
201
213
202
214
## Deactivate Defender for Identity capabilities on your domain controller
Copy file name to clipboardExpand all lines: ATPDocs/whats-new.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,13 @@ For more information, see also:
22
22
23
23
For updates about versions and features released six months ago or earlier, see the [What's new archive for Microsoft Defender for Identity](whats-new-archive.md).
24
24
25
+
## March 2025
26
+
27
+
### New LDAP query events added to the IdentityQueryEvents table in Advanced Hunting
28
+
New LDAP query events will be added by March 6th to the `IdentityQueryEvents` table in Advanced Hunting to provide more visibility into additional LDAP search queries running in the customer environment.
29
+
This update may lead to an increase in activity within the Advanced Hunting IdentityQueryEvents table for LDAP queries. If you have custom detections related to these queries, you may see a higher number of triggered alerts.
30
+
We recommend that you review your existing custom detections to ensure they align with your objectives. If needed, you can adjust your query accordingly.
@@ -67,6 +74,12 @@ We have added and updated the following events in the `IdentityDirectoryEvents`
67
74
68
75
Additionally, the **built-in schema reference** for Advanced Hunting in Microsoft Defender XDR has been updated to include detailed information on all supported event types (**`ActionType`** values) in identity-related tables, ensuring complete visibility into available events. For more information, see [Advanced hunting schema details](/defender-xdr/advanced-hunting-schema-tables).
69
76
77
+
## January 2025
78
+
79
+
### New Identity guide tour
80
+
81
+
Explore key MDI features with the new **Identities Tour** in the M365 portal. Navigate Incidents, Hunting, and Settings to enhance identity security and threat investigation.
82
+
70
83
## December 2024
71
84
72
85
### New security posture assessment: Prevent Certificate Enrollment with arbitrary Application Policies (ESC15)
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/get-started.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,10 +25,10 @@ Microsoft Defender for Cloud Apps is a security tool and therefore doesn't requi
25
25
26
26
Microsoft Defender for Cloud Apps depends on the following Microsoft Entra ID applications to function properly. Do not disable these applications in Microsoft Entra ID:
27
27
28
-
- Microsoft Defender for Cloud Apps - APIs
29
-
- Microsoft Defender for Cloud Apps - Customer Experience
30
-
- Microsoft Defender for Cloud Apps - Information Protection
31
-
- Microsoft Defender for Cloud Apps - MIP Server
28
+
- Microsoft Defender for Cloud Apps - APIs (ID: 972bb84a-1d27-4bd3-8306-6b8e57679e8c)
29
+
- Microsoft Defender for Cloud Apps - Customer Experience (ID: 9ba4f733-be8f-4112-9c4a-e3b417c44e7d)
30
+
- Microsoft Defender for Cloud Apps - Information Protection (ID: ac6dbf5e-1087-4434-beb2-0ebf7bd1b883)
31
+
- Microsoft Defender for Cloud Apps - MIP Server (ID: 0858ddce-8fca-4479-929b-4504feeed95e)
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/protect-zoom.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,8 +11,6 @@ ms.topic: how-to
11
11
12
12
Zoom is an online video conferencing and collaboration tool. Zoom holds critical data of your organization, and this makes it a target for malicious actors.
13
13
14
-
Connecting Zoom to Defender for Cloud Apps gives you improved insights into your users' activities and provides threat detection using machine learning based anomaly detections.
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/release-notes.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,18 @@ For news about earlier releases, see [Archive of past updates for Microsoft Defe
21
21
22
22
## February 2025
23
23
24
+
### Enhanced Visibility into OAuth Apps Connected to Microsoft 365 - General Availability
25
+
26
+
Defender for Cloud Apps users who use app governance will be able to gain visibility into the origin of OAuth apps connected to Microsoft 365. You can filter and monitor apps that have external origins, to proactively review such apps and improve the security posture of the organization.
27
+
28
+
The new *Permissions filter and export capabilities allow you to quickly identify apps with specific permissions to access Microsoft 365.
29
+
30
+
You can now get granular insights into data accessed by apps using legacy EWS API alongside Microsoft Graph. The enhanced coverage of data usage insights enable you to get deeper visibility into apps accessing emails using legacy EWS API.
31
+
32
+
We're also expanding the coverage of privilege level feature for all popular Microsoft first-party API permissions. The enhanced coverage of privilege level classification enables you to view and monitor apps with powerful permissions into legacy and other non-Graph APIs that have access to Microsoft 365.
33
+
34
+
For more information, see [detailed insights into OAuth apps](/defender-cloud-apps/app-governance-visibility-insights-view-apps#getting-detailed-information-on-an-app).
35
+
24
36
### Enhanced alert source accuracy
25
37
26
38
Microsoft Defender for Cloud Apps is enhancing its alert sources to deliver more precise information. This update, applicable to new alerts only, will be reflected across various experiences and APIs, including the Defender XDR portal, Advanced hunting, and Graph API.
@@ -32,7 +44,11 @@ To learn more about the Graph API alert resource: [alert resource type - Microso
32
44
33
45
### Network requirement updates
34
46
35
-
Microsoft Defender for Cloud Apps has improved its security and performance. Network information in firewalls and additional third-party services must be updated to comply with the new standards. To ensure uninterrupted access to our services you must apply these changes by March 16, 2025.
47
+
Microsoft Defender for Cloud Apps has improved its security and performance. Network information in firewalls and additional third-party services must be updated to comply with the new standards. To ensure uninterrupted access to our portals and services you must apply these changes by March 27, 2025.
48
+
49
+
New CDN domains have been added and must be included in firewall rules to allow outbound traffic on port 443:
50
+
- cdn.cloudappsecurity.com
51
+
- cdn-discovery.cloudappsecurity.com
36
52
37
53
To connect to third-party apps and enable Defender for Cloud Apps, use the following IP addresses:
Copy file name to clipboardExpand all lines: defender-business/get-defender-business.md
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ audience: Admin
9
9
ms.topic: overview
10
10
ms.service: defender-business
11
11
ms.localizationpriority: medium
12
-
ms.date: 06/07/2024
12
+
ms.date: 02/28/2025
13
13
ms.reviewer: efratka
14
14
f1.keywords: NOCSH
15
15
ms.collection:
@@ -35,12 +35,30 @@ Sections include:
35
35
36
36
To get Defender for Business, you can choose from several options:
37
37
38
+
- Work with a Microsoft partner who can help you get everything set up and configured.
38
39
- Try or buy the standalone version of Defender for Business.
39
40
- Get Microsoft 365 Business Premium, which includes Defender for Business.
40
-
- Work with a Microsoft partner who can help you get everything set up and configured.
41
41
42
42
Use the following tabs to learn more about each option.
43
43
44
+
## [Work with a Microsoft partner](#tab/findpartner)
45
+
46
+
Microsoft has a list of solution providers who are authorized to sell offerings, including Microsoft 365 Business Premium and Microsoft Defender for Business. If you'd prefer to work with a Microsoft partner, you can follow these steps to find a solution provider in your area:
47
+
48
+
1. Go to [Browse Partners](https://appsource.microsoft.com/en-us/marketplace/partner-dir).
49
+
50
+
2. In the **Filters** pane, specify search criteria, such as:
51
+
52
+
- Your location
53
+
- Your organization's size
54
+
-**Focus areas**, such as **Security** and/or **Threat Protection**
55
+
56
+
-**Services**, such as **Licensing** or **Managed Services (MSP)**
57
+
58
+
As soon as you select one or more criteria, the list of partners updates.
59
+
60
+
3. Review the list of results. Select a provider to learn more about their expertise and the services they provide.
61
+
44
62
## [Get Defender for Business (standalone)](#tab/getmdb)
45
63
46
64
Defender for Business provides advanced security protection for your company's devices. For more information, see [What is Microsoft Defender for Business](mdb-overview.md)?
@@ -77,24 +95,6 @@ Microsoft 365 Business Premium includes Defender for Business, Microsoft Defende
77
95
> [!IMPORTANT]
78
96
> Make sure to complete all the steps described in [Microsoft 365 Business Premium – productivity and cybersecurity for small business](/Microsoft-365/business-premium/m365bp-overview).
79
97
80
-
## [Work with a Microsoft partner](#tab/findpartner)
81
-
82
-
Microsoft has a list of solution providers who are authorized to sell offerings, including Microsoft 365 Business Premium and Microsoft Defender for Business. If you'd prefer to work with a Microsoft partner, you can follow these steps to find a solution provider in your area:
83
-
84
-
1. Go to the [Browse Partners](https://appsource.microsoft.com/en-us/marketplace/partner-dir).
85
-
86
-
2. In the **Filters** pane, specify search criteria, such as:
87
-
88
-
- Your location
89
-
- Your organization's size
90
-
-**Focus areas**, such as **Security** and/or **Threat Protection**
91
-
92
-
-**Services**, such as **Licensing** or **Managed Services (MSP)**
93
-
94
-
As soon as you select one or more criteria, the list of partners updates.
95
-
96
-
3. Review the list of results. Select a provider to learn more about their expertise and the services they provide.
97
-
98
98
---
99
99
100
100
## How to get Microsoft Defender for Business servers
@@ -113,7 +113,7 @@ Microsoft Defender for Business servers is an add-on to Defender for Business th
113
113
>
114
114
> - In order to add on Microsoft Defender for Business servers, you'll need at least one paid license for [Defender for Business](mdb-overview.md) (standalone) or [Microsoft 365 Business Premium](/Microsoft-365/business-premium/m365bp-overview).
115
115
> - There's a limit of 60 Microsoft Defender for Business servers licenses per subscription to Microsoft 365 Business Premium or Defender for Business.
116
-
> - If preferred, you could use [Microsoft Defender for Servers Plan 1 or Plan 2](/azure/defender-for-cloud/plan-defender-for-servers) instead to onboard your servers. To learn more, see [What happens if I have a mix of Microsoft endpoint security subscriptions](mdb-faq.yml#what-happens-if-i-have-a-mix-of-microsoft-endpoint-security-subscriptions)?
116
+
> - If preferred, you could use [Microsoft Defender for Servers Plan 1 or Plan 2](/azure/defender-for-cloud/plan-defender-for-servers) instead to onboard your servers.
0 commit comments