Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
JelaniB-sec opened this issue Oct 24, 2024 · 17 comments · Fixed by #11620
Assignees
Labels
Solution Solution specialty review needed

Comments

@JelaniB-sec
Copy link

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.

imageImage

@WVDAdminTF
Copy link

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.

Image

Image

@v-rusraut v-rusraut added the Solution Solution specialty review needed label Oct 28, 2024
@v-rusraut
Copy link
Contributor

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

@JelaniB-sec
Copy link
Author

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

@lussierd16
Copy link

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 added a commit to JelaniB-sec/Azure-Sentinel that referenced this issue Nov 11, 2024
Changed azureAD to Entra ID in an attempt to fix deployment failure. issue Azure#11329

Azure#11329
@JelaniB-sec
Copy link
Author

@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
Copy link
Contributor

Tagging author - @pemontto

@JelaniB-sec
Copy link
Author

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

@a-balde
Copy link

a-balde commented Dec 3, 2024

@v-sudkharat any update on this ?

@v-sudkharat
Copy link
Contributor

@a-balde, Still waiting for the author's response on this issue.

@v-sudkharat
Copy link
Contributor

@a-balde, In addition, we are also checking this issue with our concern team as well, to get it unblocked.

@fishslime
Copy link

Is there a way to manually execute this "deployRules" step? Everything else succeeds except this issue. I've re-tried a dozen times using different parameters.

@JelaniB-sec
Copy link
Author

any update on this? @v-sudkharat

@v-sudkharat
Copy link
Contributor

@JelaniB-sec, We have shared this issue with concern team and team is currently working on troubleshooting of script. Once we get any info on it will update you. Thanks!

javiersoriano added a commit to javiersoriano/Azure-Sentinel that referenced this issue Jan 2, 2025
This modification fixes Azure#11329
@v-sudkharat
Copy link
Contributor

@JelaniB-sec / @a-balde / @fishslime, We have raised the PR with fix, meantime could you please deploy the template from below shared readme file and let us know if still facing the same issue :

File link : -https://github.com/Azure/Azure-Sentinel/blob/762d0ebbcb32de84802a9ec01cd6332eef848d93/Tools/Sentinel-All-In-One/README.md

Image

Many Thanks!

@v-sudkharat
Copy link
Contributor

Hi @fishslime / @a-balde / @JelaniB-sec,
Waiting for your response on above comment. Thanks!

@JelaniB-sec
Copy link
Author

Hi @fishslime / @a-balde / @JelaniB-sec, Waiting for your response on above comment. Thanks!

I was able to get this working by deploying through readme.md

v-atulyadav added a commit that referenced this issue Jan 7, 2025
@a-balde
Copy link

a-balde commented Jan 7, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Solution Solution specialty review needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants