LinuxDIY Test Alerts not generating in MDE after onboarding linux server

Yashaswini Mahadeva (CP, IN) 0 Reputation points
2026-08-28T11:58:36.02+00:00

Hi Team,obraz

After successfully onboarding linux server to MDE, Eicar test alerts are generated but linux EDR diy test alert not generating only showing in the events timeline in mde, can you please check and provide the root cause and the solution for it.

Microsoft Security | Microsoft Defender | Other
0 comments No comments

1 answer

Sort by: Newest
  1. AI answer

    2026-08-28T11:58:59.9066667+00:00

    For Linux, the documented expected result of the EDR DIY test is that a detection should be raised after a few minutes in the Microsoft Defender portal / Microsoft Defender XDR. Since EICAR detections are working, onboarding and AV reporting are at least partially working, but the EDR test path should be validated separately.

    Use this end-to-end check:

    1. Confirm the device is visible in the Microsoft Defender portal device inventory. The device can take 5–20 minutes to appear after onboarding.
    2. Run the Linux EDR DIY test exactly as documented:
         curl -o ~/Downloads/MDE-Linux-EDR-DIY.zip -L https://aka.ms/MDE-Linux-EDR-DIY
         unzip ~/Downloads/MDE-Linux-EDR-DIY.zip
         chmod +x ./mde_linux_edr_diy.sh
         ./mde_linux_edr_diy.sh
      
    3. Wait a few minutes, then check in the Defender portal / Microsoft Defender XDR for:
      • the alert details
      • the machine timeline
    4. If the activity appears only in the timeline/events but no alert is raised, collect diagnostics from the Linux device:
         sudo mdatp diagnostic create
      
      Then provide the generated diagnostic zip to Microsoft support.

    Additional checks supported by the documentation:

    • Verify real-time protection is enabled:
        mdatp health --field real_time_protection_enabled
      
      If it is not enabled:
        mdatp config real-time-protection --value enabled
      
    • If mdatp is not available from the shell, restore the command symlink:
        sudo ln -sf /opt/microsoft/mdatp/sbin/wdavdaemonclient /usr/bin/mdatp
      
    • If installation success is in doubt, verify installation logs:
        sudo journalctl --no-pager|grep 'microsoft-mdatp' > installation.log
        grep 'postinstall end' installation.log
      

    Supported conclusion from the available documentation:

    • EICAR success does not by itself confirm EDR alert generation.
    • For the Linux EDR DIY test, the expected behavior is an alert after a few minutes.
    • If no alert is generated, the documented next step is to collect diagnostics and engage support with those logs.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.