Publishing New Solution Versions in MS Sentinel

Omkar Jadhav 0 Reputation points
2025-06-21T04:57:48.14+00:00

Publishing a new MS Sentinel solution version requires specific updates to JSON and related project files. Beyond general code modifications, what precise changes are necessary within these configuration files to ensure successful deployment and versioning?

Azure AI Language
Azure AI Language
An Azure service that provides natural language capabilities including sentiment analysis, entity extraction, and automated question answering.
520 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Saideep Anchuri 9,425 Reputation points Microsoft External Staff Moderator
    2025-06-21T17:29:44.19+00:00

    Hi Omkar Jadhav

    To publish a new version of a Microsoft Sentinel solution, you need to make specific updates to the JSON and related project files.

    Here are some steps:

    1. Version Number: Update the version number in the configuration files to reflect the new version. This version number should match the latest approved package version in GitHub.
    2. Package File: Ensure that the package file (zip) uploaded corresponds to the new version number. The package must include the updated createUiDefinition.json and mainTemplate.json files.
    3. Plan Configuration: In the plan setup, ensure that the version number is updated to the new version you are deploying. This is crucial for the correct listing and functioning of the solution in the Azure Marketplace.
    4. Technical Configuration: When creating or updating the plan, make sure to upload the matching package zip file that contains the updated files and reflects the new version number.

    Kindly refer below link: publish-sentinel-solutions

    Thank You.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.