Add Major Technology Solution#13788
Conversation
|
There was a problem hiding this comment.
Pull request overview
Adds a new Microsoft Sentinel Solution package for “Major Technology”, including deployment assets for a REST API Poller connector that ingests MajorBuildInvocations into a custom Log Analytics table via DCR/DCE.
Changes:
- Introduces solution metadata + release notes for Content Hub packaging.
- Adds ARM template + CreateUIDefinition + test parameters for deployment.
- Adds connector assets (CCP) including DCR, table schema, connector definition, and polling config.
Reviewed changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated 9 comments.
Show a summary per file
| File | Description |
|---|---|
| Solutions/MajorTechnology/SolutionMetadata.json | Adds Content Hub solution metadata (publisher/offer/categories/dates). |
| Solutions/MajorTechnology/ReleaseNotes.md | Adds initial release notes entry. |
| Solutions/MajorTechnology/Package/testParameters.json | Adds sample deployment parameter values for validation. |
| Solutions/MajorTechnology/Package/mainTemplate.json | Deploys DCE, custom table, DCR, and RestApiPoller connector resources. |
| Solutions/MajorTechnology/Package/createUiDefinition.json | Defines the portal UI used to collect deployment inputs. |
| Solutions/MajorTechnology/Data/Solution_MajorBuildInvocations.json | Declares solution manifest and references connector assets. |
| Solutions/MajorTechnology/Data Connectors/MajorBuildInvocations_CCP/table_MajorBuildInvocations.json | Adds custom table definition used by the connector. |
| Solutions/MajorTechnology/Data Connectors/MajorBuildInvocations_CCP/MajorBuildInvocations_PollingConfig.json | Adds polling configuration for the RestApiPoller connector. |
| Solutions/MajorTechnology/Data Connectors/MajorBuildInvocations_CCP/MajorBuildInvocations_Definition.json | Adds the connector UI definition (CCP) for the connector. |
| Solutions/MajorTechnology/Data Connectors/MajorBuildInvocations_CCP/MajorBuildInvocations_DCR.json | Adds the DCR definition (CCP) including stream + transform. |
| Solutions/MajorTechnology/.gitignore | Adds solution-local ignore rules. |
| "workspace": { | ||
| "type": "string", | ||
| "metadata": { | ||
| "description": "The name of the Log Analytics / Microsoft Sentinel workspace." | ||
| } | ||
| }, | ||
| "workspaceResourceId": { | ||
| "type": "string", | ||
| "metadata": { | ||
| "description": "Full resource ID of the Log Analytics workspace: /subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.OperationalInsights/workspaces/{name}" | ||
| } | ||
| }, | ||
| "MajorBuildAPIKey": { | ||
| "type": "securestring", | ||
| "metadata": { | ||
| "description": "Major.build Bearer API token (begins with MJR_)." | ||
| } | ||
| } |
| "workspace": { | ||
| "value": "YOURWORKSPACENAME" | ||
| }, | ||
| "workspace-location": { | ||
| "value": "eastus" | ||
| }, | ||
| "apiKey": { | ||
| "value": "MJR_yourapikeyhere" | ||
| }, | ||
| "dcrConfig": { | ||
| "value": { | ||
| "dataCollectionEndpoint": "https://your-dce.eastus-1.ingest.monitor.azure.com", | ||
| "dataCollectionRuleImmutableId": "dcr-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" | ||
| } |
| "Data Connectors/MajorBuildInvocations_ConnectorDefinition.json" | ||
| ], | ||
| "CCP": [ | ||
| "Data Connectors/MajorBuildInvocations_ConnectorDefinition.json", | ||
| "Data Connectors/MajorBuildInvocations_PollingConfig.json" |
| "dataType": "MajorBuildInvocations_CL", | ||
| "auth": { | ||
| "type": "APIKey", | ||
| "ApiKey": "[[parameters('apiKey')]", |
| "config": { | ||
| "isWizard": false, | ||
| "basics": { | ||
| "description": "<img src=\"https://www.major.build/favicon.ico\" width=\"75px\" height=\"75px\">\n\n**Note:** Please refer to the following before deploying this solution:\n\n- The connector requires a Major Build API key. Generate one at [app.major.build](https://app.major.build) under **Settings → API Keys**.\n\n- Review the solution [Release Notes](https://github.com/MitchellGulledge3/MajorTechnology/blob/main/MajorBuildInvocations/ReleaseNotes.md).\n\n**Data Connectors:** 1, **Workbooks:** 0, **Analytic Rules:** 0\n\n[Learn more about Microsoft Sentinel](https://aka.ms/azuresentinel) | [Learn more about Solutions](https://aka.ms/azuresentinelsolutionsdoc)", |
| "Author": "Major Technology", | ||
| "Logo": "<img src=\"https://www.major.build/favicon.ico\" width=\"75px\" height=\"75px\">", | ||
| "Description": "The **Major Build AI Invocations** solution for Microsoft Sentinel provides a CCF-based data connector that automatically ingests AI agent invocation records from the [Major Build](https://www.major.build) platform.\n\nEach record captures:\n- **Who** ran the AI agent (user name, email)\n- **What** application and resource integration was used\n- **What data** was accessed (including full SQL query text)\n- **Whether** the invocation succeeded or failed\n- **When** the invocation occurred and from which environment\n\nThis enables security teams to audit AI agent activity, detect anomalous access patterns, and investigate data exposure via AI agents.\n\n**Data Connectors:** 1\n\n**Table:** MajorBuildInvocations_CL\n\n**Poll Interval:** Every 5 minutes", | ||
| "BasePath": "https://raw.githubusercontent.com/MitchellGulledge3/MajorTechnology/main/MajorBuildInvocations", |
| | **Version** | **Date Modified (DD-MM-YYYY)** | **Change History** | | ||
| |-------------|--------------------------------|---------------------------| | ||
| | 1.0.0 | 04-03-2026 | Initial Release | |
| "properties": { | ||
| "networkAcls": { | ||
| "publicNetworkAccess": "Enabled" | ||
| } | ||
| } |
| "workspace": { | ||
| "type": "string", | ||
| "metadata": { | ||
| "description": "The name of the Log Analytics / Microsoft Sentinel workspace." | ||
| } | ||
| }, | ||
| "workspaceResourceId": { | ||
| "type": "string", | ||
| "metadata": { | ||
| "description": "Full resource ID of the Log Analytics workspace: /subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.OperationalInsights/workspaces/{name}" | ||
| } | ||
| }, |
|
Hi @josegironn, please update suggested changes in files and resolve validations failures. Also, package the solution using V3 tool - https://github.com/Azure/Azure-Sentinel/blob/master/Tools/Create-Azure-Sentinel-Solution/V3/README.mdThanks |
|
Hi @josegironn, please update on above comment. Thanks! |
|
Hi, we wanted to check on the status of PR #13788. PR is pending for more than 30 days. Please let us know if you need any assistance to review this PR. Per our standard operating procedures if no response is received in the next 7 business days, we will close this PR. Thank you for your cooperation. |
|
Since we have not received a response in the last 7 days, we are closing your PR #13788 per our standard operating procedures. If you still need support for this issue, you can re-open the PR at any time. If you do re-open, we simply request that you ensure the PR has response to the last request. Thank you for your cooperation. |
Summary
Test plan