Skip to content

Add a Companion skill to the RBA Summary Scrip - #2579

Draft
Shane Ferrell (Shanefe) wants to merge 2 commits into
mainfrom
Create_RBA_Skill
Draft

Add a Companion skill to the RBA Summary Scrip#2579
Shane Ferrell (Shanefe) wants to merge 2 commits into
mainfrom
Create_RBA_Skill

Conversation

@Shanefe

Copy link
Copy Markdown
Contributor

Modernizes Get-RBASummary.ps1 into a best-effort evidence collector with structured JSON output and adds an EXO RBA troubleshooting skill for safe, deterministic analysis.

Changes

  • Adds versioned JSON output containing:
    • Collector and overall collection status
    • Structured errors and stable finding IDs
    • Mailbox, CalendarProcessing, permission, lifecycle, and RBA log evidence
    • Sanitized, targeted-meeting, and full privacy modes
  • Continues independent collection when individual Exchange Online cmdlets fail.
  • Adds -MeetingSubject to locate recent meetings in retained RBA logs.
  • Extracts and normalizes meeting IDs, then correlates initial requests, updates, and cancellations.
  • Preserves complete RBA processing blocks using the exact START boundary.
  • Documents that logs are newest-first and each block must be read bottom-up chronologically.
  • Adds deterministic findings for configuration, routing, post-processing, permissions, recurrence, and observed log behavior.
  • Adds the EXO RBA troubleshooting skill, generic TSG safety rules, RBA rule catalog, and package metadata.
  • Adds build support for generating the single-file customer-facing skill artifact.
  • Expands public documentation with requirements, parameters, output files, privacy guidance, targeted-log behavior, and skill usage.
  • Adds focused Pester coverage for collection failures, sanitization, findings, lifecycle evidence, permissions, targeted meeting correlation, block boundaries, GOID normalization, and skill packaging.

Copilot AI lite review requested due to automatic review settings August 29, 2026 00:27
@Shanefe
Shane Ferrell (Shanefe) requested a review from a team as a code owner August 29, 2026 00:27
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR modernizes Get-RBASummary.ps1 into a best-effort evidence collector that produces structured JSON output (with findings, collector status, and optional targeted meeting log correlation), updates the public documentation accordingly, and extends the build pipeline to generate a companion troubleshooting skill artifact.

Changes:

  • Enhanced Get-RBASummary.ps1 with independent collectors, structured error capture, and a versioned JSON report (plus optional targeted meeting log search via -MeetingSubject).
  • Expanded documentation to describe JSON output, privacy modes, targeted meeting log behavior, and skill usage flow.
  • Updated build pipeline (and spellcheck dictionary) to support producing a companion “prototype skill” output.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File Description
docs/Calendar/Get-RBASummary.md Documents the new JSON report, privacy/targeted meeting behavior, and troubleshooting skill usage.
Calendar/Get-RBASummary.ps1 Adds best-effort collectors, structured JSON output, and targeted meeting log correlation helpers.
.build/cspell-words.txt Adds “Goid” to the spellcheck allowlist for new log/GOID terminology.
.build/Build.ps1 Attempts to add build support for generating the skill artifact into dist/.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread Calendar/Get-RBASummary.ps1 Outdated
Comment thread Calendar/Get-RBASummary.ps1
Comment thread Calendar/Get-RBASummary.ps1 Outdated
Comment thread .build/Build.ps1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants