Repository navigation
Microsoft Defender for Office 365: add XDR workbook - #15324
Merged
v-atulyadav merged 6 commits intoOct 15, 2026
Merged
Conversation
…l content Preserve existing connector, workbook and playbook selections; generate additive 3.2.0 review candidate. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
v-atulyadav
added
Solution
updated 3.2.0 row.
This reverts commit ca49c39.
Preserve the original native Notebook and explicit source/query review provenance without adding a Sentinel parent. Regenerate the additive candidate with the V3.1 hybrid packager while retaining all existing content. The packaging-time ARM-TTK run reports 47 passes and six failures, plus a trailing null-Path diagnostic. This remains an unqualified review candidate; no full suite or deployment was performed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Validate the reviewed canonical Notebook and query inventory directly from the native XDR artifact. Preserve historical import provenance and all stable identities; no separate source file or Sentinel parent is required. Rebuilt with corrected V3.1 tooling; deployed package JSON is unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Use the exact O365 offer tracking ID supplied by the owner. Regenerate the additive 3.2.0 candidate with V3.1; the sole semantic ARM addition is the empty unconditional root attribution deployment. Both XDR workbooks and existing Sentinel content remain unchanged. Automatic ARM-TTK reports 47 passes and six failures plus the existing null-Path diagnostic. Partner Center acceptance remains unverified. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
v-atulyadav
approved these changes
Oct 15, 2026
Ofer Inbar (oferInbar)
added
1P Solution
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
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.
Change(s):
XDR Workbooks/MicrosoftDefenderForOffice365.jsonalongside the existing Sentinel workbook.Package/3.2.0.zip.EmailEvents,EmailAttachmentInfoandEmailUrlInfofor the XDR sibling.serializedDatacontract and use object-shaped Notebook content for the XDR workbook.Reason for Change(s):
Version Updated:
3.0.3→3.2.0.Testing Completed:
DeployDefenderWorkbook=false).Checked that the validations are passing and have addressed any issues that are present:
Cannot bind argument to parameter 'Path' because it is null.after generating the artifacts. Its zero process exit code is not treated as validation success.