MicrosoftHey Ely_Abramovitch , this solution works fine for me when the subscription is not a new one, but if I want to use it on a virgin subscription I get an internal server error.
I use ARM template (subscriptionDeploymentTemplate.json) to deploy a resource group, then create a LAW in it and then enable Sentinel on it. When I use the older solution (Microsoft.OperationsManagement/solutions) it works just fine, I can deploy the above-mentioned resources. But if I try to use the new solution (Microsoft.OperationalInsights/workspaces/providers/onboardingStates) then I get this:
{
"status": "Failed",
"error": {
"code": "InternalServerError",
"message": "Internal server error"
}
}
The resource group is still deployed, I can also see the LAW being deployed, but the Sentinel is not enabled because of this error.
I assume this is not a normal behavior. If needed I can share my code somewhere.
