Sentinel Deployment Fix

[Springstone]

Overview/Summary

This pull request contains changes to the eslzArm/eslzArm.json and eslzArm/subscriptionTemplates/logAnalyticsWorkspace.json files. The changes mainly revolve around the removal of the enableSecuritySolution parameter and related deployment references. Additionally, there is an update to the API version in the logAnalyticsWorkspace.json file.

Removal of enableSecuritySolution:

• eslzArm/eslzArm.json: Removed the enableSecuritySolution parameter and its allowed values.
• eslzArm/eslzArm.json: Removed the monitoringSolutions deployment URI.
• eslzArm/eslzArm.json: Removed the monitoringSolutionsDeploymentName variable.
• eslzArm/eslzArm.json: Removed the monitoringSolutionsLiteDeploymentName variable.
• eslzArm/eslzArm.json: Removed the deployment block for Sentinel to Log Analytics workspace.
• eslzArm/eslzArm.json: Removed the deployment block for Sentinel to the Log Analytics workspace for the ES Lite.

Removal of logAnalyticsSolutions.json:

• eslzArm/subscriptionTemplates/logAnalyticsSolutions.json: The entire file has been removed.

API version update:

• eslzArm/subscriptionTemplates/logAnalyticsWorkspace.json: Updated the API version for the deployment.

Testing URLs

Azure Public

[jtracey93]

@arjenhuitema can you confirm none of the solutions for LAW are needed anymore?

[Springstone]

@arjenhuitema can you confirm none of the solutions for LAW are needed anymore?

None are currently used. Everything was commented out except the old way of deploying Sentinel.

[arjenhuitema]

@arjenhuitema can you confirm none of the solutions for LAW are needed anymore?

Correct, there is no need to deploy any of the legacy solutions anymore. Sentinel was the last one.

Note that the ChangeTracking solution is still installed but this is done automatically as part of the CT DCR deployment.