Use this article as a guide to resolve issues you might encounter in Defender for Business.
My setup and configuration process failed
If you're using the simplified configuration process in Defender for Business and something went wrong, you can still configure your security settings and policies manually. See Set up and configure Defender for Business.
I'm seeing indications that some devices aren't protected even though they're onboarded to Defender for Business
If devices are running a non-Microsoft antivirus/antimalware solution, real-time protection might be turned off when those devices are onboarded to Defender for Business. Real-time protection is turned on by default in Defender for Business, but a non-Microsoft antivirus/antimalware solution might affect your settings. When real-time protection is turned off, you'll see notifications in the Microsoft Defender portal (https://security.microsoft.com) that some devices aren't protected. In these cases, make sure real-time protection is turned on.
To confirm that real-time protection is turned on, you can view, and if necessary, edit your next-generation protection policies. See View or edit your next-generation protection policies.
We recommend using Microsoft Defender Antivirus together with Defender for Business to get better protection that's coordinated across products and services. To learn more, see Better together - Microsoft Defender Antivirus and Microsoft Defender for Endpoint.
Users are unable to onboard mobile devices using the Microsoft Defender app.
If Defender for Business hasn't finished provisioning, users might not be able to onboard their mobile devices using the Microsoft Defender app. To confirm whether provisioning has completed follow these steps:
Go to the Microsoft Defender portal and sign in.
In the navigation bar, go to Assets > Devices.
If you see a message that says, "Hang on! We're preparing new spaces for your data and connecting them," it means that Defender for Business hasn't finished provisioning. This process is happening now, and can take up to 24 hours to complete.
If you see a list of devices, or you're prompted to onboard devices, it means Defender for Business provisioning has completed. Users should now be able to onboard their mobile devices as expected.
Users are running into issues with the Microsoft Defender app on their mobile devices.
If users are reporting issues with the Microsoft Defender app, see the following resources to help troubleshoot their issues:
I need to resolve a policy conflict
Policy conflicts can arise when security policies are defined using multiple tools or methods. Here's an example:
Suppose that Lee has been using Microsoft Intune to manage devices and security settings. Lee has recently started using Defender for Business. Lee has chosen to use the simplified configuration process in Defender for Business. Now, Lee sees policy conflicts in Intune and in the Microsoft Defender portal.
Fortunately, policy conflicts can be resolved by taking one or more of the following actions:
- Delete your existing policies in the Intune admin center
- See Troubleshoot policies in Microsoft Intune
See the following articles to learn more about your security policies in Defender for Business:
There's an integration issue between Defender for Business and Microsoft Intune
During your setup and configuration process, you might see an error message that says:
Something went wrong, and we couldn't complete your setup process. There's an integration issue between Defender for Business and Microsoft Endpoint Manager.
The error message means that a configuration channel must be established between Defender for Business and Microsoft Intune. If you see the error message, it means that something has gone wrong with integration. To resolve the issue, use the following three procedures:
Procedure 1: Turn on the Microsoft Intune connection in the Microsoft Defender portal
Go to the Microsoft Defender portal (https://security.microsoft.com) and sign in.
Choose Settings > Endpoints. Then, under General, select Advanced features.
Scroll down to Microsoft Intune connection, and make sure it's turned on.
Procedure 2: Set the enforcement scope for Defender for Business
Go to the Microsoft Defender portal (https://security.microsoft.com), and sign in.
Choose Settings > Endpoints. Under Configuration management, select Enforcement scope.
Under OS platform, turn on Windows Client devices.
Procedure 3: Turn on Endpoint Security Profile settings in Intune
Go to Intune (https://intune.microsoft.com) and sign in.
Select Endpoint security, and then, under Setup, select Microsoft Defender for Endpoint.
Under Endpoint Security Profile Settings, set Allow Microsoft Defender for Endpoint to enforce Endpoint Security Configurations to On.
Something went wrong with onboarding devices in the Microsoft Defender portal
When you're onboarding devices in the Microsoft Defender portal (https://security.microsoft.com), if something went wrong, an error message is displayed. This issue can occur if you're onboarding devices using a downloadable onboarding package for Microsoft Intune, Group Policy, System Center Configuration Manager, or Mobile Device Management capabilities with Defender for Business.
Defender for Business uses a capability called Security Management for Microsoft Defender for Endpoint. If onboarding in Defender for Business fails, the cause most likely has to do with Security Management for Defender for Endpoint. To resolve the issue, see the following articles:
Alternately, you can try onboarding devices manually. See Onboard devices.