Skip to content

Commit 6ab4257

Browse files
authored
Merge branch 'main' into docs-editor/mde-linux-prerequisites-1765336118
2 parents 9a1cf7e + 7fc19db commit 6ab4257

File tree

128 files changed

+259
-254
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

128 files changed

+259
-254
lines changed

defender-endpoint/android-support-signin.md

Lines changed: 11 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
ms.topic: troubleshooting-general
1515
ms.subservice: android
1616
search.appverid: met150
17-
ms.date: 03/21/2025
17+
ms.date: 12/10/2025
1818
appliesto:
1919
- Microsoft Defender for Endpoint Plan 1
2020
- Microsoft Defender for Endpoint Plan 2
@@ -129,43 +129,35 @@ The Android devices Battery Optimization screen opens automatically as part of t
129129

130130
5. Navigate back to Defender
131131

132-
**Solution 2** (needed in case the Solution 1 does not work):
132+
**Solution 2** (needed in case the Solution 1 doesn't work):
133133

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.)
135135
2. Open the Company Portal and tap on Settings.
136136
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.
137137
4. Again, go to the Battery Optimization section and tap on the **Turn On** button. The battery saver section opens.
138138
5. Find the Defender app and tap on it.
139139
6. Select **No Restriction**. Go back to the Defender app in work profile and tap on **Allow** button.
140140
7. The application shouldn't be uninstalled from personal profile for this to work.
141141

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)
143143

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
145145

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.
147147

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.
159151

160152
## Send in-app feedback
161153

162154
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:
163155

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.
165157

166158
:::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":::
167159

168-
2. Select "Help & feedback".
160+
2. Select **Help & feedback**.
169161

170162
:::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":::
171163

defender-for-cloud-apps/app-governance-app-policies-create.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,7 @@ The following table lists the app governance templates supported to generate ale
5353

5454
|Template name|Description|
5555
|---|---|
56+
|**Unused app**|Find apps that have not authenticated recently. This policy checks the following conditions: <ul><li>Last used: More than 90 days (customizable)</li></ul>|
5657
|**New app with high data usage**|Find newly registered apps that have uploaded or downloaded large amounts of data using Microsoft Graph and EWS APIs. This policy checks the following conditions: <ul><li>Registration age: Seven days or less (customizable)</li><li>Data usage: Greater than 1 GB in one day (customizable)</li></ul>|
5758
|**Increase in users**|Find apps with a sizable increase in the number of users. This policy checks the following conditions: <ul><li>Time range: Last 90 days</li><li>Increase in consenting users: At least 50% (customizable)</li></ul>|
5859

@@ -78,7 +79,7 @@ The following table lists the app governance templates supported to generate ale
7879

7980
Use a custom app policy when you need to do something not already done by one of the built-in templates.
8081

81-
- To create a new custom app policy, first select **Create new policy** on the **Policies** page. On the **Choose App policy template page**, select the **Custom** category, the **Custom policy** template, and then select **Next**.
82+
1. To create a new custom app policy, first select **Create new policy** on the **Policies** page. On the **Choose App policy template page**, select the **Custom** category, the **Custom policy** template, and then select **Next**.
8283

8384
1. On the **Name and description** page, configure the following settings:
8485
- Policy Name
@@ -125,6 +126,7 @@ Use a custom app policy when you need to do something not already done by one of
125126
|**Sensitivity labels accessed**|Select one or more sensitivity labels from the list|Apps that accessed data with specific sensitivity labels in the last 30 days.||
126127
|**Services accessed** (Graph only)|Exchange and/or OneDrive and/or SharePoint and/or Teams|Apps that have accessed OneDrive, SharePoint, or Exchange Online using Microsoft Graph and EWS APIs|Multiple selections allowed.|
127128
|**Error rate** (Graph only)|Error rate is greater than X% in the last seven days|Apps whose Graph API error rates in the last seven days are greater than a specified percentage||
129+
|**Last used**|Within last X days|Apps that have not authenticated within a specified period from the current date||
128130
|**App origin**|External or Internal|Apps that originated within the tenant or registered in an external tenant||
129131

