Skip to content

Commit d793d0e

Browse files
committed
Merge branch 'main' into v-smandalika-8894710
2 parents c4bc668 + 5881b0f commit d793d0e

File tree

8 files changed

+39
-36
lines changed

8 files changed

+39
-36
lines changed

defender-endpoint/android-intune.md

Lines changed: 24 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ Defender for Endpoint on Android supports Android Enterprise enrolled devices.
9393

9494
For more information on the enrollment options supported by Microsoft Intune, see [Enrollment Options](/mem/intune/enrollment/android-enroll).
9595

96-
**Currently, personally owned devices using a work profile and corporate-owned, fully managed user device enrollments are supported for deployment.**
96+
**Currently, Personally-owned devices with work profile, Corporate-owned devices with work profile, and Corporate-owned fully managed user device enrollments are supported in Android Enterprise.**
9797

9898
## Add Microsoft Defender for Endpoint on Android as a Managed Google Play app
9999

@@ -280,11 +280,11 @@ Android low touch onboarding is disabled by default. Admins can enable it throug
280280

281281
6. Under **Configuration settings**, select `Use Configuration designer`, and then select **Add**.
282282

283-
7. Select **Low touch onboarding and User UPN**. For User UPN, change the value type to `Variable`, and set the configuration value to `User Principal Name`. Enable low-touch onboarding by changing its configuration value to `1`.
284-
285-
>[!div class="mx-imgBorder"]
286-
>![Screenshot showing a low touch onboarding configuration policy.](media/low-touch-user-upn.png)
283+
1. Select **Low touch onboarding and User UPN**. For User UPN, change the value type to `Variable`, and set the configuration value to `User Principal Name`. Enable low-touch onboarding by changing its configuration value to `1`.
287284

285+
> [!div class="mx-imgBorder"]
286+
> ![Screenshot showing a low touch onboarding configuration policy.](media/low-touch-user-upn.png)
287+
288288
8. Assign the policy to the target user group.
289289

