Environment failing to Deploy - enableSolutionAndAlerts - Create-NewSolutionAndRulesFromList.ps1: line 44

[JelaniB-sec]

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.

image

[WVDAdminTF]

Hi @JelaniB-sec
please do not expect any change since this issue is existing since 1 week of September, some random person will respond to you in 1-2 weeks to try again, with doing any actual fixes.

[v-rusraut]

Hi @WVDAdminTF , Is your issue resolved, or did you make any changes during deployment to resolve it?

[JelaniB-sec]

@v-rusraut yep still experiencing this issue on my end fyi

[lussierd16]

I had this same issue when I would run this and passing a parameters file. I fixed this by changing one of the inputs for the "enabelSolutions1P" to "Entra ID" instead of "Azure AD". I found that on some old tenants "Azure AD" works but with newer tenants it needs "Entra ID".

[JelaniB-sec]

@lussierd16 Can you provide some more clarity on where you changed the input?
I added a commit that was intended to use that naming convention change, but still experiencing the same issue.
JelaniB-sec@0436573

Any further help would be greatly appreciated

[v-sudkharat]

Tagging author - @pemontto

[JelaniB-sec]

@v-sudkharat thank you, I will await further correspondance