130132
All of the specified conditions must be met for this app policy to generate an alert.
@@ -176,9 +178,9 @@ Policies for OAuth apps trigger alerts only on policies that are authorized by u
176178
177179
3. You might want to set the policy based on the group memberships of the users who authorized the apps. For example, an admin can decide to set a policy that revokes uncommon apps if they ask for high permissions, only if the user who authorized the permissions is a member of the Administrators group.
178180

179-
For example:
180-
181-
![new OAuth app policy.](media/app-permissions-policy.png)
181+
For example:
182+
183+
![new OAuth app policy.](media/app-permissions-policy.png)
182184

183185
### Anomaly detection policies for OAuth apps connected to Salesforce and Google Workspace
184186

@@ -188,7 +190,6 @@ This section is only relevant for Salesforce and Google Workspace applications.
188190

189191
> [!NOTE]
190192
> Anomaly detection policies are only available for OAuth apps that are authorized in your Microsoft Entra ID.
191-
>
192193
> The severity of OAuth app anomaly detection policies can't be modified.
193194
194195
The following table describes the out-of-the-box anomaly detection policies provided by Defender for Cloud Apps:

defender-for-cloud-apps/app-governance-secure-apps-app-hygiene-features.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.reviewer: anandd512
1010
# Secure apps with app hygiene features
1111

1212
> [!NOTE]
13-
> Management of unused apps, unused credentials, and expiring credentials will only be available to app governance customers with Microsoft Entra Workload ID Premium. For more information, see [What are workload identities?](/azure/active-directory/workload-identities/workload-identities-overview)
13+
> Management of unused credentials and expiring credentials is available to app governance customers with a Microsoft Entra Workload ID Premium license. For more information, see [What are workload identities?](/azure/active-directory/workload-identities/workload-identities-overview)
1414
1515
Have you ever wanted to see the apps that your organization owns but isn't using, but didn't know how to? Or clean up unused or expiring credentials more easily? Microsoft Entra ID includes recommendations to help you identify such apps, and the **App governance** page in Microsoft Defender provides an app hygiene feature suite that includes controls and insights on unused apps, unused credentials, and expiring credentials.
1616

