Add M365 defender oauth2 params for incident and alert - #16628
Merged
Conversation
4 tasks
Contributor
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
incident |
1077.59 | 840.41 | -237.18 (-22.01%) | 💔 |
alert |
893.66 | 715.31 | -178.35 (-19.96%) | 💔 |
event |
634.92 | 521.92 | -113 (-17.8%) | 💔 |
To see the full report comment with /test benchmark fullreport
narph
added
Integration:m365_defender
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
chrisberkhout
approved these changes
Dec 19, 2025
chrisberkhout
left a comment
chrisberkhout
left a comment
Contributor
There was a problem hiding this comment.
It's nice to have system tests covering this and I think it's enough.
But it wouldn't hurt to have policy tests as well.
Here's an example from o365: it confirms that this config gets rendered like this in the policy.
Co-authored-by: Chris Berkhout <chris.berkhout@elastic.co>
…tic/integrations into m365_defender-oauth2-params
💚 Build Succeeded
History
cc @a03nikki |
Contributor
|
Package m365_defender - 5.4.0 containing this change is available at https://epr.elastic.co/package/m365_defender/5.4.0/ |
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Add support for OAuth2Endpoint Params option for alert and incident data streams.
The Alert and Incident data streams use the httpjson input type. This pull request adds the parameter along with the http mocks to test the parameters.
The configuration changes were heavily copied from previous Microsoft integration updates including #15667, #14924, and #15749.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Use Kibana to validate the parameters are presented.
Related issues
Screenshots
None taken