How to Deploy Microsoft Defender for Endpoint Without Intune
Question details
A small organization with 20 on-premises devices needs to deploy Microsoft Defender for Endpoint without using Microsoft Intune or an Active Directory domain controller.

- Product
- Microsoft Defender for Endpoint
- Device & OS
- Windows
- Scenario
- Deploying enterprise endpoint security in a small network environment that lacks centralized domain management or cloud-based device management systems.
- Observed behavior
- The available local onboarding script restricts deployment to 10 devices and consumes additional CPU resources due to high data-reporting frequencies meant only for evaluation.
Before attempting deployment, ensure you have local administrative privileges on all target devices and that they meet the minimum operating system requirements for the Defender sensor.
Use an Alternative Centralized Deployment Tool
This is the recommended approach for production environments to avoid the performance penalties and device limits of local evaluation scripts.
While Intune and a Domain Controller are not strictly required for onboarding, Microsoft highly recommends using a centralized deployment method for production environments. Manual local scripts are designed purely for evaluation and use a high data-reporting frequency that can impact system CPU performance.
Identify an alternative endpoint management tool available in your network, such as Microsoft Endpoint Configuration Manager (MECM) or a third-party software distribution system.
Log into the Microsoft 365 Defender portal, navigate to Settings > Endpoints > Onboarding, and select the specific deployment method corresponding to your centralized management tool.
Deploy the downloaded onboarding package across your 20 devices using your management tool's standard software distribution protocols.

Use the Local Script Method (At Your Own Risk)
Can technically be executed manually on up to 20 devices if no centralized management tool is available, though it is not recommended by Microsoft.
Equip Your Endpoints with WPS Office
While you work on securing your organization's devices, ensuring your team has efficient and lightweight productivity tools is just as important. WPS Office provides a complete, professional office suite that minimizes system resource usage—ideal for small business environments.
- 1. Download the lightweight installer: Visit the official WPS website to download the unified installer, perfect for deploying across multiple endpoints without straining network bandwidth.
- 2. Install on local devices: Run the installer on your Windows endpoints. Its minimal footprint guarantees it won't interfere with your Microsoft Defender deployment.
- 3. Open existing documents seamlessly: Double-click your existing Microsoft Office files to open them instantly in WPS Office with all original formatting preserved.

Frequently Asked Questions
Why does Microsoft recommend a 10-device limit for the local onboarding script?
The local script is explicitly designed for evaluation purposes. It uses a much higher data-reporting frequency to provide rapid telemetry during testing, which consumes more CPU and network resources than standard production onboarding methods.
Can I manually change the data-reporting frequency in Microsoft Defender for Endpoint?
No, there is currently no separate setting or registry key available to manually adjust the reporting frequency for threat hunting. Microsoft balances default reporting latency dynamically to optimize both speed and CPU performance.
Are Intune or a Domain Controller strictly mandatory for deploying Defender?
No. While Microsoft Intune and an Active Directory Domain Controller streamline the deployment process, they are not strictly required. You can use any centralized deployment solution, such as Microsoft Endpoint Configuration Manager or third-party endpoint management tools.




