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-support-signin.md
+11-19Lines changed: 11 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.collection:
14
14
ms.topic: troubleshooting-general
15
15
ms.subservice: android
16
16
search.appverid: met150
17
-
ms.date: 03/21/2025
17
+
ms.date: 12/10/2025
18
18
appliesto:
19
19
- Microsoft Defender for Endpoint Plan 1
20
20
- Microsoft Defender for Endpoint Plan 2
@@ -129,43 +129,35 @@ The Android devices Battery Optimization screen opens automatically as part of t
129
129
130
130
5. Navigate back to Defender
131
131
132
-
**Solution 2** (needed in case the Solution 1 does not work):
132
+
**Solution 2** (needed in case the Solution 1 doesn't work):
133
133
134
-
1. Install MDE app in personal profile. (Sign-in isn't required.)
134
+
1. Install the Microsoft Defender for Endpoint app in personal profile. (Sign-in isn't required.)
135
135
2. Open the Company Portal and tap on Settings.
136
136
3. Go to the Battery Optimization section, tap on the **Turn Off** button, and then select on **Allow** to turn off Battery Optimization for the Company Portal.
137
137
4. Again, go to the Battery Optimization section and tap on the **Turn On** button. The battery saver section opens.
138
138
5. Find the Defender app and tap on it.
139
139
6. Select **No Restriction**. Go back to the Defender app in work profile and tap on **Allow** button.
140
140
7. The application shouldn't be uninstalled from personal profile for this to work.
141
141
142
-
## Unable to use banking applications with MDE app
142
+
## Unable to use certain third party applications along with the Microsoft Defender for Endpoint app (VPN)
143
143
144
-
**Applies to:**Banking apps like iMobile Pay (ICICI), PNB ONE.
144
+
**Applies to:**(Not limited) Apps handling banking, government services, or handling sensitive personal information
145
145
146
-
**Cause:**Android allows apps in the personal profile to check if there's a VPN active on the device, even outside of the personal profile. The banking app checks that and blocks it in VPN work profiles only. The banking app doesn't work with any other VPN product.
146
+
**Cause:**Some applications, such as those used for banking, government services, or handling sensitive personal information, may restrict access if a VPN is detected on your device. These restrictions are determined by the app developer as part of their implementation and even applies all VPNs *including third party) on the device. Microsoft Defender doesn't control or enforce this behavior through its settings or policies.
147
147
148
-
**Solution:**
149
-
Users need to disable MDE VPN from the Settings page. The following steps can be used:
150
-
151
-
1. Go to Settings on the mobile device.
152
-
2. Search for VPN or open 'Network and Internet' and select on VPN.
153
-
3. Select on Microsoft Defender and select Disconnect.
154
-
155
-
Users should enable VPN when they're no longer using the banking app to ensure that their devices are protected.
156
-
157
-
> [!NOTE]
158
-
> This a temporary workaround. We are working on other alternatives to provide users more control over the VPN settings from within the app.
148
+
**Workaround:**
149
+
If an app doesn't function while a VPN is enabled or present in the work profile, you might need to disable the VPN or work profile when you use the app.
150
+
Users should enable VPN when they're no longer using the app to ensure that their devices are protected.
159
151
160
152
## Send in-app feedback
161
153
162
154
If a user faces an issue, which isn't already addressed in the above sections or is unable to resolve using the listed steps, the user can provide **in-app feedback** along with **diagnostic data**. Our team can then investigate the logs to provide the right solution. Users can follow these steps to do the same:
163
155
164
-
1. Open the **MDE application** on your device and select on the **profile icon** in the top-left corner.
156
+
1. Open the **Microsoft Defender for Endpoint application** on your device and select the **profile icon** in the top-left corner.
165
157
166
158
:::image type="content" source="media/select-profile-icon-1.jpg" alt-text="The profile icon in the Microsoft Defender for Endpoint portal" lightbox="media/select-profile-icon-1.jpg":::
167
159
168
-
2. Select "Help & feedback".
160
+
2. Select **Help & feedback**.
169
161
170
162
:::image type="content" source="media/selecthelpandfeedback2.png" alt-text="The Help & feedback option that can be selected in the Microsoft Defender for Endpoint portal" lightbox="media/selecthelpandfeedback2.png":::
Copy file name to clipboardExpand all lines: defender-xdr/advanced-hunting-schema-changes.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ appliesto:
21
21
- Microsoft Defender XDR
22
22
- Microsoft Sentinel in the Microsoft Defender portal
23
23
ms.topic: reference
24
-
ms.date: 11/27/2025
24
+
ms.date: 12/10/2025
25
25
---
26
26
27
27
# Advanced hunting schema - Naming changes
@@ -38,7 +38,7 @@ Naming changes are automatically applied to queries that are saved in Microsoft
38
38
- Queries that are saved elsewhere outside Microsoft Defender XDR
39
39
40
40
## November 2025
41
-
- The Boolean field values in advanced hunting results will change from numeric (`1` and `0`) to textual (`True` and `False`) on January 25, 2026. While your queries and custom detection rules won't be affected by this change, you might want to update your automated processes (for example, scripts, playbooks, or integrations) parsing these values.
41
+
- The Boolean field values in advanced hunting results will change from numeric (`1` and `0`) to textual (`True` and `False`) on February 25, 2026. While your queries and custom detection rules won't be affected by this change, you might want to update your automated processes (for example, scripts, playbooks, or integrations) parsing these values.
42
42
43
43
44
44
- The [`AADSignInEventsBeta`](advanced-hunting-aadsignineventsbeta-table.md) and [`AADSpnSignInEventsBeta`](advanced-hunting-aadspnsignineventsbeta-table.md) tables are being replaced by [`EntraIdSignInEvents`](advanced-hunting-entraidsigninevents-table.md) and [`EntraIdSpnSignInEvents`](advanced-hunting-entraidspnsigninevents-table.md), respectively. These changes are being made to remove the former tables' preview status and to align them with the existing product branding.
0 commit comments