defender-for-cloud-apps/app-governance-trial-user-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Start by using the following steps to get visibility and insights about your app
3434
> You can also view app governance-related recommendations in [Secure Score](https://security.microsoft.com/securescore?viewid=overview&tid=b5304409-74ae-42bf-a3e3-d62da4845129) to help you holistically manage your posture.
3535
>
3636
37-
1. **[View your apps](app-governance-visibility-insights-view-apps.md)**: Sort the data on the **App governance** tabs by apps with high data usage or number of consents given, or filter by high privileged apps, apps with unused permissions, or unverified publisher, and more.
37+
1. **[View your apps](app-governance-visibility-insights-view-apps.md)**: Sort the data on the **App governance** tabs by apps with high data usage or number of consents given, or filter by high privileged apps, unused apps, apps with unused permissions, or unverified publisher, and more.
3838

3939
Use these sorting and filtering options to gain deeper insights into your OAuth apps, including relevant app metadata and usage data.
4040

defender-for-cloud-apps/app-governance-visibility-insights-compliance-posture.md

Lines changed: 10 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -14,16 +14,14 @@ The **Overview** page shows the following details:
1414

1515
|Apps / incidents |Details shown | Use this data to... |
1616
|---------|---------|---------|
17-
|**OAuth-enabled apps that use the Microsoft Graph API** | - How many apps are in your tenant <br>- How many apps might be overprivileged <br>- How many apps are highly privileged | Determine the level of risk to your organization by overprivileged and highly privileged apps. |
18-
|**For incidents** | - How many active incidents your tenant has <br>- How many are based on app governance detections (**Threat incidents**) <br>- How many are based on app policies you have in place (**Policy incidents**) <br>- The 10 latest incidents | Determine how quickly incidents are being generated and the relative number of detected and policy-based incidents. |
17+
|**OAuth-enabled apps that use the Microsoft Graph API** | - How many apps are in your tenant <br> - How many apps are unused in the last 90 days <br> - How many apps might be overprivileged <br> - How many apps are highly privileged | Determine the level of risk to your organization by unused, overprivileged and highly privileged apps. |
18+
|**For incidents** | - How many active incidents your tenant has <br>- How many are based on app governance detections (**Threat incidents**) <br> - How many are based on app policies you have in place (**Policy incidents**) <br>- The 10 latest incidents | Determine how quickly incidents are being generated and the relative number of detected and policy-based incidents. |
1919

2020
For example:
2121

22-
> [!div class="mx-imgBorder"]
23-
> ![Relative number of detected and policy-based incidents.](media/incidents-summary1.png)
24-
>
25-
> [!div class="mx-imgBorder"]
26-
> ![top alerts.](media/app-governance-visibility-insights-compliance-posture/top-alerts.png)
22+
:::image type="content" source="media/incidents-summary1.png" alt-text="Screenshot showing relative number of detected and policy-based incidents.":::
23+
24+
:::image type="content" source="media/app-governance-visibility-insights-compliance-posture/top-alerts.png" alt-text="Screenshot showing top alerts.":::
2725

2826
## Data usage cards
2927

@@ -35,17 +33,15 @@ Data usage cards show the following types of information:
3533

3634
For example:
3735

38-
> [!div class="mx-imgBorder"]
39-
> ![Total data accessed by apps.](media/app-governance-visibility-insights-compliance-posture/data-usage-chart.png)
36+
:::image type="content" source="media/app-governance-visibility-insights-compliance-posture/data-usage-chart.png" alt-text="Screenshot showing total data accessed by apps.":::
4037

4138
## Apps that access data on Microsoft 365
4239

4340
For apps that access data on Microsoft 365, cards show the number of apps that have accessed data on SharePoint, OneDrive, Exchange Online, or Teams using Microsoft Graph and EWS APIs in the last 30 days.
4441

4542
For example:
4643

47-
> [!div class="mx-imgBorder"]
48-
> ![Apps that have accessed data on SharePoint, OneDrive, Exchange Online, or Teams in the last 30 days.](media/app-governance-visibility-insights-compliance-posture/apps-accessed-m365-services-chart.png)
44+
:::image type="content" source="media/app-governance-visibility-insights-compliance-posture/apps-accessed-m365-services-chart.png" alt-text="Screenshot showing apps that have accessed data on SharePoint, OneDrive, Exchange Online, or Teams in the last 30 days.":::
4945

5046
## Sensitivity labels accessed
5147

@@ -54,8 +50,9 @@ For sensitivity labeling data, cards show the number apps that have accessed con
5450
For example:
5551

5652
The number of apps that have accessed content with sensitivity labels.
57-
> :::image type="content" source="media/sensitive-data-accessed-chart1.png" alt-text="Number of apps that have accessed content with sensitivity labels.":::
53+
54+
:::image type="content" source="media/sensitive-data-accessed-chart1.png" alt-text="Screenshot showing the number of apps that have accessed content with sensitivity labels.":::
5855

5956
## Next steps
6057

61-
[Get insights on and regulate access to sensitive content](app-governance-visibility-insights-sensitive-content.md)
58+
[Get insights on and regulate access to sensitive content](app-governance-visibility-insights-sensitive-content.md)

defender-for-cloud-apps/app-governance-visibility-insights-get-started.md

Lines changed: 17 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The dashboard on the **Overview** tab contains a summary of your app ecosystem:
2828
|**Apps that accessed data across Microsoft 365 services** | The count of apps that have accessed data with and without sensitivity labels on SharePoint, OneDrive, Exchange Online, and Teams in the last 30 days. <br><br>For example, in the screenshot above, 99 apps accessed OneDrive in the last 30 days, out of which 27 apps accessed data with sensitivity labels. |
2929
|**Sensitivity labels accessed** | Count of apps that accessed labeled data across SharePoint, OneDrive, Exchange Online, and Teams in the last 30 days, sorted by the count. <br><br>For example, in the screenshot above, 90 apps accessed confidential data on SharePoint, OneDrive, Exchange Online, and Teams. |
3030
|**Predefined policies** | Count of active and total predefined policies that identify risky apps, such as apps with excessive privileges, unusual characteristics, or suspicious activities. |
31-
|**App categories** | The top apps sorted by these categories: <br><br>- **All categories**: Sorts across all available categories.<br> - **Highly privileged**: High privilege is an internally determined category based on platform machine learning and signals.<br> - **Overprivileged**: When app governance receives data that indicates that a permission granted to an application hasn't been used in the last 90 days, that application is overprivileged. App governance must be operating for at least 90 days to determine if any app is overprivileged. <br>- **Unverified publisher**: Applications that haven't received [publisher certification](/azure/active-directory/develop/publisher-verification-overview) are considered unverified.<br> - **App only permissions**: [Application permissions](/azure/active-directory/develop/v2-permissions-and-consent#permission-types) are used by apps that can run without a signed-in user present. Apps with permissions to access data across the tenant are potentially a higher risk.<br>- **New apps**: New apps that have been registered in the last seven days. |
31+
|**App categories** | The top apps sorted by these categories: <br><br>- **All categories**: Sorts across all available categories.<br> - **Highly privileged**: High privilege is an internally determined category based on platform machine learning and signals.<br> - **Overprivileged**: When app governance receives data that indicates that a permission granted to an application hasn't been used in the last 90 days, that application is overprivileged. App governance must be operating for at least 90 days to determine if any app is overprivileged.<br> - **Unused**: Apps that have not signed in within the last 90 days <br>- **Unverified publisher**: Applications that haven't received [publisher certification](/azure/active-directory/develop/publisher-verification-overview) are considered unverified.<br> - **App only permissions**: [Application permissions](/azure/active-directory/develop/v2-permissions-and-consent#permission-types) are used by apps that can run without a signed-in user present. Apps with permissions to access data across the tenant are potentially a higher risk.<br>- **New apps**: New apps that have been registered in the last seven days. |
3232

3333
## View app insights
3434

@@ -56,25 +56,28 @@ One of the primary value points for app governance is the ability to quickly vie
5656

5757
- **Publisher verified**
5858

59-
Use one of the following nondefault filters to further customize the apps listed:
60-
61-
- **Last modified**
59+
- **Last used**
6260

63-
- **Added on**
61+
- **Services accessed**
6462

65-
- **Certification**
63+
- **Sensitivity labels accessed**
6664

65+
Use one of the following nondefault filters to further customize the apps listed:
66+
67+
- **Last modified**
68+
69+
- **Added on**
70+
71+
- **Certification**
72+
6773
- **Users**
68-
69-
- **Services accessed**
70-
74+
7175
- **Data usage**
72-
73-
- **Sensitivity labels accessed**
76+
77+
> [!TIP]
78+
> Save the query to save the currently selected filters for use again in the future.
79+
7480

75-
> [!TIP]
76-
> Save the query to save the currently selected filters for use again in the future.
77-
7881
1. Select the name of an app to view more details. For example:
7982

8083
:::image type="content" source="media/app-governance-visibility-insights-get-started/app-governance-app-list-view.png" alt-text="Screenshot of the app details pan showing an app summary." lightbox="media/app-governance-visibility-insights-get-started/app-governance-app-list-view.png":::

defender-for-cloud-apps/app-governance-visibility-insights-overview.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ App governance provides access to the following data:
2424

2525
- Data accessed and permissions used by all apps with workload and user level insights.
2626

27-
- App information and metadata, such as Graph API and legacy permissions, registration date, and certification.
27+
- App information and metadata, such as Graph API and legacy permissions, registration date, last used date and certification.
2828

2929
- Publisher information and metadata, such as name and verification status.
3030

@@ -36,6 +36,8 @@ App governance provides access to the following data:
3636

3737
- High-privileged apps.
3838
- Overprivileged apps.
39+
- Unused apps.
40+
3941
- High-usage apps.
4042
- Top consented users whose data a specific app can access.
4143
- Priority accounts who have data that a specific app can access.

0 commit comments

Comments
 (0)