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: defender-endpoint/android-intune.md
+24-24Lines changed: 24 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ Defender for Endpoint on Android supports Android Enterprise enrolled devices.
93
93
94
94
For more information on the enrollment options supported by Microsoft Intune, see [Enrollment Options](/mem/intune/enrollment/android-enroll).
95
95
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.**
97
97
98
98
## Add Microsoft Defender for Endpoint on Android as a Managed Google Play app
99
99
@@ -280,11 +280,11 @@ Android low touch onboarding is disabled by default. Admins can enable it throug
280
280
281
281
6. Under **Configuration settings**, select `Use Configuration designer`, and then select **Add**.
282
282
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
-
>
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`.
287
284
285
+
> [!div class="mx-imgBorder"]
286
+
> 
287
+
288
288
8. Assign the policy to the target user group.
289
289
290
290
9. Review and create the policy.
@@ -297,29 +297,29 @@ Admins can go to the [Microsoft Endpoint Management admin center](https://intune
297
297
298
298
1. Go to **Apps> App configuration policies** and click on **Add**. Select **Managed Devices**.
299
299
300
-
> [!div class="mx-imgBorder"]
301
-
> 
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
-
> 
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
-
> 
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
+
> 
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'**.
314
304
315
-
> [!div class="mx-imgBorder"]
316
-
> 
305
+
> [!div class="mx-imgBorder"]
306
+
> 
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'**.
317
309
318
-
5.**Assign** the configuration policy to a group of users. **Review and create** the policy.
310
+
> [!div class="mx-imgBorder"]
311
+
> 
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**.
319
314
320
-
> [!div class="mx-imgBorder"]
321
-
> 
315
+
> [!div class="mx-imgBorder"]
316
+
> 
317
+
318
+
1.**Assign** the configuration policy to a group of users. **Review and create** the policy.
322
319
320
+
> [!div class="mx-imgBorder"]
321
+
> 
322
+
323
323
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).
324
324
325
325
Organizations can communicate to their users to protect Personal profile with Microsoft Defender on their enrolled BYOD devices.
Copy file name to clipboardExpand all lines: defender-endpoint/configure-proxy-internet.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,7 @@ Configure the static proxy using the Group Policy available in Administrative Te
132
132
>
133
133
> 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.
134
134
>
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.
136
136
>
137
137
> You can use PowerShell with the `Set-MpPreference` cmdlet to configure these options:
Copy file name to clipboardExpand all lines: defender-endpoint/device-control-overview.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Get an overview of device control, including removable storage acce
4
4
author: siosulli
5
5
ms.author: siosulli
6
6
manager: deniseb
7
-
ms.date: 08/27/2024
7
+
ms.date: 08/28/2024
8
8
ms.topic: overview
9
9
ms.service: defender-endpoint
10
10
ms.subservice: asr
@@ -57,7 +57,6 @@ Device control capabilities from Microsoft can be organized into three main cate
57
57
58
58
-**Device control in Defender for Endpoint**. Device control in Defender for Endpoint provides more advanced capabilities and is cross platform.
59
59
- 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.
61
60
- Reporting and advanced hunting - complete visibility into add device related activities.
62
61
- Device control in Microsoft Defender can be managed using Intune or [Group Policy](device-control-deploy-manage-gpo.md).
63
62
-**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).
Copy file name to clipboardExpand all lines: defender-endpoint/threat-analytics.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -211,6 +211,8 @@ When looking at the threat analytics data, remember the following factors:
211
211
- 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.
212
212
- The recommended actions don’t guarantee complete resilience and only reflect the best possible actions needed to improve it.
213
213
- 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*.
Copy file name to clipboardExpand all lines: defender-for-iot/prerequisites.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Before you start, you need:
27
27
28
28
- A Microsoft 365 E5/ Defender for Endpoint Plan 2/ E5 security license.
29
29
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).
- ✅ <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,
120
120
121
121
- 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:
122
122
-**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:
124
124
- The message isn't identified as malware or high confidence phishing (malware and high confidence phishing messages are quarantined).
125
125
- 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).
126
126
- 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.
Copy file name to clipboardExpand all lines: defender-xdr/threat-analytics.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -209,7 +209,8 @@ When looking at the threat analytics data, remember the following factors:
209
209
- 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.
210
210
- The recommended actions don’t guarantee complete resilience and only reflect the best possible actions needed to improve it.
211
211
- 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*.
0 commit comments