Skip to content

Commit c450490

Browse files
authored
Merge pull request #1682 from MicrosoftDocs/diannegali-updatetroubleshoot
updated troubleshoot page
2 parents 937c44c + 50f0896 commit c450490

File tree

5 files changed

+111
-153
lines changed

5 files changed

+111
-153
lines changed

.openpublishing.redirection.defender.json

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,6 +109,16 @@
109109
"source_path": "defender-endpoint/defender-endpoint-demonstration-amsi.md",
110110
"redirect_url": "/defender-endpoint/mde-demonstration-amsi",
111111
"redirect_document_id": true
112-
}
112+
},
113+
{
114+
"source_path": "defender-xdr/tickets.md",
115+
"redirect_url": "/defender-xdr/troubleshoot",
116+
"redirect_document_id": true
117+
},
118+
{
119+
"source_path": "defender-xdr/portal-submission-troubleshooting.md",
120+
"redirect_url": "/defender-xdr/troubleshoot",
121+
"redirect_document_id": false
122+
}
113123
]
114124
}

defender-xdr/TOC.yml

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -549,18 +549,14 @@
549549
href: configure-email-notifications.md
550550
- name: Set time zone
551551
href: m365d-time-zone.md
552-
- name: Troubleshoot service issues
553-
href: troubleshoot.md
554552
- name: Set up dynamic rules for devices
555553
href: configure-asset-rules.md
556554
- name: Provide feedback
557555
href: feedback.md
558556
- name: Provide managed service provider (MSSP) access
559557
href: mssp-access.md
560-
- name: Create ServiceNow tickets and tasks
561-
items:
562-
- name: ServiceNow integration overview
563-
href: ./tickets.md
558+
- name: Troubleshoot service issues
559+
href: troubleshoot.md
564560
- name: Microsoft Defender XDR APIs
565561
items:
566562
- name: Overview
@@ -627,8 +623,6 @@
627623
href: /defender-endpoint/technological-partners
628624
- name: Professional services supported by Microsoft Defender XDR
629625
href: /defender-endpoint/professional-services
630-
- name: Understand threat intelligence concepts
631-
href: /defender-endpoint/threat-indicator-concepts
632626
- name: Bi-directional connector for Microsoft Sentinel
633627
href: microsoft-365-defender-integration-with-azure-sentinel.md
634628
- name: Resources
@@ -641,8 +635,8 @@
641635
href: criteria.md
642636
- name: Submit files for analysis
643637
href: submission-guide.md
644-
- name: Troubleshoot MSI portal errors caused by admin block
645-
href: portal-submission-troubleshooting.md
638+
- name: Understand threat intelligence concepts
639+
href: /defender-endpoint/threat-indicator-concepts
646640
- name: Microsoft virus initiative
647641
href: virus-initiative-criteria.md
648642
- name: Software developer FAQ

defender-xdr/portal-submission-troubleshooting.md

Lines changed: 0 additions & 99 deletions
This file was deleted.

defender-xdr/tickets.md

Lines changed: 0 additions & 34 deletions
This file was deleted.

defender-xdr/troubleshoot.md

Lines changed: 96 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: Troubleshoot Microsoft Defender XDR service issues
3-
description: Find solutions and workarounds to known Microsoft Defender XDR issues.
3+
description: Find and solve known Microsoft Defender XDR issues and use workarounds to resolve blocks while using the service.
44
ms.service: defender-xdr
55
f1.keywords:
66
- NOCSH
77
ms.author: macapara
8-
author: mjcaparas
8+
author: diannegali
99
ms.localizationpriority: medium
1010
manager: dansimp
1111
audience: ITPro
@@ -16,18 +16,16 @@ ms.topic: conceptual
1616
search.appverid:
1717
- MOE150
1818
- MET150
19-
ms.date: 03/28/2024
19+
ms.date: 10/23/2024
20+
appliesto:
21+
- Microsoft Defender XDR
2022
---
2123

2224
# Troubleshoot Microsoft Defender XDR service issues
2325

