Skip to content

Microsoft Defender XDR: fix XDR workbooks (3.2.2) - #15331

Merged
v-atulyadav merged 3 commits into
Azure:masterfrom
kingwil:kingwil/xdr-workbook-fixes-3-2-2
Oct 16, 2026
Merged

v-atulyadav merged 3 commits into
Azure:masterfrom
kingwil:kingwil/xdr-workbook-fixes-3-2-2

Conversation

@kingwil

@kingwil kingwil commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Change(s):

  • Endpoint: fix time filters, daily chart/counts, Tor cutoff and empty labels.
  • Identity: fix time filters, port chart, account fallbacks and weighted logon totals/trends.
  • Detections and Insights: fix Teams Subject queries, consistent incident/true-positive totals, time bindings and Defender guidance.
  • Retain IDs, Sentinel content, attribution and historical conversion evidence. Add reviewed-update evidence, V3.1 package and one short release note.

Reason for Change(s):

Version Updated:

  • Solution and all three XDR workbooks: 3.2.1 -> 3.2.2.

Testing Completed:

  • Per supplied changelog: Endpoint/Identity re-imported and 21 surfaces each checked; all 243 Detections queries returned HTTP 200 at seven days.
  • User visually accepted all five workbooks at 24 hours on 15 October. Empty panels lack populated-rendering proof; full 90-day workload was not rerun.

Checked that the validations are passing and have addressed any issues that are present:

Preserve user-tested Notebook edits and stable IDs. Record fresh reviewed-update evidence separately from historical migration receipts, retain existing solution content and attribution, regenerate with V3.1, and add a short release note. Automatic ARM-TTK still fails inner-template extraction; no new live qualification claimed.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@kingwil
kingwil requested review from a team as code owners October 15, 2026 14:44
@v-atulyadav v-atulyadav added Solution Solution specialty review needed XDR Defender XDR Custom Detection content labels Oct 16, 2026
@v-atulyadav v-atulyadav self-assigned this Oct 16, 2026
Retain approval and migration evidence only in ignored local receipts. Publish compact identity/version/dependency metadata and explicitly cover SecurityIncident with the existing MicrosoftThreatProtection connector. Preserve all Notebook content, IDs and 3.2.2 versions; regenerate V3.1 candidate.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
v-atulyadav
v-atulyadav previously approved these changes Oct 16, 2026
Keep queries, managed IDs and candidate versions unchanged. Regenerate the V3.1 package with readable portal names.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@v-atulyadav
v-atulyadav merged commit eed6c39 into Azure:master Oct 16, 2026
33 of 34 checks passed
@oferInbar Ofer Inbar (oferInbar) added 1P Solution 1P Microsoft-owned Sentinel solution Migration Sentinel-to-Defender-XDR content migration (NPF) labels Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1P Solution 1P Microsoft-owned Sentinel solution Migration Sentinel-to-Defender-XDR content migration (NPF) Solution Solution specialty review needed XDR Defender XDR Custom Detection content

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants