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-configure.md
+20-5Lines changed: 20 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,11 +110,12 @@ In the Microsoft Intune admin center, navigate to Apps > App configuration polic
110
110
> [!IMPORTANT]
111
111
> Starting May 19, 2025, alerts are no longer generated in the Microsoft Defender portal for mobile devices connecting or disconnecting to an open wireless network and for downloading/installing/deleting self-signed certificates. Instead, these activities are now generated as events and are viewable in the device timeline.
112
112
> Here are key changes about this new experience:
113
-
> - For these changes to take effect, end-users must update to the latest version of Defender for Endpoint on Android available on mid-May 2025. Otherwise, the previous experience of generating alerts will still be in place. If auto-remediation key is enabled by the admin, old alerts are resolved automatically after the changes take effect.
114
-
> - When an end-user connects or disconnects to an open wireless network multiple times within the same 24-hour period, only one event each for the connection and disconnection is generated in that 24-hour period and sent to the device timeline.
115
-
> - Enable Users to Trust Networks: After the update, connection and disconnection events to open wireless networks, including trusted networks, are sent to the device timeline as events.
116
-
> - Users allow-listed certificates: After the update, downloading/installing/deleting self-signed certificates events, including user-trusted certificates, are sent to the device timeline as events.
117
-
> - The previous experience of generating alerts for these activities still continue to apply to GCC tenants.
113
+
- For these changes to take effect, end-users must update to the latest version of Defender for Endpoint on Android available on mid-May 2025. Otherwise, the previous experience of generating alerts will still be in place. If auto-remediation key is enabled by the admin, old alerts are resolved automatically after the changes take effect.
114
+
- When an end-user connects or disconnects to an open wireless network multiple times within the same 24-hour period, only one event each for the connection and disconnection is generated in that 24-hour period and sent to the device timeline.
115
+
- Enable Users to Trust Networks: After the update, connection and disconnection events to open wireless networks, including trusted networks, are sent to the device timeline as events.
116
+
- Users allow-listed certificates: After the update, downloading/installing/deleting self-signed certificates events, including user-trusted certificates, are sent to the device timeline as events.
117
+
- The previous experience of generating alerts for these activities still continue to apply to GCC tenants.
118
+
118
119
119
120
## Privacy Controls
120
121
@@ -127,6 +128,20 @@ Following privacy controls are available for configuring the data that is sent b
127
128
|Vulnerability assessment of apps |By default only information about apps installed in the work profile is sent for vulnerability assessment. Admins can disable privacy to include personal apps|
128
129
|Network Protection | Admins can enable or disable privacy in network protection. If enabled, then Defender won't send network details.|
129
130
131
+
## Root Detection (Preview)
132
+
133
+
Microsoft Defender for Endpoint has the capability of detecting unmanaged and managed devices that are rooted. These root detection checks are done periodically. If a device is detected as rooted, these events occur:
134
+
135
+
- A high-risk alert is reported to the Microsoft Defender portal. If device Compliance and Conditional Access are set up based on device risk score, then the device is blocked from accessing corporate data.
136
+
137
+
- User data on app is cleared. When user opens the app after rooted.
138
+
139
+
The feature is enabled by default; no action is required from admin or user. Any android device running Defender version **1.0.8125.0302** (or later) will have it activated.
140
+
141
+
**Prerequisite**
142
+
143
+
- Company portal must be installed, and version must be >=5.0.6621.0
144
+
130
145
### Configure privacy alert report
131
146
132
147
Admins can now enable privacy control for the phishing report, malware report, and network report sent by Microsoft Defender for Endpoint on Android. This configuration ensures that the domain name, app details, and network details, respectively, aren't sent as part of the alert whenever a corresponding threat is detected.
Copy file name to clipboardExpand all lines: defender-endpoint/android-whatsnew.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,20 @@ Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.](
29
29
30
30
### Releases for Defender for Endpoint on Android
31
31
32
+
#### October 2025
33
+
34
+
| Build| 1.0.8201.0101|
35
+
| -------- | -------- |
36
+
| Release Date | October 2, 2025 |
37
+
38
+
**What's New**
39
+
40
+
- Improved UX experience for the onboarding screens, for more details please visit this link - [UX Enhancement](/defender-endpoint/android-new-ux)
41
+
42
+
- Global Secure Access Kerberos SSO support on Android (GA): Kerberos SSO experience for users on Android devices with Global Secure Access is now supported. User will need to install and configure a 3rd party SSO client.
Copy file name to clipboardExpand all lines: defender-endpoint/ios-whatsnew.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,18 @@ Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.](
30
30
31
31
## Releases for Defender for Endpoint on iOS
32
32
33
+
#### October 2025
34
+
35
+
| Build | 1.1.69250104|
36
+
| -------- | -------- |
37
+
| Release Date | October 7, 2025 |
38
+
39
+
**What's New**
40
+
41
+
- Global Secure Access Kerberos SSO support on iOS (Preview): Kerberos SSO experience for users on iOS devices with Global Secure Access is now supported. On iOS, to create and deploy profile, refer - [Single sign-on app extension](/intune/intune-service/configuration/ios-device-features-settings).
Copy file name to clipboardExpand all lines: defender-endpoint/linux-preferences.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
---
1
+
---
2
2
title: Configure security settings in Microsoft Defender for Endpoint on Linux
3
3
ms.reviewer: gopkr, ardeshmukh
4
4
description: Describes how to configure Microsoft Defender for Endpoint on Linux in enterprises.
@@ -581,10 +581,8 @@ Specify the maximum number of entries to keep in the scan history. Entries inclu
581
581
582
582
### Exclusion setting preferences
583
583
584
-
**Exclusion setting preferences are currently in preview**.
585
-
586
584
> [!NOTE]
587
-
> Global exclusions are currently in public preview, and are available in Defender for Endpoint beginning with version `101.23092.0012` or later in the Insiders Slow and Production rings.
585
+
> Global exclusions are available in Defender for Endpoint beginning with version `101.24092.0001` or above.
588
586
589
587
The `exclusionSettings` section of the configuration profile is used to configure various exclusions for Microsoft Defender for Endpoint for Linux.
Copy file name to clipboardExpand all lines: defender-for-cloud-apps/governance-discovery.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,24 @@
1
1
---
2
2
title: Govern discovered apps
3
3
description: This article describes the procedure for governing your discovered apps by blocking their usage in your organization.
4
-
ms.date: 01/29/2023
4
+
ms.date: 09/30/2025
5
5
ms.topic: how-to
6
6
ms.reviewer: Mravela
7
7
---
8
8
9
9
# Govern discovered apps
10
10
11
11
12
-
13
12
After you review the list of discovered apps in your environment, you can secure your environment by approving safe apps (**Sanctioned**) or prohibiting unwanted apps (**Unsanctioned**) in the following ways.
14
13
14
+
## Prerequisites
15
+
16
+
Before you can block discovered cloud apps, you must meet the following requirements:
17
+
18
+
-[Turn on **Cloud Protection** in Microsoft Defender for Endpoint](/defender-endpoint/enable-cloud-protection-microsoft-defender-antivirus)
19
+
-[Turn on **Network Protection** in Microsoft Defender for Endpoint.](/defender-endpoint/network-protection#required-browser-configuration)
20
+
- Install the **Microsoft Defender Browser Protection** add-on across all non-Microsoft browsers in your organization.
21
+
15
22
## Sanctioning/unsanctioning an app
16
23
17
24
You can mark a specific risky app as unsanctioned by clicking the three dots at the end of the row. Then select **Unsanctioned**. Unsanctioning an app doesn't block use, but enables you to more easily monitor its use with the cloud discovery filters. You can then notify users of the unsanctioned app and suggest an alternative safe app for their use, or [generate a block script using the Defender for Cloud Apps APIs](api-discovery-script.md) to block all unsanctioned apps.
Copy file name to clipboardExpand all lines: defender-for-cloud-apps/troubleshooting-proxy-end-users.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -217,6 +217,14 @@ This message only appears for Chrome users, as Microsoft Edge users benefit from
217
217
218
218
If you receive a message like this, contact Microsoft’s support to address it with the relevant browser vendor.
219
219
220
+
## Users encounter Entra ID Login after clicking mcas.ms links
221
+
Attackers can craft URLs that appear to lead to trusted domains but actually redirect users to malicious sites. For users protected by the session/suffix-based solution, an attacker might attempt to bypass controls by appending the mcas.ms suffix to a malicious URL, exploiting the assumption that such URLs are safe.
222
+
223
+
To mitigate this, Microsoft Defender for Cloud Apps redirects any mcas.ms URL lacking valid session context to Entra ID for authentication, effectively blocking such exploits.
224
+
225
+
However, legitimate mcas.ms URLs without context can exist, for example, if a user clicks on an old browser bookmark. In such cases, the user will first be redirected to Entra ID. If their identity provider (IdP) is not Entra ID, they will need to manually remove the mcas.ms suffix to proceed.
226
+
227
+
220
228
## More considerations for troubleshooting apps
221
229
222
230
When troubleshooting apps, there are some more things to consider:
Copy file name to clipboardExpand all lines: defender-for-identity/deploy/prerequisites-sensor-version-3.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,13 +70,13 @@ Applying the **Unified Sensor RPC Audit** tag enables a new, tested capability o
70
70
**Steps to apply the configuration:**
71
71
72
72
1. In the **Microsoft Defender portal**, navigate to: **System > Settings > Microsoft Defender XDR > Asset Rule Management**.
73
-
1. Create a new rule.
73
+
1.Select **Create a new rule**
74
74
75
75

76
76
77
77
3. In the side panel:
78
78
79
-
1.Select a **name**for the rule.
79
+
1.Enter a **Rule name**and **Description**.
80
80
81
81
1. Set **rule conditions** using `Device name`, `Domain`, or `Device tag` to target the desired machines.
82
82
@@ -88,9 +88,15 @@ Applying the **Unified Sensor RPC Audit** tag enables a new, tested capability o
88
88
89
89

90
90
91
-
5.Click**Submit** to save the rule.
91
+
5.Select**Next** to review and finish creating the rule and then select **Submit**.
92
92
93
-
Offboarding a device from this configuration can be done by **deleting the asset rule** or **modifying the rule conditions** so the device no longer matches.
93
+
### Updating rules
94
+
Offboarding a device from this configuration can be done **only** from **deleting the asset rule** or **modifying the rule conditions** so the device no longer matches.
95
+
96
+
>[!NOTE]
97
+
> It may take up to 1 hour for changes to be reflected in the portal.
98
+
99
+
Learn more about Asset Management Rule [here](/defender-xdr/configure-asset-rules)
Copy file name to clipboardExpand all lines: defender-office-365/air-auto-remediation.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
@@ -48,7 +48,7 @@ After you select the cluster types to automatically remediate, the selected reme
48
48
49
49
Use the following steps to select the cluster types to automatically remediate:
50
50
51
-
In the Microsoft Defender portal at <https://security.microsoft.com>, go to **Settings**\>**Email & collaboration**\>**MDO automation settings**.
51
+
In the Microsoft Defender portal at <https://security.microsoft.com>, go to **Settings**\>**Email & collaboration**\>**MDO automation settings**. Or, to go directly to the **Automation settings** page, use <https://security.microsoft.com/securitysettings/mdoAutomationSettings>.
52
52
53
53
The following settings are available on the **Automation settings** page:
0 commit comments