CrowdStrike and Microsoft Defender in the same organisation: when running both makes sense
Key takeaways
- If CrowdStrike Falcon is the primary protection on a Windows client, Microsoft Defender Antivirus switches itself off. As a rule, it only goes into passive mode if the device is also onboarded to Defender for Endpoint. On Windows Server you have to set passive mode yourself.
- In passive mode, attack surface reduction rules, network protection and cloud-delivered protection, among others, stop working. EDR in block mode, device control and Endpoint DLP keep working.
- Defender for Office 365, Defender for Identity and Defender for Cloud Apps work independently of the EDR on endpoints. Without Defender for Endpoint, however, device signals and the device-level actions of automatic attack disruption are missing.
- Microsoft Sentinel connects to Falcon through a Microsoft connector. Raw data through the Falcon Data Replicator requires a separate CrowdStrike licence.
In many organisations two worlds meet: the Microsoft 365 licence includes Defender capabilities, while CrowdStrike Falcon is the chosen EDR, perhaps because the parent company requires it, the cyber insurer recommended it or the IT provider works with it. The question then is not which product is better, but how the two work together without leaving gaps or being paid for twice. This article shows what happens technically, what you keep and lose, and which criteria to decide by.
What happens to Defender Antivirus when CrowdStrike is installed?
It depends on the operating system and on whether the device is onboarded to Microsoft Defender for Endpoint. According to Microsoft:
| Device | Onboarded to Defender for Endpoint? | Defender Antivirus state |
|---|---|---|
| Windows 10/11 with CrowdStrike as primary protection | No | Disabled, automatically |
| Windows 10/11 with CrowdStrike as primary protection | Yes | Passive mode |
| Windows Server 2016 and later with CrowdStrike | No | Must be disabled or uninstalled manually |
| Windows Server 2016 and later with CrowdStrike | Yes | Passive mode only if you set it |
There is one exception on Windows 11: if Smart App Control is on or in evaluation mode, Microsoft states that Defender Antivirus enters a passive mode even without onboarding. This is not the same as passive mode on devices onboarded to Defender for Endpoint.
On Windows Server, Defender Antivirus does not switch to passive mode by itself. Microsoft documents the registry value ForceDefenderPassiveMode (type REG_DWORD, value 1) under HKLM\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection for this. Set it before onboarding: once tamper protection is on and Defender has been in active mode, Microsoft states that tamper protection prevents the switch back to passive mode.
Two further points matter. The Windows Security Center service must be running; otherwise Defender does not detect the third-party product and stays active, and Microsoft does not support two active antivirus products side by side. And Defender should keep receiving updates in passive mode too. You check the state with Get-MpComputerStatus | select AMRunningMode; expected values are “Normal”, “Passive” or “EDR Block Mode”.
What remains in passive mode and what stops working?
Microsoft documents exactly which protections work in passive mode. The most important ones:
| Capability | Active mode | Passive mode |
|---|---|---|
| Real-time protection (blocking) | Yes | No |
| Cloud-delivered protection | Yes | No |
| Network protection | Yes | No |
| Attack surface reduction rules | Yes | No |
| Controlled folder access | Yes | No |
| File scanning and detection information | Yes | Yes |
| Remediation | Yes | Only through EDR in block mode |
| Device control | Yes | Yes |
| Endpoint DLP | Yes | Yes |
| Web content filtering | Yes | Only in Microsoft Edge |
In practice, the attack surface reduction rules, which for example stop Office macros from launching processes, no longer apply. CrowdStrike then has to cover that layer through its own prevention policies. Check that the corresponding settings are actually enabled in Falcon rather than assuming they are.
EDR in block mode is what makes a mixed setup interesting. According to Microsoft, it lets Defender for Endpoint detect and remediate malicious artefacts after a breach even when Defender Antivirus is not the primary antivirus. That adds a second detection layer, but only on devices onboarded to Defender for Endpoint. Microsoft also recommends adding the Defender processes to the other product’s exclusion list. Align mutual exclusions with CrowdStrike’s documentation.
What do you lose and keep in Microsoft Defender XDR?
Microsoft Defender XDR is the common portal for several products. Most of them do not depend on the EDR on endpoints:
- Defender for Office 365 protects email and collaboration in Exchange Online, Teams and SharePoint. It works regardless of the EDR.
- Defender for Identity monitors Active Directory through sensors on the domain controllers and can disable compromised accounts.
- Defender for Cloud Apps assesses cloud applications and OAuth apps.
What is missing without Defender for Endpoint are device signals in the cross-product correlation and actions that take effect on endpoints. Microsoft’s automatic attack disruption includes actions such as “Contain device”, “Contain user” and “Isolate device”; according to Microsoft these only take effect on devices onboarded to Defender for Endpoint. Actions through Entra ID and Defender for Identity, such as disabling an account or revoking sessions, remain available.
This leads to two operating models:
- CrowdStrike only on endpoints. Defender Antivirus is disabled, Defender XDR uses email, identity and cloud app signals. Endpoint detection and response sits entirely in Falcon.
- CrowdStrike primary, Defender for Endpoint in addition. Defender Antivirus runs passively, EDR in block mode is on and device signals flow into Defender XDR. You keep device-level attack disruption, but you run two sensors and need rules for which team responds to which alert.
How does Falcon telemetry reach Microsoft Sentinel?
Microsoft provides several CrowdStrike connectors in the Sentinel content hub:
- The CrowdStrike API Data Connector, built on the Codeless Connector Framework, retrieves alerts, detections, hosts, cases and vulnerabilities through the CrowdStrike API. For most organisations it is the starting point.
- The Falcon Data Replicator connectors collect raw Falcon sensor events from an AWS S3 bucket, either one managed by CrowdStrike or your own. According to Microsoft, a Falcon Data Replicator licence must be available and enabled for this.
- The CrowdStrike Falcon Adversary Intelligence connector brings indicators from the Falcon Intelligence API into Sentinel’s threat intelligence.
Raw data from the Data Replicator allows your own hunting queries across process and network events, but it produces large volumes that Sentinel bills by data volume. Start with the API connector for alerts and detections. Raw data only pays off once your SOC actually uses it for threat hunting.
How do you avoid paying twice for licences?
First check what you already pay for. Microsoft 365 E5 and the Microsoft Defender Suite include Defender for Endpoint Plan 2, Microsoft 365 E3 includes Plan 1, and Microsoft 365 Business Premium includes Defender for Business. For servers, Defender for Endpoint is included in Defender for Servers Plan 1 and Plan 2. If you also license Falcon Insight XDR for the same devices, you pay twice for EDR.
That can still make sense if you choose model 2 deliberately. It becomes wasteful when Defender for Endpoint is licensed but not onboarded anywhere, or when Defender for Servers is enabled for Azure VMs that run Falcon anyway. Since February 2026, the CrowdStrike Falcon platform has also been available through Microsoft Marketplace and, according to Microsoft, counts towards an Azure consumption commitment (MACC). That does not change the double-licensing question, but it can simplify budget planning.
Which criteria should drive the decision?
Our recommendation: one primary EDR per device class, one clearly named console for response, and Defender capabilities beyond the endpoint in use in every case.
| Situation | Recommendation |
|---|---|
| Microsoft 365 E5 or Business Premium, no existing CrowdStrike contract | Defender for Endpoint as the only EDR |
| CrowdStrike is the group standard, SOC works in Falcon | CrowdStrike primary; keep using Defender for Office 365, Identity and Cloud Apps; Falcon alerts into Sentinel |
| CrowdStrike primary, but a Microsoft licence with Defender for Endpoint Plan 2 exists and attack disruption is wanted | Model 2 with passive Defender and EDR in block mode, with a clear ownership rule |
| CrowdStrike contract is up for renewal | Evaluate moving to Defender for Endpoint if the licence is already paid for |
Regulated organisations should ask one more question: can your SOC assess an incident within the NIS2 or DORA reporting deadlines if the signals are spread across two consoles? If not, at least set up Sentinel as a common view.
Next step
Our Endpoint Security services cover reviewing existing EDR configurations and introducing Defender for Endpoint, including in mixed setups. If signals from Falcon and Defender should come together in one SOC, our Managed Security service supports you.
Frequently asked questions
Can Defender Antivirus and CrowdStrike both protect actively at the same time?
No. Microsoft does not support running Defender Antivirus and another antivirus product both in active mode. Defender then runs passively or is disabled.
Does EDR in block mode work if CrowdStrike is the primary antivirus?
Yes. According to Microsoft, EDR in block mode is intended precisely for devices on which Defender Antivirus is not the primary protection. The device must be onboarded to Defender for Endpoint and Defender Antivirus must run in passive mode.
Does Defender for Office 365 need Defender for Endpoint?
No. Defender for Office 365 protects email and collaboration regardless of which EDR runs on the endpoints.
Does Defender for Cloud recognise CrowdStrike on Azure VMs?
Yes. With Defender for Servers Plan 2 or Defender CSPM, Defender for Cloud checks agentlessly whether an EDR runs on VMs and, according to Microsoft, also recognises CrowdStrike Falcon on Windows and Linux.
Book an introductory call