-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#11810 - Enabling m365_defender with Agentless deployment #12891
Conversation
🚀 Benchmarks reportTo see the full report comment with |
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
💚 Build Succeeded
History
|
|
Package m365_defender - 2.24.0 containing this change is available at https://epr.elastic.co/package/m365_defender/2.24.0/ |
Parent Ticket:
#11810
Proposed commit message
Updated the documentation based upon agreed upon language to highlight that the integration now supports Agentless deployment

Upgraded the
format_version
to latest, 3.2.3Updated Kibana version constraints to ^8.18 || ^9.0.0
Checklist
changelog.yml
file.How to test this PR locally
Note that
Incident.Read.All
andIncident.ReadWrite.All
was not added as these APIs permissions are not available anymore within the permissions list and the integration has marked as deprecated2. Fill in the client id, client secret and tenant id and install the integration, only tested API and did NOT setup Azure Event Hub
3. The integration does not fetch past events and only events from the time the integration is installed so I was forced to use
msgraph import GraphServiceClient
to touch an existing Incident, this allowed the Incident to update it's date field and the data was ingested into ES via Agentless Agent4. Validated that the incidents that were touched were seen within Elasticsearch/Kibana
5. Validated that agent logs did not show any errors