2426
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
2527

26-
27-
**Applies to:**
28-
- Microsoft Defender XDR
29-
30-
This section addresses issues that might arise as you use the Microsoft Defender XDR service.
28+
This article addresses issues that might arise as you use the Microsoft Defender XDR service. It provides solutions and workarounds to help you resolve these issues. If you encounter a problem that isn't addressed here, contact [Microsoft Support](https://support.microsoft.com/contactus).
3129

3230
<a name='i-dont-see-microsoft-365-defender-content'></a>
3331

@@ -45,11 +43,100 @@ If you have Microsoft Defender for Identity deployed in your environment but you
4543

4644
For more information, see [Microsoft Defender for Identity integration](/cloud-app-security/mdi-integration).
4745

48-
## Where is the settings page for turning on the service?
46+
## How do I turn on Microsoft Defender XDR??
4947

5048
To turn on Microsoft Defender XDR, access **Settings** from the navigation pane in the Microsoft Defender portal. This navigation item is visible only if you have the [prerequisite permissions and licenses](m365d-enable.md#check-license-eligibility-and-required-permissions).
5149

5250
## How do I create an exception for my file/URL?
5351

5452
A false positive is a file or URL that is detected as malicious but isn't a threat. You can create indicators and define exclusions to unblock and allow certain files/URLs. See [Address false positives/negatives in Defender for Endpoint](/defender-endpoint/defender-endpoint-false-positives-negatives).
53+
54+
## How can I integrate ServiceNow tickets into the Microsoft Defender portal?
55+
56+
The Microsoft Defender XDR-ServiceNow connector is no longer available in the Microsoft Defender portal. However, you can still integrate Microsoft Defender XDR with ServiceNow by using the Microsoft Security Graph API. For more information, see [Security solution integrations using the Microsoft Graph Security API](/graph/security-integration).
57+
58+
The Microsoft Defender XDR-ServiceNow integration was previously available in the Microsoft Defender portal for preview and feedback. This integration allowed you to create ServiceNow incidents from Microsoft Defender XDR incidents.
59+
60+
## Why can't I submit files?
61+
62+
In some instances, an administrator block might cause submission issues when you try to submit a potentially infected file to the [Microsoft Security intelligence website](https://www.microsoft.com/wdsi) for analysis. The following process shows how to resolve this problem.
63+
64+
### Review your settings
65+
66+
Open your Azure [Enterprise application settings](https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/UserSettings/menuId/). Under **Enterprise Applications** > **Users can consent to apps accessing company data on their behalf**, check whether Yes or No is selected.
67+
68+
- If **No** is selected, a Microsoft Entra administrator for the customer tenant needs to provide consent for the organization. Depending on the configuration with Microsoft Entra ID, users might be able to submit a request right from the same dialog box. If there's no option to ask for admin consent, users need to request for these permissions to be added to their Microsoft Entra admin. Go to the following section for more information.
69+
70+
- If **Yes** is selected, ensure the Windows Defender Security Intelligence app setting **Enabled for users to sign in?** is set to **Yes** [in Azure](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Properties/appId/f0cf43e5-8a9b-451c-b2d5-7285c785684d/objectId/4a918a14-4069-4108-9b7d-76486212d75d). If **No** is selected, you need to request a Microsoft Entra admin enable it.
71+
72+
### Implement required Enterprise Application permissions
73+
74+
> [!IMPORTANT]
75+
> Microsoft recommends that you use roles with the fewest permissions. This helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
76+
77+
This process requires a Global Administrator or Application Administrator in the tenant.
78+
79+
1. Open [Enterprise Application settings](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Permissions/appId/f0cf43e5-8a9b-451c-b2d5-7285c785684d/objectId/4a918a14-4069-4108-9b7d-76486212d75d).
80+
81+
2. Select **Grant admin consent for organization**.
82+
83+
3. If you're able to do so, review the API permissions required for this application, as the following image shows. Provide consent for the tenant.
84+
85+
![grant consent image.](/defender/media/security-intelligence-images/msi-grant-admin-consent.jpg)
86+
87+
4. If the administrator receives an error while attempting to provide consent manually, try either [Option 1](#option-1-approve-enterprise-application-permissions-by-user-request) or [Option 2](#option-2-provide-admin-consent-by-authenticating-the-application-as-an-admin) as possible workarounds.
88+
89+
#### Option 1: Approve enterprise application permissions by user request
90+
91+
Microsoft Entra Administrators need to allow for users to request admin consent to apps. Verify the setting is configured to **Yes** in [Enterprise applications](https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/UserSettings/menuId/).
92+
93+
![Enterprise applications user settings.](/defender/media/security-intelligence-images/msi-enterprise-app-user-setting.jpg)
94+
95+
More information is available in [Configure Admin consent workflow](/azure/active-directory/manage-apps/configure-admin-consent-workflow).
96+
97+
Once this setting is verified, users can go through the enterprise customer sign-in at [Microsoft security intelligence](https://www.microsoft.com/wdsi/filesubmission), and submit a request for admin consent, including justification.
98+
99+
![Contoso sign in flow.](/defender/media/security-intelligence-images/msi-contoso-approval-required.png)
100+
101+
Administrators can review and approve the application permissions [Azure admin consent requests](https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/AccessRequests/menuId/).
102+
103+
After providing consent, all users in the tenant will be able to use the application.
104+
105+
#### Option 2: Provide admin consent by authenticating the application as an admin
106+
107+
This process requires that Global Administrators go through the Enterprise customer sign-in flow at [Microsoft security intelligence](https://www.microsoft.com/wdsi/filesubmission).
108+
109+
![Consent sign in flow.](/defender/media/security-intelligence-images/msi-microsoft-permission-required.jpg)
110+
111+
Then, admins review the permissions and make sure to select **Consent on behalf of your organization**, and then select **Accept**.
112+
113+
All users in the tenant can now use this application.
114+
115+
#### Option 3: Delete and readd app permissions
116+
117+
If neither of these options resolve the issue, try the following steps (as an admin):
118+
119+
1. Remove previous configurations for the application. Go to [Enterprise applications](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Properties/appId/f0cf43e5-8a9b-451c-b2d5-7285c785684d/objectId/982e94b2-fea9-4d1f-9fca-318cda92f90b)
120+
and select **delete**.
121+
122+
![Delete app permissions.](/defender/media/security-intelligence-images/msi-properties.png)
123+
124+
2. Capture `TenantID` from [Properties](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Properties).
125+
126+
3. Replace `{tenant-id}` with the specific tenant that needs to grant consent to this application in the URL below. Copy the following URL into browser: `https://login.microsoftonline.com/{tenant-id}/v2.0/adminconsent?client_id=f0cf43e5-8a9b-451c-b2d5-7285c785684d&state=12345&redirect_uri=https%3a%2f%2fwww.microsoft.com%2fwdsi%2ffilesubmission&scope=openid+profile+email+offline_access`
127+
128+
The rest of the parameters are already completed.
129+
130+
![Permissions needed.](/defender/media/security-intelligence-images/msi-microsoft-permission-requested-your-organization.png)
131+
132+
4. Review the permissions required by the application, and then select **Accept**.
133+
134+
5. Confirm the permissions are applied in the [Azure portal](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Permissions/appId/f0cf43e5-8a9b-451c-b2d5-7285c785684d/objectId/ce60a464-5fca-4819-8423-bcb46796b051).
135+
136+
![Review that permissions are applied.](/defender/media/security-intelligence-images/msi-permissions.jpg)
137+
138+
6. Sign in to [Microsoft security intelligence](https://www.microsoft.com/wdsi/filesubmission) as an enterprise user with a non-admin account to see if you have access.
139+
140+
If the warning isn't resolved after following these troubleshooting steps, call Microsoft support.
141+
55142
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]

0 commit comments

Comments
 (0)