Skip to content

Commit 39c9c2e

Browse files
authored
Merge pull request #3261 from MicrosoftDocs/main
Published main to live, Monday 10:30 AM PDT, 03/24
2 parents a9f6dc4 + 21e28f0 commit 39c9c2e

13 files changed

+36
-50
lines changed

ATPDocs/architecture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Microsoft Defender for Identity monitors your domain controllers by capturing an
1212

1313
The following image shows how Defender for Identity is layered over Microsoft Defender XDR, and works together with other Microsoft services and third-party identity providers to monitor traffic coming in from domain controllers and Active Directory servers.
1414

15-
:::image type="content" source="media/architecture/architecture.png" alt-text="Diagram of the Defender for Identity architecture." border="false":::
15+
:::image type="content" source="media\diagram-of-the-defender-for-identity-architecture.png" alt-text="Diagram of the Defender for Identity architecture." border="false":::
1616

1717
Installed directly on your domain controller, Active Directory Federation Services (AD FS), or Active Directory Certificate Services (AD CS) servers, the Defender for Identity sensor accesses the event logs it requires directly from the servers. After the logs and network traffic are parsed by the sensor, Defender for Identity sends only the parsed information to the Defender for Identity cloud service.
1818

ATPDocs/investigate-assets.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,9 +63,10 @@ When you investigate a specific identity, you'll see the following details on an
6363
|[Remediation actions](/microsoft-365/security/defender/investigate-users#remediation-actions) | Respond to compromised users by disabling their accounts or resetting their password. After taking action on users, you can check on the activity details in the Microsoft Defender XDR **Action center.|
6464

6565
> [!NOTE]
66-
> **Investigation Priority Score** has been deprecated on December 3, 2025. As a result, both the Investigation Priority Score breakdown and the scored activity timeline cards have been removed from the UI.
66+
> **Investigation Priority Score** has been deprecated on December 3, 2024. As a result, both the Investigation Priority Score breakdown and the scored activity timeline cards have been removed from the UI.
67+
68+
6769

68-
6970
For more information, see [Investigate users](/microsoft-365/security/defender/investigate-users) in the Microsoft Defender XDR documentation.
7071

7172
## Investigation steps for suspicious groups
305 KB
Loading

ATPDocs/whats-new.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,10 @@ For updates about versions and features released six months ago or earlier, see
2424

2525
## March 2025
2626

27+
### New Health Issue
28+
29+
New [health issue](health-alerts.md#network-configuration-mismatch-for-sensors-running-on-vmware) for cases where sensors running on VMware have network configuration mismatch.
30+
2731
### Enhanced Identity Inventory (Preview)
2832

2933
The Identities page under *Assets* has been updated to provide better visibility and management of identities across your environment.

defender-endpoint/android-intune.md

Lines changed: 11 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.custom: partner-contribution
1515
ms.topic: conceptual
1616
ms.subservice: android
1717
search.appverid: met150
18-
ms.date: 03/21/2025
18+
ms.date: 03/24/2025
1919
---
2020

2121
# Deploy Microsoft Defender for Endpoint on Android with Microsoft Intune
@@ -95,7 +95,7 @@ For more information on the enrollment options supported by Microsoft Intune, se
9595

9696
## Add Microsoft Defender for Endpoint on Android as a Managed Google Play app
9797

98-
Follow the steps below to add Microsoft Defender for Endpoint app into your managed Google Play Store.
98+
To add the Microsoft Defender for Endpoint app into your managed Google Play Store, follow these steps:
9999

100100
1. In [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) , go to **Apps** \> **Android Apps** \> **Add** and select **Managed Google Play app**.
101101

@@ -105,33 +105,17 @@ Follow the steps below to add Microsoft Defender for Endpoint app into your mana
105105

106106
:::image type="content" source="media/0f79cb37900b57c3e2bb0effad1c19cb.png" alt-text="The Managed Google Play page in the Microsoft Intune admin center portal" lightbox="media/0f79cb37900b57c3e2bb0effad1c19cb.png":::
107107

108-
3. In the **App description** page, you should be able to see app details about the Defender for Endpoint app. Review the information on the page, and then select **Approve**.
108+
3. In the **App description** page, you should be able to see app details about the Defender for Endpoint app. Review the information on the page, tap **Select** to select the app, and then select **Sync** at the top of the blade to sync the app.
109109

110-
:::image type="content" source="media/07e6d4119f265037e3b80a20a73b856f.png" alt-text="The page of Managed Google Play in the Microsoft Intune admin center portal" lightbox="media/07e6d4119f265037e3b80a20a73b856f.png":::
111-
112-
4. When you're prompted to approve permissions for Defender for Endpoint obtains, review the information, and then select **Approve**.
113-
114-
:::image type="content" source="media/206b3d954f06cc58b3466fb7a0bd9f74.png" alt-text="The permissions approval page in the Microsoft Defender portal" lightbox="media/206b3d954f06cc58b3466fb7a0bd9f74.png":::
115-
116-
5. On the **Approval settings** page, review your preference to handle new app permissions that Defender for Endpoint on Android might ask. Review the choices, and then select your preferred option. Then, select **Done**.
117-
118-
By default, managed Google Play selects **Keep approved when app requests new permissions**.
119-
120-
:::image type="content" source="media/ffecfdda1c4df14148f1526c22cc0236.png" alt-text=" The approval settings configuration completion page in the in the Microsoft Defender portal" lightbox="media/ffecfdda1c4df14148f1526c22cc0236.png":::
121-
122-
6. After the permissions handling selection is made, select **Sync** to sync Microsoft Defender for Endpoint to your apps list.
123-
124-
:::image type="content" source="media/34e6b9a0dae125d085c84593140180ed.png" alt-text="The Sync pane in the Microsoft Defender portal" lightbox="media/34e6b9a0dae125d085c84593140180ed.png":::
110+
:::image type="content" source="media/app-description-page.png" alt-text="Screenshot of the Microsoft Defender app page in the store." lightbox="media/app-description-page.png":::
125111

126112
The sync completes in a few minutes.
127113

128-
:::image type="content" source="media/9fc07ffc150171f169dc6e57fe6f1c74.png" alt-text="The application sync status pane in the Android apps page in the Microsoft Defender portal" lightbox="media/9fc07ffc150171f169dc6e57fe6f1c74.png":::
129-
130-
7. Select the **Refresh** button in the Android apps screen. Microsoft Defender for Endpoint should be visible in the apps list.
114+
4. Select the **Refresh** button in the Android apps screen. Microsoft Defender for Endpoint should be visible in the apps list.
131115

132-
:::image type="content" source="media/fa4ac18a6333335db3775630b8e6b353.png" alt-text="The page displaying the synced application" lightbox="media/fa4ac18a6333335db3775630b8e6b353.png":::
116+
:::image type="content" source="media/fa4ac18a6333335db3775630b8e6b353.png" alt-text="Screenshot showing the Microsoft Defender for Endpoint app in a list." lightbox="media/fa4ac18a6333335db3775630b8e6b353.png":::
133117

134-
8. Defender for Endpoint supports app configuration policies for managed devices using Microsoft Intune. This capability can be used to select different configurations for Defender for Endpoint.
118+
5. Defender for Endpoint supports app configuration policies for managed devices using Microsoft Intune. This capability can be used to select different configurations for Defender for Endpoint.
135119

136120
1. In the **Apps** page, go to **Policy** > **App configuration policies** > **Add** > **Managed devices**.
137121

@@ -154,7 +138,7 @@ Follow the steps below to add Microsoft Defender for Endpoint app into your mana
154138
- **Auto grant** - Automatically approves without notifying the user.
155139
- **Auto deny** - Automatically denies without notifying the user.
156140

157-
5. Go to the **Configuration settings** section, and choose **Use configuration designer**.
141+
5. Go to the **Configuration settings** section, and then choose **Use configuration designer**.
158142

159143
:::image type="content" alt-text="Image of android create app configuration policy." source="media/configurationformat.png" lightbox="media/configurationformat.png":::
160144

@@ -174,15 +158,15 @@ Follow the steps below to add Microsoft Defender for Endpoint app into your mana
174158

175159
The app configuration policy for Defender for Endpoint is now assigned to the selected user group.
176160

177-
9. Select **Microsoft Defender** app in the list \> **Properties** \> **Assignments** \> **Edit**.
161+
6. Select **Microsoft Defender** app in the list \> **Properties** \> **Assignments** \> **Edit**.
178162

179163
:::image type="content" source="media/mda-properties.png" alt-text="The Edit option on the Properties page" lightbox="media/mda-properties.png":::
180164

181-
10. Assign the app as a required app to a user group. It's automatically installed in the work profile during the next sync of the device via Company Portal app. Navigate to the **Required** section, select **Add group**, select the appropriate user group, and then choose **Select**.
165+
7. Assign the app as a required app to a user group. It's automatically installed in the work profile during the next sync of the device via Company Portal app. Navigate to the **Required** section, select **Add group**, select the appropriate user group, and then choose **Select**.
182166

183167
:::image type="content" source="media/ea06643280075f16265a596fb9a96042.png" alt-text="The Edit application page" lightbox="media/ea06643280075f16265a596fb9a96042.png":::
184168

185-
11. In the **Edit Application** page, review all the information that was specified earlier. Select **Review + Save**, and then select **Save** to commence assignment.
169+
8. In the **Edit Application** page, review all the information that was specified earlier. Select **Review + Save**, and then select **Save** to commence assignment.
186170

187171
### Auto setup of always-on VPN
188172

defender-endpoint/configure-machines-onboarding.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.collection:
1313
ms.topic: conceptual
1414
ms.subservice: onboard
1515
search.appverid: met150
16-
ms.date: 12/18/2023
16+
ms.date: 03/24/2025
1717
---
1818

1919
# Get devices onboarded to Microsoft Defender for Endpoint
@@ -50,7 +50,7 @@ The **Onboarding** card provides a high-level overview of your onboarding rate b
5050
5151
## Onboard more devices with Intune profiles
5252

53-
Defender for Endpoint provides several convenient options for [onboarding Windows devices](onboard-configure.md). For Intune-managed devices, however, you can leverage Intune profiles to conveniently deploy the Defender for Endpoint sensor to select devices, effectively onboarding these devices to the service.
53+
Defender for Endpoint provides several convenient options for [onboarding Windows devices](onboarding.md). For Intune-managed devices, however, you can leverage Intune profiles to conveniently deploy the Defender for Endpoint sensor to select devices, effectively onboarding these devices to the service.
5454

5555
From the **Onboarding** card, select **Onboard more devices** to create and assign a profile on Intune. The link takes you to the device compliance page on Intune, which provides a similar overview of your onboarding state.
5656

-60.9 KB
Binary file not shown.
462 KB
Loading

defender-endpoint/microsoft-defender-endpoint-mac.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: macos
1717
search.appverid: met150
18-
ms.date: 10/15/2024
18+
ms.date: 03/24/2025
1919
---
2020

2121
# Microsoft Defender for Endpoint on Mac
@@ -24,9 +24,8 @@ ms.date: 10/15/2024
2424

2525
**Applies to:**
2626
- [Microsoft Defender XDR](/defender-xdr)
27-
- [Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
27+
- [Microsoft Defender for Endpoint Plan 1 and Plan 2](microsoft-defender-endpoint.md)
2828
- [Microsoft Defender for Business](https://www.microsoft.com/security/business/endpoint-security/microsoft-defender-business)
29-
- [Microsoft Defender for Endpoint Plan 1](microsoft-defender-endpoint.md)
3029
- [Microsoft Defender for Individuals](https://www.microsoft.com/microsoft-365/microsoft-defender-for-individuals)
3130

3231
> Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.](https://go.microsoft.com/fwlink/p/?linkid=2225630)
@@ -159,8 +158,8 @@ Starting with macOS 11 (Big Sur), Microsoft Defender for Endpoint has been fully
159158

160159
## Resources
161160

162-
- For more information about logging, uninstalling, or other articles, see [Resources for Microsoft Defender for Endpoint on Mac](mac-resources.md).
163-
- [Privacy for Microsoft Defender for Endpoint on Mac](mac-privacy.md).
161+
- For more information about logging, uninstalling, or other articles, see [Resources for Microsoft Defender for Endpoint on macOS](mac-resources.md).
162+
- [Privacy for Microsoft Defender for Endpoint on macOS](mac-privacy.md).
164163
- [Turn on Network protection for macOS](network-protection-macos.md)
165164

166165
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

defender-endpoint/mobile-resources-defender-endpoint.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@ ms.collection:
1414
ms.topic: conceptual
1515
ms.subservice: ngp
1616
search.appverid: met150
17-
ms.date: 10/18/2024
17+
ms.date: 03/24/2025
1818
---
1919
# Resources for Microsoft Defender for Endpoint for mobile devices
2020

21-
Microsoft Defender for Endpoint provides multiple capabilities on mobile devices. Some of these capabilities are set to default, and some require admin configuration. The following table shows how to configure the resources related to Microsoft Defender for Endpoint on Android and iOS.
21+
Microsoft Defender for Endpoint provides multiple capabilities on mobile devices. Some of these capabilities are set to default, and some require administrator configuration. The following table shows how to configure the resources related to Microsoft Defender for Endpoint on Android and iOS.
2222

2323
## Feature configurations
2424

@@ -61,23 +61,21 @@ Suspicious certificates |Informational| | |
6161

6262
[Complete privacy information for iOS](ios-privacy.md)
6363

64-
## Microsoft Defender Mobile App exclusion from Conditional Access(CA) Policies
64+
## Microsoft Defender mobile app exclusion from Conditional Access (CA) Policies
6565

66-
Microsoft Defender Mobile app is a security app that needs to constantly be running in the background to report the device security posture. This security posture is used in the Compliance and App Protection policies to secure the managed apps and ensure that corporate data is accessed only in a secured device. However, with restrictive Conditional Access policies such as having Block policies based on certain locations, or enforcing frequent sign ins can result in Defender blocked from reporting posture. If the Defender app fails to report the device posture this can lead to situation where the device is under a threat, leading to vulnerability of corporate data on the device. To ensure seamless protection, we recommend excluding the Defender app from the blocking Conditional Access Policy.
66+
The Microsoft Defender mobile app is a security app that needs to constantly be running in the background to report the device security posture. This security posture is used in the Compliance and App Protection policies to secure the managed apps and ensure that corporate data is accessed only in a secured device. However, with restrictive Conditional Access policies such as having Block policies based on certain locations, or enforcing frequent sign ins can result in Defender blocked from reporting posture. If the Defender app fails to report the device posture this can lead to situation where the device is under a threat, leading to vulnerability of corporate data on the device. To ensure seamless protection, we recommend excluding the Defender app from the blocking Conditional Access Policy.
6767

6868
### Apps required to exclude
6969

70-
1. **Xplat Broker App ( a0e84e36-b067-4d5c-ab4a-3db38e598ae2)**
71-
Xplat Broker App is the application responsible for forwarding Defender risk signals to the Defender backend. However, the presence of restrictive CA policies can result in Defender blocked from reporting signals. In these scenarios, we recommend excluding the Xplat Broker App. Note, that **Xplat Broker App** is also used by other platforms like Mac and Linux. So if the policy is same for these platforms, it is better to create a separate Conditional Access policy for Mobile.
70+
1. **MicrosoftDefenderATP XPlat app (a0e84e36-b067-4d5c-ab4a-3db38e598ae2)**: MicrosoftDefenderATP XPlat app is the application responsible for forwarding Defender risk signals to the Defender backend. However, the presence of restrictive CA policies can result in Defender blocked from reporting signals. In these scenarios, we recommend excluding the MicrosoftDefenderATP XPlat app. Note, that **MicrosoftDefenderATP XPlat app** is also used by other platforms like Mac and Linux. So if the policy is same for these platforms, it is better to create a separate Conditional Access policy for Mobile.
7271

73-
2. **TVM app (e724aa31-0f56-4018-b8be-f8cb82ca1196)**
74-
Microsoft Defender for Mobile TVM (Threat and Vulnerability Management) is the service, which provides the vulnerability assessment for the installed apps on the iOS devices. However, the presence of restrictive CA policies can result in Defender blocked from communicating the onboarding requests to the TVM backend services. This service should be excluded if MDVM (Vulnerability Assessment) is used in the organization.
72+
2. **Microsoft Defender for Mobile TVM app (e724aa31-0f56-4018-b8be-f8cb82ca1196)**: Microsoft Defender for Mobile TVM (Threat and Vulnerability Management) is the service, which provides the vulnerability assessment for the installed apps on the iOS devices. However, the presence of restrictive CA policies can result in Defender blocked from communicating the onboarding requests to the TVM backend services. This service should be excluded if MDVM (Vulnerability Assessment) is used in the organization.
7573

7674
### Steps to exclude
7775

7876
1. Create service principal for the apps that needs to be excluded. [Steps to create service principal.](/graph/api/serviceprincipal-post-serviceprincipals?view=graph-rest-1.0&tabs=powershell#request&preserve-view=true).
7977

80-
1. While creating the service principal object above, use these app IDs: **Xplat Broker App ( a0e84e36-b067-4d5c-ab4a-3db38e598ae2), TVM app (e724aa31-0f56-4018-b8be-f8cb82ca1196)**.
78+
1. While creating the service principal object above, use these app IDs: **MicrosoftDefenderATP XPlat app (a0e84e36-b067-4d5c-ab4a-3db38e598ae2), Microsoft Defender for Mobile TVM app (e724aa31-0f56-4018-b8be-f8cb82ca1196)**.
8179

8280
1. After the object is successfully created the two apps are visible in the CA screen and can be excluded.
8381

0 commit comments

Comments
 (0)