290290
9. Review and create the policy.
@@ -297,29 +297,29 @@ Admins can go to the [Microsoft Endpoint Management admin center](https://intune
297297

298298
1. Go to **Apps> App configuration policies** and click on **Add**. Select **Managed Devices**.
299299

300-
> [!div class="mx-imgBorder"]
301-
> ![Image of adding app configuration policy.](media/addpolicy.png)
302-
303-
2. Enter **Name** and **Description** to uniquely identify the configuration policy. Select platform as **'Android Enterprise'**, Profile type as **'Personally-owned work profile only'** and Targeted app as **'Microsoft Defender'**.
304-
305-
> [!div class="mx-imgBorder"]
306-
> ![Image of naming configuration policy.](media/selectapp.png)
307-
308-
3. On the settings page, in **'Configuration settings format'**, select **'Use configuration designer'** and click on **Add**. From the list of configurations that are displayed, select **'Microsoft Defender in Personal profile'**.
309-
310-
> [!div class="mx-imgBorder"]
311-
> ![Image of configuring personal profile.](media/addconfiguration.png)
312-
313-
4. The selected configuration will be listed. Change the **configuration value to 1** to enable Microsoft Defender support personal profiles. A notification will appear informing the admin about the same. Click on **Next**.
300+
> [!div class="mx-imgBorder"]
301+
> ![Image of adding app configuration policy.](media/addpolicy.png)
302+
303+
1. Enter **Name** and **Description** to uniquely identify the configuration policy. Select platform as **'Android Enterprise'**, Profile type as **'Personally-owned work profile only'** and Targeted app as **'Microsoft Defender'**.
314304

315-
> [!div class="mx-imgBorder"]
316-
> ![Image of changing config value.](media/changeconfigvalue.png)
305+
> [!div class="mx-imgBorder"]
306+
> ![Image of naming configuration policy.](media/selectapp.png)
307+
308+
1. On the settings page, in **'Configuration settings format'**, select **'Use configuration designer'** and click on **Add**. From the list of configurations that are displayed, select **'Microsoft Defender in Personal profile'**.
317309

318-
5. **Assign** the configuration policy to a group of users. **Review and create** the policy.
310+
> [!div class="mx-imgBorder"]
311+
> ![Image of configuring personal profile.](media/addconfiguration.png)
312+
313+
1. The selected configuration will be listed. Change the **configuration value to 1** to enable Microsoft Defender support personal profiles. A notification will appear informing the admin about the same. Click on **Next**.
319314

320-
> [!div class="mx-imgBorder"]
321-
> ![Image of reviewing and creating policy.](media/savepolicy.png)
315+
> [!div class="mx-imgBorder"]
316+
> ![Image of changing config value.](media/changeconfigvalue.png)
317+
318+
1. **Assign** the configuration policy to a group of users. **Review and create** the policy.
322319

320+
> [!div class="mx-imgBorder"]
321+
> ![Image of reviewing and creating policy.](media/savepolicy.png)
322+
323323
Admins also can set up **privacy controls** from the Microsoft Intune admin center to control what data can be sent by the Defender mobile client to the security portal. For more information, see [configuring privacy controls](android-configure.md).
324324

325325
Organizations can communicate to their users to protect Personal profile with Microsoft Defender on their enrolled BYOD devices.

defender-endpoint/configure-proxy-internet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ Configure the static proxy using the Group Policy available in Administrative Te
132132
>
133133
> For resiliency purposes and the real-time nature of cloud-delivered protection, Microsoft Defender Antivirus caches the last known working proxy. Ensure your proxy solution does not perform SSL inspection, as that breaks the secure cloud connection.
134134
>
135-
> Microsoft Defender Antivirus doesn't use the static proxy to connect to Windows Update or Microsoft Update for downloading updates. Instead, it uses a system-wide proxy if configured to use Windows Update, or the configured internal update source according to the [configured fallback order](manage-protection-updates-microsoft-defender-antivirus.md). If necessary, you can use **Administrative Templates > Windows Components > Microsoft Defender Antivirus > Define proxy auto-config (.pac)** for connecting to the network. If you need to set up advanced configurations with multiple proxies, use **Administrative Templates > Windows Components > Microsoft Defender Antivirus > Define addresses** to bypass proxy server and prevent Microsoft Defender Antivirus from using a proxy server for those destinations.
135+
> Microsoft Defender Antivirus doesn't use the static proxy to connect to Windows Update or Microsoft Update for downloading updates. Instead, it uses a system-wide proxy if configured to use Windows Update, or the configured internal update source according to the [configured fallback order](manage-protection-updates-microsoft-defender-antivirus.md). If necessary, you can use **Administrative Templates > Windows Components > Microsoft Defender Antivirus > Define proxy auto-config (.pac)** for connecting to the network. If you need to set up advanced configurations with multiple proxies, use **Administrative Templates > Windows Components > Microsoft Defender Antivirus > Define addresses to bypass proxy server** and prevent Microsoft Defender Antivirus from using a proxy server for those destinations.
136136
>
137137
> You can use PowerShell with the `Set-MpPreference` cmdlet to configure these options:
138138
> - `ProxyBypass`

defender-endpoint/device-control-overview.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Get an overview of device control, including removable storage acce
44
author: siosulli
55
ms.author: siosulli
66
manager: deniseb
7-
ms.date: 08/27/2024
7+
ms.date: 08/28/2024
88
ms.topic: overview
99
ms.service: defender-endpoint
1010
ms.subservice: asr
@@ -57,7 +57,6 @@ Device control capabilities from Microsoft can be organized into three main cate
5757

5858
- **Device control in Defender for Endpoint**. Device control in Defender for Endpoint provides more advanced capabilities and is cross platform.
5959
- Granular access control - create policies to control access by device, device type, operation (read, write, execute), user group, network location, or file type.
60-
- File evidence - store the file information and contents to audit files copied or accessed on devices.
6160
- Reporting and advanced hunting - complete visibility into add device related activities.
6261
- Device control in Microsoft Defender can be managed using Intune or [Group Policy](device-control-deploy-manage-gpo.md).
6362
- **Device control in Microsoft Defender and Intune**. Intune provides a rich experience for managing complex device control policies for organizations. You can configure and deploy device restriction settings in Defender for Endpoint, for example. See [Deploy and manage device control with Microsoft Intune](device-control-deploy-manage-intune.md).

defender-endpoint/linux-preferences.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: defender-endpoint
66
ms.author: dansimp
77
author: dansimp
88
ms.localizationpriority: medium
9-
ms.date: 07/31/2024
9+
ms.date: 08/28/2024
1010
manager: deniseb
1111
audience: ITPro
1212
ms.collection:
@@ -63,12 +63,13 @@ Specifies the enforcement preference of antivirus engine. There are three values
6363
- Real-time (`real_time`): Real-time protection (scan files as they're modified) is enabled.
6464
- On-demand (`on_demand`): Files are scanned only on demand. In this:
6565
- Real-time protection is turned off.
66-
- Passive (`passive`): Runs the antivirus engine in passive mode. In this:
66+
- Passive (`passive`): Runs the antivirus engine in passive mode. In this case, all of the following apply:
6767
- Real-time protection is turned off: Threats are not remediated by Microsoft Defender Antivirus.
6868
- On-demand scanning is turned on: Still use the scan capabilities on the endpoint.
69-
- Automatic threat remediation is turned off: No files will be moved and security admin is expected to take required action.
70-
- Security intelligence updates are turned on: Alerts will be available on security admins tenant.
71-
69+
- Automatic threat remediation is turned off: No files are moved and your security administrator is expected to take required action.
70+
- Security intelligence updates are turned on: Alerts are available in the security administrator's tenant.
71+
- Definition updates occur only when a scan starts, even if `automaticDefinitionUpdateEnabled` is set to `true` in passive mode.
72+
7273
|Description|JSON Value|Defender Portal Value|
7374
|---|---|---|
7475
|**Key**|enforcementLevel|Enforcement Level|

defender-endpoint/threat-analytics.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -211,6 +211,8 @@ When looking at the threat analytics data, remember the following factors:
211211
- The checklist in the **Recommended actions** tab only displays recommendations tracked in [Microsoft Secure Score](/defender-xdr/microsoft-secure-score). Check the **Analyst report** tab for more recommended actions that aren't tracked in Secure Score.
212212
- The recommended actions don’t guarantee complete resilience and only reflect the best possible actions needed to improve it.
213213
- Antivirus-related statistics are based on Microsoft Defender Antivirus settings.
214+
- The **Misconfigured devices** column in the main Threat analytics page shows the number of devices affected by a threat when the threat's related recommended actions aren't turned on. However, if Microsoft researchers don't link any recommended actions, the **Misconfigured devices** column shows the status *Not available*.
215+
- The **Vulnerable devices** column in the main Threat analytics page shows the number of devices running software that are vulnerable to any of the vulnerabilities linked to the threat. However, if Microsoft researchers don't link any vulnerabilities, the **Vulnerable devices** column shows the status *Not available*.
214216

215217
## See also
216218

defender-for-iot/prerequisites.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Before you start, you need:
2727

2828
- A Microsoft 365 E5/ Defender for Endpoint Plan 2/ E5 security license.
2929

30-
- Microsoft Defender for Endpoint agents deployed in your environment. For more information, see [onboard Microsoft Defender for Endpoint](/defender-endpoint/onboarding)
30+
- Microsoft Defender for Endpoint agents deployed in your environment. For more information, see [onboard Microsoft Defender for Endpoint](/defender-endpoint/onboarding).
3131

3232
## Prerequisites for setting up a site
3333

defender-office-365/create-safe-sender-lists-in-office-365.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.custom:
1818
- seo-marvel-apr2020
1919
description: Admins can learn about the available and preferred options to allow inbound messages in Exchange Online Protection (EOP).
2020
ms.service: defender-office-365
21-
ms.date: 06/10/2024
21+
ms.date: 08/27/2024
2222
appliesto:
2323
- ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Exchange Online Protection</a>
2424
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 1 and Plan 2</a>
@@ -120,7 +120,7 @@ When messages skip spam filtering due to entries in a user's Safe Senders list,
120120

121121
- In Exchange Online, whether entries in the Safe Senders list work or don't work depends on the verdict and action in the policy that identified the message:
122122
- **Move messages to Junk Email folder**: Domain entries and sender email address entries are honored. Messages from those senders aren't moved to the Junk Email folder.
123-
- **Quarantine**: Domain entries aren't honored (messages from those senders are quarantined). Email address entries are honored (messages from those senders aren't quarantined) if either of the following statements are true:
123+
- **Quarantine**: Domain entries and email address entries are honored (messages from those senders aren't quarantined) if either of the following statements are true:
124124
- The message isn't identified as malware or high confidence phishing (malware and high confidence phishing messages are quarantined).
125125
- The email address isn't also in a block entry in the [Tenant Allow/Block List](tenant-allow-block-list-email-spoof-configure.md#create-block-entries-for-domains-and-email-addresses).
126126
- Entries for blocked senders and blocked domains are honored (messages from those senders are moved to the Junk Email folder). Safe mailing list settings are ignored.

defender-xdr/threat-analytics.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,8 @@ When looking at the threat analytics data, remember the following factors:
209209
- The checklist in the **Recommended actions** tab only displays recommendations tracked in [Microsoft Secure Score](microsoft-secure-score.md). Check the **Analyst report** tab for more recommended actions that aren't tracked in Secure Score.
210210
- The recommended actions don’t guarantee complete resilience and only reflect the best possible actions needed to improve it.
211211
- Antivirus-related statistics are based on Microsoft Defender Antivirus settings.
212-
212+
- The **Misconfigured devices** column in the main Threat analytics page shows the number of devices affected by a threat when the threat's related recommended actions aren't turned on. However, if Microsoft researchers don't link any recommended actions, the **Misconfigured devices** column shows the status *Not available*.
213+
- The **Vulnerable devices** column in the main Threat analytics page shows the number of devices running software that are vulnerable to any of the vulnerabilities linked to the threat. However, if Microsoft researchers don't link any vulnerabilities, the **Vulnerable devices** column shows the status *Not available*.
213214

214215
## See also
215216

0 commit comments

Comments
 (0)