Update D3 Smart SOAR solution to v3.2.0 with new offer ID

[brianbtzhong]

Change(s):

• Updated offer ID from azure-sentinel-solution-d3soar to azure-sentinel-solution-d3smartsoar in SolutionMetadata.json and mainTemplate.json
• Bumped solution version from 3.1.0 to 3.2.0 across all solution files
• Updated support URLs to https://d3security.com/company/contact/
• Added 3.2.0.zip package

Reason for Change(s):

• The previous Partner Center offer was configured as a Managed Application plan type, which does not work with Microsoft Sentinel Content Hub. A new offer has been created with the correct Solution Template plan type, requiring a new offer ID (azure-sentinel-solution-d3smartsoar).

Version Updated:

• Yes — 3.1.0 → 3.2.0

Testing Completed:

• Yes — ARM template deployed and validated via Azure CLI on test instance (subscription 982dc654, resource group d3cyber, workspace d3devcyber). CCP connector pagination verified with CountBasedPaging using $.CommandParams.PageIndex.

Checked that the validations are passing and have addressed any issues that are present:

• Yes

[d3-kdeng]

@v-atulyadav @v-shukore @v-maheshbh We have to publish the solution to Sentinel Content Hub in very recent days , If you have time, please review this commit and merge at an earlier convinience, thanks very much.

[d3-kdeng]

hello, @v-atulyadav could these few changes be merged? anything we need to change? thanks.

[v-maheshbh]

Hi @brianbtzhong

Changing the OfferId will create a new solution identity in Content Hub. This will impact existing customers, as their currently deployed solution will no longer receive updates and may also lead to duplication upon reinstallation. Kindly revert this change to avoid disruption to the customer experience.

Thanks!

[d3-kdeng]

Hi @brianbtzhong

Changing the OfferId will create a new solution identity in Content Hub. This will impact existing customers, as their currently deployed solution will no longer receive updates and may also lead to duplication upon reinstallation. Kindly revert this change to avoid disruption to the customer experience.

Thanks!

@v-maheshbh @v-atulyadav

Thanks for the kind reminder.

btw: @brianbtzhong We are in the same team in D3 working on this. This is an intended change, since the original offer which was created and approved last week only went to the MS marketplace, the offer plan type (Managed Application cannot be changed once published) won't let it get published into Sentinel Content Hub (which is our purpose indeed). Because of this we have to recreate a new offer in the MS Partner Center Portal by using a new offerId with a different plan type so it can appear in Sentinel Content Hub. Otherwise, we wont pull request this change.

Fortunately the previous offer was just createdly for only few days (we haven't noticed any client used it), we will stop the distribution and hide the old offer once this is merged and the new offer is approved. We need have to let all those to be done before April 9th for joining the MISA(Microsoft Intelligent Security Association). Kindly please review and merge it.

Thanks.

[v-maheshbh]

Hi @brianbtzhong

There is a mismatch between the mainTemplate inside the ZIP package and the one outside. Kindly repackage the solution so we can proceed with approval.

Thanks!

[brianbtzhong]

Hi @brianbtzhong

There is a mismatch between the mainTemplate inside the ZIP package and the one outside. Kindly repackage the solution so we can proceed with approval.

Thanks!

Hi @v-maheshbh , I've updated and repackaged the changes. Would you be able to take a look when you get a chance? We're working against a tight deadline, so an earlier review would be a huge help if your schedule allows. Really appreciate your time on this!

[v-maheshbh]

Hi @brianbtzhong
Changing the OfferId will create a new solution identity in Content Hub. This will impact existing customers, as their currently deployed solution will no longer receive updates and may also lead to duplication upon reinstallation. Kindly revert this change to avoid disruption to the customer experience.
Thanks!

@v-maheshbh @v-atulyadav

Thanks for the kind reminder.

btw: @brianbtzhong We are in the same team in D3 working on this. This is an intended change, since the original offer which was created and approved last week only went to the MS marketplace, the offer plan type (Managed Application cannot be changed once published) won't let it get published into Sentinel Content Hub (which is our purpose indeed). Because of this we have to recreate a new offer in the MS Partner Center Portal by using a new offerId with a different plan type so it can appear in Sentinel Content Hub. Otherwise, we wont pull request this change.

Fortunately the previous offer was just createdly for only few days (we haven't noticed any client used it), we will stop the distribution and hide the old offer once this is merged and the new offer is approved. We need have to let all those to be done before April 9th for joining the MISA(Microsoft Intelligent Security Association). Kindly please review and merge it.

Thanks.

We will proceed with approval upon your confirmation.

[v-maheshbh]

Hi @brianbtzhong

Kindly note that the existing solution needs to be deprecated, and the deprecation notification should be sent to the App Assure team. Once this is completed, approval will be provided from Partner Center.

Thanks!

[brianbtzhong]

Hi @brianbtzhong

Kindly note that the existing solution needs to be deprecated, and the deprecation notification should be sent to the App Assure team. Once this is completed, approval will be provided from Partner Center.

Thanks!

Hi @v-maheshbh , thanks for the feedback. Regarding the deprecation of the old offer (azure-sentinel-solution-d3soar), we plan to stop selling the old offer in Partner Center and notify the App Assure team. Could you clarify if there are any additional steps needed on the repo side (e.g. marking files as deprecated, updating ReleaseNotes, etc.), or is the deprecation handled entirely through Partner Center?