Microsoft Defender for Endpoint
by Microsoft
Enterprise endpoint protection, EDR and vulnerability management from Microsoft.
- Category
- IT, Security & Monitoring
- Type
- Endpoint security
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0
02Data
What you can sync.
- Machines
- Alerts
- Vulnerabilities
- Software inventory
- Recommendations
Keep Microsoft Defender for Endpoint machines in your own Lake, on your servers, and report on it with the rest of IT.
Need more? Name any other Microsoft Defender for Endpoint data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
Microsoft Defender for Endpoint uses OAuth 2.0 (client ID, client secret, refresh token). You add the credentials once, when the AI asks for them, and it tells you where to create them in Microsoft if you need help.
04How it works
How it works in DataMind.
-
Pick Microsoft Defender for Endpoint.
Open Lake, pick Microsoft Defender for Endpoint in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Microsoft Defender for Endpoint API docs.
-
Answer a few questions.
The AI reads the Microsoft Defender for Endpoint documentation, then asks which credentials you will use, which data to sync (for example machines and alerts), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Microsoft Defender for Endpoint data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.