CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sentinel-xdr-migration-orchestrator

Orchestrate conversion of a Microsoft Sentinel solution into Defender XDR Custom Detection YAML by using repository utilities and available runtime providers.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/sentinel-xdr-migration-orchestrator/SKILL.md
SKILL.md
Quality
Evals
Security

Migrate a Microsoft Sentinel solution to XDR Detection YAML

The goal is to migrate the solution and support publishing validated content. Follow the canonical workflow's strict over-50% partial-publication policy and single-owner ACTION_REQUIRED watchdog best practice; do not reproduce those policies here.

Scope

This milestone creates and validates XDR Detections/*.yaml.

It does not:

  • generate or modify ARM templates;
  • deploy analytic rules or Custom Detections;
  • generate or ingest mock data;
  • convert workbooks;
  • compare generated alerts.

Workflow

  1. If the package is unavailable, install it from the repository:

    python -m pip install -e Tools\SentinelToXDRMigration
  2. Run sentinel-xdr-migration doctor.

  3. If firstRun is true, run sentinel-xdr-migration setup --non-interactive.

  4. Inspect the official Triage MCP capabilities. Prefer its advertised tools for every supported runtime query operation, including RunAdvancedHuntingQuery. This check is separate from doctor, because MCP authentication belongs to the agent host rather than the Python CLI.

  5. Ask before launching interactive CLI or MCP sign-in. Continue with offline conversion if authentication is declined or unavailable.

  6. Confirm the solution path.

  7. Use sentinel-xdr-rule-converter; conversion always runs locally and does not depend on MCP.

  8. Review every needsReview result. Never present it as XDR-ready.

  9. Use sentinel-xdr-detection-validator. Prefer Triage MCP for supported original Sentinel and Advanced Hunting queries. Fall back to Log Analytics CLI/API for Sentinel queries and the Graph CLI for Advanced Hunting only when the MCP lacks the capability or has a provider-level failure, never for genuine KQL failures.

  10. Report:

  • source analytic rules;
  • generated detection files;
  • deterministic rewrites;
  • provenance status;
  • Sentinel and Advanced Hunting execution status;
  • unresolved parity gaps.

An XDR-ready result requires valid YAML, no conversion errors, successful runtime execution on both platforms, and reviewed entity mappings.

Repository

Azure/Azure-Sentinel

Path

.github/skills/sentinel-xdr-migration-orchestrator/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.