The Deployment fails in 3 different environments with different configuration on the same point - enableSolutionAndAlerts - Create-NewSolutionAndRulesFromList.ps1: line 44

[WVDAdminTF]

Describe the bug
A clear and concise description of what the bug is.

The resource write operation failed to complete successfully, because it reached terminal provisioning state 'failed'. (Code: ResourceDeploymentFailure)
The provided script failed with the following error:
Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 400 (Bad Request).
at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
at , /mnt/azscripts/azscriptinput/Create-NewSolutionAndRulesFromList.ps1: line 44
at , : line 1
at , /mnt/azscripts/azscriptinput/DeploymentScript.ps1: line 310. Please refer to
https://aka.ms/DeploymentScriptsTroubleshoot
for more deployment script information. (Code: DeploymentScriptError)

To Reproduce
Simply deploy the Template it WILL fail.

Expected behavior
The resource write operation failed to complete successfully, because it reached terminal provisioning state 'failed'. (Code: ResourceDeploymentFailure)
The provided script failed with the following error:
Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 400 (Bad Request).
at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
at , /mnt/azscripts/azscriptinput/Create-NewSolutionAndRulesFromList.ps1: line 44
at , : line 1
at , /mnt/azscripts/azscriptinput/DeploymentScript.ps1: line 310. Please refer to
https://aka.ms/DeploymentScriptsTroubleshoot
for more deployment script information. (Code: DeploymentScriptError)

Please refer the Screenshot, @pemontto

Screenshots
If applicable, add screenshots to help explain your problem.
Environment 1

Environment 2

Desktop (please complete the following information):
Azure Portal

Smartphone (please complete the following information):

Additional context

[WVDAdminTF]

Dear @v-rusraut @v-sudkharat please can you let me know if there is any update on the same

[v-sudkharat]

Hi @WVDAdminTF, Could you please provide more info about the in which sentinel solution or its content the deployment is failing?

[WVDAdminTF]

Hi @v-sudkharat could you please be more specific what you would like apart from the information already shared that your repo - https://github.com/Azure/Azure-Sentinel/blob/master/Tools/Sentinel-All-In-One/v2/Scripts/**Create-NewSolutionAndRulesFromList.ps1**

ps1 file line 44 - is causing the deployment to fail.

Please can you deploy the template and confirm that it is working with a screenshot.

[v-sudkharat]

Hi @WVDAdminTF, Are your deploying below ARM template? - https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzure-Sentinel%2Fmaster%2FTools%2FSentinel-All-In-One%2Fv2%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzure-Sentinel%2Fmaster%2FTools%2FSentinel-All-In-One%2Fv2%2FcreateUiDefinition.json

For this ARM template we are having authentication error due to some permissions.

[WVDAdminTF]

Hi @v-sudkharat

yes, this is the template. Please can you advise when are we expected to have the issue fixed.

If there is any workaround for the same, please can you share the steps.

[garybushey]

This was due to some change so that the Get-AzContext did not return the SubscriptionId. Changes have been made to fix this as well as add a delay so that the managed identity's permissions get fully distributed. The changes in the pipeline to get accepted.

[WVDAdminTF]

Hi @garybushey,

Thank you for the update. I will execute the same and let you know if the Deployment completes

[v-sudkharat]

@WVDAdminTF, Please let us know once it done. Thanks!

[v-sudkharat]

Hi @WVDAdminTF, Did you get a chance to check on above suggestion?

[v-sudkharat]

Hi @WVDAdminTF, Gentle Reminder: We are waiting for your response on this issue. If you still need to keep this issue active, please respond to it in the next 2 days. If we don't receive a response by 22-10-2024 date, we will be closing this issue.
Thanks!