Add Sentinel Data Connector and Agent Builder tool#14543
Open
suchandanreddy wants to merge 1 commit into
Open
Conversation
Author
|
@microsoft-github-policy-service agree company="Microsoft"
…On Mon, Jun 22, 2026 at 8:31 PM microsoft-github-policy-service[bot] < ***@***.***> wrote:
*microsoft-github-policy-service[bot]* left a comment
(Azure/Azure-Sentinel#14543)
<#14543 (comment)>
@suchandanreddy <https://github.com/suchandanreddy> please read the
following Contributor License Agreement(CLA). If you agree with the CLA,
please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
- (default - no company specified) I have sole ownership of
intellectual property rights to my Submissions and I am not making
Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
- (when company given) I am making Submissions in the course of work
for my employer (or my employer has intellectual property rights in my
Submissions by contract or applicable law). I have permission from my
employer to make Submissions and enter into this Agreement on behalf of my
employer. By signing below, the defined term “You” includes me and my
employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement Contribution License Agreement
This Contribution License Agreement (*“Agreement”*) is agreed to by the
party signing below (*“You”*),
and conveys certain license rights to Microsoft Corporation and its
affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is
effective as of the latest signature
date below.
1. *Definitions*.
*“Code”* means the computer software code, whether in human-readable
or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
*“Project”* means any of the projects owned or managed by Microsoft
and offered under a license
approved by the Open Source Initiative (www.opensource.org).
*“Submit”* is the act of uploading, submitting, transmitting, or
distributing code or other content to any
Project, including but not limited to communication on electronic
mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf
of, the Project for the purpose of
discussing and improving that Project, but excluding communication
that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
*“Submission”* means the Code and any other copyrightable material
Submitted by You, including any
associated comments and documentation.
2. *Your Submission*. You must agree to the terms of this Agreement
before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now
or in the future (except as
described in Section 4 below), Submit to any Project.
3. *Originality of Work*. You represent that each of Your Submissions
is entirely Your original work.
Should You wish to Submit materials that are not Your original work,
You may Submit them separately
to the Project if You (a) retain all copyright and license information
that was in the materials as You
received them, (b) in the description accompanying Your Submission,
include the phrase “Submission
containing materials of a third party:” followed by the names of the
third party and any licenses or other
restrictions of which You are aware, and (c) follow any other
instructions in the Project’s written
guidelines concerning Submissions.
4. *Your Employer*. References to “employer” in this Agreement include
Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a
contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your
employer has intellectual
property rights in Your Submission by contract or applicable law, You
must secure permission from Your
employer to make the Submission before signing this Agreement. In that
case, the term “You” in this
Agreement will refer to You and the employer collectively. If You
change employers in the future and
desire to Submit additional Submissions for the new employer, then You
agree to sign a new Agreement
and secure permission from the new employer before Submitting those
Submissions.
5. *Licenses*.
- *Copyright License*. You grant Microsoft, and those who receive the
Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly
display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all
of the foregoing rights to third
parties.
- *Patent License*. You grant Microsoft, and those who receive the
Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or
the combination of the
Submission with the Project to which it was Submitted to make, have
made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the
Project.
- *Other Rights Reserved*. Each party reserves all rights not
expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without
limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
6. *Representations and Warranties*. You represent that You are
legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your
original work (except as You may
have disclosed under Section 3). You represent that You have secured
permission from Your employer to
make the Submission in cases where Your Submission is made in the
course of Your work for Your
employer or Your employer has intellectual property rights in Your
Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You
represent and warrant that You
have the necessary authority to bind the listed employer to the
obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless
You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE
WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED
UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO,
ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. *Notice to Microsoft*. You agree to notify Microsoft in writing of
any facts or circumstances of which
You later become aware that would make Your representations in this
Agreement inaccurate in any
respect.
8. *Information about Submissions*. You agree that contributions to
Projects and information about
contributions may be maintained indefinitely and disclosed publicly,
including Your name and other
information that You submit with Your Submission.
9. *Governing Law/Jurisdiction*. This Agreement is governed by the
laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal
courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in
which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County,
Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
10. *Entire Agreement/Assignment*. This Agreement is the entire
agreement between the parties, and
supersedes any and all prior agreements, understandings or
communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may
be assigned by Microsoft.
—
Reply to this email directly, view it on GitHub
<#14543?email_source=notifications&email_token=AJOPJ6BAYKGQFSNTSMNEYJD5BHMWDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZXGQ3TQNBSG42KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4774784274>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJOPJ6D5DBDMUJYXNLLPINL5BHMWDAVCNFSNUABFKJSXA33TNF2G64TZHMYTINJRHAZTENZRHNEXG43VMU5TINZSGE4DKNBVGQ2KC5QC>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/AJOPJ6HDYO7VOC6CEHFKILT5BHMWDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZXGQ3TQNBSG42KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y>
and Android
<https://github.com/notifications/mobile/android/AJOPJ6FI7LFJ4SPS6UXVI735BHMWDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZXGQ3TQNBSG42KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a new self-contained “Sentinel Data Connector and Agent Builder” tool under Tools/ to guide ISVs/partners through Sentinel Data Lake onboarding, sample data ingestion, MCP schema verification, Security Copilot agent (or custom MCP tools) creation, and publishing workflows—primarily via Copilot instructions/skills plus helper scripts.
Changes:
- Adds templates and knowledge-base docs to drive a phased onboarding + authoring workflow.
- Adds multiple PowerShell/bash utilities for prerequisite checks, data lake detection/remediation, ingestion validation, SCU lifecycle/cost control, MCP manifest validation, and packaging.
- Adds VS Code chat participant extension scaffolding (
package.json,src/extension.js) alongside workspace-level Copilot instructions/skills.
Reviewed changes
Copilot reviewed 50 out of 56 changed files in this pull request and generated 11 comments.
Show a summary per file
| File | Description |
|---|---|
| Tools/Sentinel-Data-Connector-and-Agent-Builder/templates/use-case-brief.md.tmpl | Use-case brief template for ideation and planning inputs. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/templates/mcp-tool-definition.json.tmpl | Template for a custom MCP tool definition with parameterized KQL. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/templates/entities.json.tmpl | Entity pools template for generating correlated scenarios/sample data. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/templates/dcr-transform.kql.tmpl | KQL transform template for DCR ingestion normalization. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/templates/dcr-per-table.json | ARM template for per-table DCR deployments for Logs Ingestion API. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/templates/custom-table-schema.json.tmpl | Template for creating custom table schema resources. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/templates/agent-instructions.yaml.tmpl | YAML template for agent instruction scaffolding. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/src/extension.js | VS Code chat participant implementation that loads instructions/knowledge and calls the LM. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/validate-urls.sh | URL validation helper to enforce link hygiene with JSONL output. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Validate-Prerequisites.ps1 | Prerequisite and role checks for tenant/subscription readiness. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Validate-Ingestion.ps1 | Validates ingestion by querying tables and (optionally) scenario assertions. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Validate-DataLake.ps1 | Tenant-wide data lake onboarding detection + remediation directions. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Test-McpToolsManifest.ps1 | Static validator for custom MCP tool manifests (lint + optional render). |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Test-AgentInSecurityCopilot.ps1 | SCU preflight + runbook generation for SCC validation. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Setup-ScuAutoDelete.ps1 | One-time deployment of server-side SCU auto-delete automation. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Setup-DataIngestion.ps1 | Sets up table/DCE/DCR ingestion infrastructure via az + REST. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Remove-SccCapacity.ps1 | Deletes SCU capacities (and optionally RG) with cost estimation and cleanup. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Package-Agent.ps1 | Packages agent for publishing with Phase 5 validation gate + table renames. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Ingest-SampleData.ps1 | Posts sample records to Logs Ingestion API for verification. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Grant-IngestionRbac.ps1 | Grants RG-scope RBAC to avoid per-DCR cold-start authorization caching issues. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Get-ScuCostWindow.ps1 | Computes cost-window timing + recommendations for SCU hour-block billing. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scripts/Create-Workspace.ps1 | Creates LAW + enables Sentinel with region allowlist checks. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/schemas/.gitkeep | Placeholder documenting per-ISV schemas directory usage. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/scenarios/.gitkeep | Placeholder documenting per-ISV scenarios directory usage. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/package.json | VS Code extension manifest for chat participant contribution. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/knowledge/use-case-frameworks.md | Reference content for structured use-case ideation. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/knowledge/security-copilot-agent-guide.md | Step-by-step SCC build/validation guidance and Phase 5 gate definition. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/knowledge/publishing-guide.md | Partner Center/Security Store packaging and submission guide. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/knowledge/mcp-verification-guide.md | MCP setup + Phase 4 schema/query verification recipe and gates. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/knowledge/agent-instructions-lint.md | Prose-level lint rules for SCC instruction documents. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/infra/scu-autodelete/scu-autodelete.bicep | Infrastructure for server-side SCU teardown + notification. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/config/workspace.json.template | Workspace config template for per-tenant setup. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/config/regions.json | Supported region catalog + defaults and guidance. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/agent/investigation-queries.kql | Example investigation KQL blocks mirroring example agent steps. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/agent/agent-instructions.yaml | Example agent instructions YAML for a Contoso scenario. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/agent/README.md | Example Phase 5 workflow instructions for the sample agent. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/README.md | Main tool documentation (setup, prerequisites, phases, scripts). |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/.vscode/launch.json | VS Code debug configuration for running the extension host. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/.gitignore | Ignores per-tenant/per-ISV state, packaging outputs, and local artifacts. |
| Tools/Sentinel-Data-Connector-and-Agent-Builder/.github/skills/sentinel-data-connector-agent-builder/SKILL.md | Skill definition describing capabilities, phase gates, and behaviors. |
Files not reviewed (1)
- Tools/Sentinel-Data-Connector-and-Agent-Builder/package-lock.json: Generated file
Comment on lines
+14
to
+15
| "activationEvents": [], | ||
| "main": "./src/extension.js", |
Comment on lines
+74
to
+89
| // Build the system prompt with agent instructions + relevant knowledge | ||
| const systemPrompt = buildPrompt(instructions, knowledgeContext, command); | ||
|
|
||
| // Use Copilot's language model to generate response | ||
| const messages = [ | ||
| vscode.LanguageModelChatMessage.User(systemPrompt), | ||
| ...context.history.map(h => { | ||
| if (h instanceof vscode.ChatResponseTurn) { | ||
| return vscode.LanguageModelChatMessage.Assistant( | ||
| h.response.map(r => r.value?.value || r.value || '').join('') | ||
| ); | ||
| } | ||
| return vscode.LanguageModelChatMessage.User(h.prompt); | ||
| }), | ||
| vscode.LanguageModelChatMessage.User(request.prompt) | ||
| ]; |
Comment on lines
+101
to
+112
| try { | ||
| $qr = az monitor log-analytics query ` | ||
| --workspace $workspaceId ` | ||
| --analytics-query $kql ` | ||
| --output json 2>$null | ConvertFrom-Json | ||
|
|
||
| if ($qr -and $qr.Count -gt 0) { | ||
| $rows = [int]$qr[0].Rows | ||
| $latest = $qr[0].Latest | ||
| } else { | ||
| $rows = 0; $latest = $null | ||
| } |
Comment on lines
+186
to
+205
| try { | ||
| $qr = az monitor log-analytics query ` | ||
| --workspace $workspaceId ` | ||
| --analytics-query $sc.kqlAssertion ` | ||
| --output json 2>$null | ConvertFrom-Json | ||
|
|
||
| $count = 0 | ||
| if ($qr -and $qr.Count -gt 0) { | ||
| # `| count` returns single row with single 'Count' column | ||
| $row = $qr[0] | ||
| foreach ($prop in $row.PSObject.Properties) { | ||
| if ($prop.Name -match '^(Count|Count_)$') { $count = [int]$prop.Value; break } | ||
| } | ||
| if ($count -eq 0) { | ||
| # fallback: first numeric property | ||
| foreach ($prop in $row.PSObject.Properties) { | ||
| if ($prop.Value -is [int] -or $prop.Value -is [long]) { $count = [int]$prop.Value; break } | ||
| } | ||
| } | ||
| } |
Comment on lines
+125
to
+129
| try { | ||
| az rest --method post ` | ||
| --uri "$logicAppId/runs/$runId/cancel?api-version=2016-06-01" ` | ||
| --output none 2>$null | ||
| Write-Info "Cancelled server-side auto-delete (Logic App run $runId)." |
Comment on lines
+15
to
+19
| "main": "./src/extension.js", | ||
| "contributes": { | ||
| "chatParticipants": [ | ||
| { | ||
| "id": "sentinel-data-connector-agent-builder.builder", |
Comment on lines
+124
to
+129
| if (-not $currentUserId) { | ||
| Write-Status "Could not resolve signed-in user object ID via 'az ad signed-in-user show'. Falling back to UPN-based lookup (may miss MSA / guest accounts)." "warn" | ||
| $azureRoles = az role assignment list --assignee $account.user.name --subscription $SubscriptionId --include-inherited --include-groups --output json 2>$null | ConvertFrom-Json | ||
| } else { | ||
| $azureRoles = az role assignment list --assignee-object-id $currentUserId --subscription $SubscriptionId --include-inherited --include-groups --output json 2>$null | ConvertFrom-Json | ||
| } |
| Write-Status "Azure: MISSING required Azure roles for Step A" "fail" | ||
| if (-not $hasUAA) { | ||
| Write-Host " Missing: User Access Administrator" | ||
| Write-Host " Remediation: az role assignment create --assignee-object-id $currentUserId --assignee-principal-type User --role 'User Access Administrator' --scope /subscriptions/$SubscriptionId" |
| } | ||
| if (-not $hasSentinelContrib) { | ||
| Write-Host " Missing: Microsoft Sentinel Contributor" | ||
| Write-Host " Remediation: az role assignment create --assignee-object-id $currentUserId --assignee-principal-type User --role 'Microsoft Sentinel Contributor' --scope /subscriptions/$SubscriptionId" |
Comment on lines
+69
to
+81
| try { | ||
| $response = Invoke-RestMethod -Uri $uri -Method Post -Headers $headers -Body $body | ||
| Write-Host "✅ Data ingested successfully!" | ||
| } catch { | ||
| $statusCode = $_.Exception.Response.StatusCode.value__ | ||
| if ($statusCode -eq 204) { | ||
| Write-Host "✅ Data ingested successfully (204 No Content)." | ||
| } else { | ||
| Write-Host "❌ Ingestion failed: $($_.Exception.Message)" | ||
| Write-Host " Status: $statusCode" | ||
| exit 1 | ||
| } | ||
| } |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| "rules": [{"id": r["id"], "status": r["status"]} for r in rules_log], | ||
| "renameMapApplied": rename_log, | ||
| }, | ||
| "scuEstimate": "__SCU_TBD__", |
| "renameMapApplied": rename_log, | ||
| }, | ||
| "scuEstimate": "__SCU_TBD__", | ||
| "partnerCenterStatus": "draft", |
| import argparse | ||
| import datetime | ||
| import json | ||
| import os |
| import re | ||
| import subprocess | ||
| import sys | ||
| from io import StringIO |
| fixed = collapsed | ||
| if fixed != orig: | ||
| # Preserve original block-scalar style on assignment | ||
| style = getattr(orig, "_yaml_format", None) |
Author
|
@v-shukore , @v-atulyadav , Could you please let me know if you need any further details to approve the PR? Please note that I have reviewed all the comments from Copilot, they stem from Copilot not being able to run its full tool suite and reflect static assumptions about az REST shapes rather than actual CLI behavior. We have verified the tool locally in VS Code and tested end-to-end with external ISVs/partners across multiple live-tenant sessions — all phases work as expected. The documented Azure CLI prerequisite (2.60+) and other required tools to the run agent, already handles every scenario the scripts rely on. |
Author
|
@v-shukore, Below are the screenshots of using the agent from VS code chat. Please let me know if you need any further details for approving the PR. 
Security Copilot Agent Use Case Ideation using the Tool: 
Data Lake Onboarding using the Tool and progress to Data Ingestion phase: 
Data Ingestion script triggered and successfully executed by Agent: 
Validation script run successfully by the Agent: 
End to End outputs across phases when using the Agent: 
|
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.
Overview
This PR adds a new tool under
Tools/Sentinel-Data-Connector-and-Agent-Builder/: aworkspace-level VS Code GitHub Copilot Chat agent that walks an ISV / partner developer
end-to-end through onboarding to Microsoft Sentinel Data Lake and shipping a
Security Copilot agent (or a Custom MCP tool collection) on top of it — in a single chat.
The agent is delivered as GitHub Copilot custom instructions + skills
(
.github/copilot-instructions.mdand.github/skills/) plus a set of cross-platformPowerShell / Python helper scripts. There is no marketplace extension to install — a
developer sparse-checks-out this folder, opens it as the VS Code workspace root, and Copilot
Chat auto-loads the agent.
It guides developers through a phased workflow:
Azure-Sentinel/Solutions/,classifies it (
custom-table/native-cef-syslog/native-builtin), or kicks off a customconnector build when none exists.
Logs Ingestion API so agents are testable in later phases.
lints them, and validates every KQL block against the data lake.
or generates a deployment guide for customer-tenant rollout.
All Azure-mutating steps are gated behind explicit confirmation, and the tool keeps no secrets in
source — per-tenant / per-session runtime artifacts are
.gitignored.Why it belongs in
Tools/It is a self-contained developer enablement tool for the Sentinel platform — it consumes
Azure-Sentinel/Solutions/connector content as an input and helps partners build on top ofSentinel Data Lake + Security Copilot. It adds no analytic rules, parsers, hunting queries,
or workbooks, and touches no existing files — it is purely additive under a single new folder.
What's included
.github/copilot-instructions.md+.github/skills/— the agent definition (personality, phase rules, lint rules).scripts/— PowerShell + Python helpers (prerequisite checks, data-lake validation, ingestion engine,KQL instruction validator, SCU cost-control automation, Partner Center packager).
knowledge/— runtime reference guides the agent reads.templates/,config/(templates +.gitkeeponly),infra/— supporting assets.README.md— setup, prerequisites, and usage.Change(s):
Tools/Sentinel-Data-Connector-and-Agent-Builder/(Copilot agent instructions + skills + helper scripts + docs). No existing files are modified.
Reason for Change(s):
build + validate + publish Security Copilot agents and Custom MCP tool collections on the Sentinel platform.
Version Updated:
Testing Completed:
tenant across multiple ISVs and multiple VS Code Copilot Chat sessions — connector discovery,
data-lake onboarding, attack-scenario sample-data ingestion (Logs Ingestion API), MCP schema
verification, agent-instruction authoring + KQL validation, and packaging. Helper scripts run on
PowerShell 7+ / Python 3.10+, and the optional Azure-side SCU auto-delete automation was deployed
and validated in-tenant. The tool adds no KQL/YAML detection content to the repo's validation surface.
Checked that the validations are passing and have addressed any issues that are present:
have nothing new to validate in this folder. The added files are docs, scripts, and templates only.