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
+17-12Lines changed: 17 additions & 12 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](quick-installation-guide.md).
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
@@ -88,12 +88,16 @@ Activate the Defender for Identity from the [Microsoft Defender portal](https://
88
88
89
89
The Activation page lists servers discovered in Device Inventory and identified as eligible domain controllers.
90
90
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.
91
+
1. 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
+
:::image type="content" source="media/activate-capabilities/1.jpg" lightbox="media/activate-capabilities/1.jpg" alt-text="Screenshot that shows how to activate the new sensor.":::
92
94
93
95
> [!NOTE]
94
96
> 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
97
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.
98
+
1. 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.
99
+
100
+
:::image type="content" source="media/activate-capabilities/2.jpg" lightbox="media/activate-capabilities/2.jpg" alt-text="Screenshot that shows how to seethe onboarded servers.":::
97
101
98
102
## Onboarding Confirmation
99
103
@@ -104,7 +108,7 @@ To confirm the sensor has been onboarded:
104
108
2. Check that the onboarded domain controller is listed.
105
109
106
110
> [!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.
111
+
> 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.
108
112
109
113
## Test activated capabilities
110
114
@@ -126,7 +130,6 @@ In the Defender portal, select **Identities** > **Dashboard**, and review the de
126
130
127
131
For more information, see [Work with Defender for Identity's ITDR dashboard](../dashboard.md).
128
132
129
-
130
133
### Confirm entity page details
131
134
132
135
Confirm that entities, such as domain controllers, users, and groups, are populated as expected.
@@ -139,7 +142,7 @@ In the Defender portal, check for the following details:
139
142
140
143
-**Group entities**: Use the global search to find a user group, or pivot from a user or device details page where group details are shown. Check for details of group membership, view group users, and group timeline data.
141
144
142
-
If no event data is found on the group timeline, you may need to create some manually. For example, do this by adding and removing users from the group in Active Directory.
145
+
If no event data is found on the group timeline, you may need to create some manually. For example, do this by adding and removing users from the group in Active Directory.
143
146
144
147
For more information, see [Investigate assets](../investigate-assets.md).
145
148
@@ -205,18 +208,20 @@ Test remediation actions on a test user. For example:
205
208
206
209
1. In the Defender portal, go to the user details page for a test user.
207
210
208
-
1. From the **Options** menu, select any of the available remediation actions.
211
+
2. From the **Options** menu, select any of the available remediation actions.
209
212
210
-
1. Check Active Directory for the expected activity.
213
+
3. Check Active Directory for the expected activity.
211
214
212
215
For more information, see [Remediation actions in Microsoft Defender for Identity](../remediation-actions.md).
213
216
214
217
## Deactivate Defender for Identity capabilities on your domain controller
215
218
216
219
If you want to deactivate Defender for Identity capabilities on your domain controller, delete it from the **Sensors** page:
217
220
218
-
1. In the Defender portal, select **Settings > Identities > Sensors**.
219
-
1. Select the domain controller where you want to deactivate Defender for Identity capabilities, select **Delete**, and confirm your selection.
221
+
1. In the Defender portal, select **Settings** > **Identities** > **Sensors**.
222
+
2. Select the domain controller where you want to deactivate Defender for Identity capabilities, select **Delete**, and confirm your selection.
223
+
224
+
:::image type="content" source="media/activate-capabilities/3.jpg" lightbox="media/activate-capabilities/3.jpg" alt-text="Screenshot that shows how to deactivate a server.":::
220
225
221
226
Deactivating Defender for Identity capabilities from your domain controller doesn't remove the domain controller from Defender for Endpoint. For more information, see [Defender for Endpoint documentation](/microsoft-365/security/defender-endpoint/).
Copy file name to clipboardExpand all lines: ATPDocs/health-alerts.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
@@ -39,6 +39,12 @@ This section describes all the health issues for each component, listing the cau
39
39
40
40
Sensor-specific health issues are displayed in the **Sensor health issues** tab and domain related or aggregated health issues are displayed in the **Global health issues** tab as detailed in the following tables:
41
41
42
+
### Network configuration mismatch for sensors running on VMware
|The virtual machines that the listed Defender for Identity sensors are installed on has a network configuration mismatch. This issue may affect the performance and reliability of the sensors.|Review the network interface settings, including disabling the Large Send Offload (LSO), and follow the instructions in [here](https://aka.ms/mdi/vmware-sensor-issue).|High|Sensors health issues tab|
47
+
42
48
### A domain controller is unreachable by a sensor
# For more information, see https://review.learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata?branch=main
4
+
# For valid values of ms.service, ms.prod, and ms.topic, see https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies?branch=main
5
+
6
+
title: Identity inventory
7
+
description: The Identity Inventory provides a centralized location for customers to view and manage identity information across their environment, ensuring optimal visibility and a comprehensive experience. The updated Identities Inventory page, located under Assets in Defender XDR portal
8
+
author: LiorShapiraa # GitHub alias
9
+
ms.author: liorshapira
10
+
ms.service: microsoft-defender-for-identity
11
+
ms.topic: article
12
+
ms.date: 03/13/2025
13
+
---
14
+
15
+
# Identity inventory
16
+
17
+
__Applies to:__
18
+
19
+
-[Microsoft Defender for Identity](https://aka.ms/aatp/docs)
20
+
21
+
-[Microsoft Defender for Cloud Apps](/defender-cloud-apps/)
22
+
23
+
-[Microsoft Defender XDR](/defender-xdr)
24
+
25
+
The __Identity inventory__ provides a centralized view of all identities in your organization, enabling you to monitor and manage them efficiently. At a glance, you can see key details such as Domain, Tags, Type, and other attributes, helping you quickly identify and manage identities that require attention.
26
+
27
+
The Identities inventory page includes the following tabs:
28
+
29
+
-**Identities**: A consolidated view of identities across Active Directory, Entra ID. This Identities tab highlights key details, including identity types, and user's information.
30
+
31
+
-**Cloud application accounts:** Displays a list of cloud application accounts, including those from application connectors and third-party sources (original available in the previous version based on Microsoft Defender for Cloud Apps). Learn more about [Cloud application accounts from connected apps.](/defender-cloud-apps/accounts)
32
+
33
+
There are several options you can choose from to customize the identities list view. On the top navigation you can:
34
+
35
+
- Add or remove columns.
36
+
37
+
- Apply filters.
38
+
39
+
- Search for an identity by name or full UPN, Sid and Object ID.
40
+
41
+
- Export the list to a CSV file.
42
+
43
+
- Copy list link with the included filters configured.
44
+
45
+
## 
46
+
47
+
### Identity details
48
+
49
+
The **Identities** list offers a consolidated view of identities across Active Directory and Entra ID. It highlights key details, including the following columns by default:
50
+
51
+
-__Display name__ – The full name of the identity as shown in the directory.
52
+
53
+
-__SID__ – The Security Identifier, a unique value used to identify the identity in Active Directory.
54
+
55
+
-__Domain__ – The Active Directory domain to which the identity belongs.
56
+
57
+
-__Object ID__ – A unique identifier for the identity in Entra ID.
58
+
59
+
-__Source__ – Indicates whether the identity is on-premises (originate from Active Directory), Cloud only (Entra ID) or Hybrid (synced from AD to Entra ID).
60
+
61
+
-__Type__ – Specifies if the identity is a user account or service account.
62
+
63
+
-__UPN (User Principal Name)__ – The unique login name of the identity in an email-like format.
64
+
65
+
-__Tags__ – Custom labels that help categorize or classify identities: Sensitive and Honeytoken.
66
+
67
+
-__Created time__ – The timestamp when the identity was first created.
68
+
69
+
-__Criticality level__ – Indicates the critical level of the identity.
70
+
71
+
-__Account status__ – Shows whether the identity is enabled or disabled.
72
+
73
+
-__Last updated__ – The timestamp of the most recent update to the identity's attributes in Active Directory.
74
+
75
+
Non-default columns: Email and Entra ID risk level.
76
+
77
+
> [!TIP]
78
+
> To see all columns, you likely need to do one or more of the following steps:
79
+
> - Horizontally scroll in your web browser.
80
+
> - Narrow the width of appropriate columns.
81
+
> - Zoom out in your web browser.
82
+
83
+
### Sort and filter the Identities list
84
+
85
+
You can apply the following filters to limit the list of identities and get a more focused view:
86
+
87
+
- Domain
88
+
89
+
- Type
90
+
91
+
- Source
92
+
93
+
- Tags
94
+
95
+
- Criticality level
96
+
97
+
- Account status
98
+
99
+
Sort option applies to Display name, Domain and Created time columns.
100
+
101
+
### Identity inventory insights
102
+
103
+
- The __Classify critical assets__ card allows you to define identity groups as business critical. For more information, see [Microsoft Security Exposure Management](/security-exposure-management/microsoft-security-exposure-management).
104
+
105
+
-**Highly privileged identities** card helps you investigate in Advanced hunting all sensitive accounts in your organization, including Entra ID security administrators and Global admin users.
106
+
107
+
-**Critical Active Directory service accounts** card helps you quickly identify all Active Directory accounts designated as critical, making it easier to focus on identities most at risk.
108
+
109
+
At the top of each device inventory tab, the following device counts are available:
110
+
111
+
-__Total__: The total number of identities.
112
+
113
+
-__Critical:__ The number of your critical assets.
114
+
115
+
-**Disabled:** The number of all disabled identities in your organization.
116
+
117
+
-**Services:** The number of all service accounts both on-premises and cloud.
118
+
119
+
You can use this information to help you prioritize devices for security posture improvements.
120
+
121
+
### Navigate to the Identity inventory page
122
+
123
+
Use relative links instead of absolute links.
124
+
In the Defender XDR portal at [https://security.microsoft.com](https://security.microsoft.com), go to Assets > Identities. Or, to navigate directly to the [identity inventory](/defender-for-identity/identity-inventory) page.
0 commit comments