Hello @Arek and others, The product team as identified the underlying issue and is working to have it fixed February 20th. Apologies for the inconvenience this has caused.
Azure Cloud - creating Automation Account - Bad request error
I found a problem while creating an Automation Account either with use of Azure Portal or with use of Power Shell. I get the same error "Bad request" - description "Message":"Something went wrong. Please contact support."} (code: BadRequest)" The command I use in PowerShell is New-AzAutomationAccount -Name 'Azure-AA' -Location 'EastUS' -ResourceGroupName 'Azure-AA-RG'
I can't figure out what is wrong and why I can't create an Automation Account?
Azure Automation
-
Mohit Kumar 31 Reputation points
2024-01-30T05:18:40.6666667+00:00 Getting the following error while trying to create a New Automation Account via Azure portal, no added parameters or values i have used, just selecting the RG and entering the name of AM and then clicking review+create - {"code":"BadRequest","message":"{"Message":"Something went wrong. Please contact support."}"}. Tried multiple time but still encountering the same error.
-
Arek 45 Reputation points
2024-01-31T10:06:31.7366667+00:00 Thank you
-
Ryan Hill 25,821 Reputation points • Microsoft Employee
2024-02-01T15:01:32.9733333+00:00 @Mohit Kumar @Arek you're not the only ones. I'm working to escalate this issue. Please email your subscription id and a link to this post to AzCommunity[at]microsoft[dot]com ATTN: Ryan.
-
Val Gurariy 5 Reputation points
2024-02-01T15:14:40.69+00:00 I have the same issue since 4-5 days ago, exactly the same generic error message of 'Bad request' after creation Error : "
{ "code": "BadRequest", "message": "{\"Message\":\"Something went wrong. Please contact support.\"}" }
"
-
Jeoffrey NGO 0 Reputation points
2024-02-04T21:11:37.74+00:00 I have exactly the same problem, I will send the email as advised, I hope the problem will be solved soon...
-
Andrew Reeves 0 Reputation points
2024-02-12T16:45:03.06+00:00 I have exactly the same and really need this working to create an automated sharepoint site template script.
-
HARISHANKAR B 0 Reputation points
2024-02-17T12:25:36.4833333+00:00 I am trying to build "Azuregoat" using the terraform command "terraform apply --auto--approve" And I am getting similar error. "Error: creating Automation Account: (Name "dev-automation-account-appazgoat3429518" / Resource Group "azuregoat_app"): automation.AccountClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="{"Message":"Something went wrong. Please contact support."}"
-
Ryan Hill 25,821 Reputation points • Microsoft Employee
2024-02-18T04:50:54.6633333+00:00 @HARISHANKAR B please see my answer below.
Sign in to comment
2 answers
Sort by: Most helpful
-
Ryan Hill 25,821 Reputation points • Microsoft Employee
2024-02-10T16:27:52.33+00:00 -
Val Gurariy 5 Reputation points
2024-02-12T17:09:16.2033333+00:00 Thank you for the update Ryan
-
Deepak 0 Reputation points
2024-02-19T14:37:06.0466667+00:00 Many thanks. I experience the same issue as well. Hopefully this gets resolved today
-
Ryan Hill 25,821 Reputation points • Microsoft Employee
2024-02-20T18:47:41.53+00:00 The latest update is the fix is rolling out and should be completed in two days.
-
Tec 0 Reputation points
2024-02-22T09:04:08.96+00:00 Still broken
-
Val Gurariy 5 Reputation points
2024-02-22T17:55:42.8166667+00:00 Same, still error. Any update when being fixed?
-
Greg Wolski 0 Reputation points
2024-02-22T22:08:25.8+00:00 I just tried it and it worked! Created automation account after over a month of failing.
-
Ryan Hill 25,821 Reputation points • Microsoft Employee
2024-02-22T22:51:32.0366667+00:00 @Val Gurariy I've received confirmation that the rollout has been completed. Retry your operation and let me know if you encounter any isssues.
-
Troy C 0 Reputation points
2024-02-23T00:07:44.2066667+00:00 I'm still getting the same error. I can confirm it is region-specific. I can create an automation account in the US, for example, but not in Australia. The problem is it is erroring for all regions in Australia preventing me from setting up site recovery and proceeding with deploying our applications to Azure.
New-AzAutomationAccount -Name "testautomationaccount" -Location "Australia East" -ResourceGroupName "ResourceGroup1"
-
-
Jeoffrey NGO 0 Reputation points
2024-02-23T23:37:03.8233333+00:00 Hi, I have still the same error but not in all of the suscriptions of my account. For one of them (the one where it's must be deployed) it is not working: {"Message":"Something went wrong. Please contact support."}
-
Ryan Hill 25,821 Reputation points • Microsoft Employee
2024-02-24T04:57:22.4633333+00:00 @Jeoffrey NGO I believe this your issue is separate because of the different error message. Can you create a new post and tag me in a comment please?
-
Salvador Doménech 0 Reputation points
2024-02-26T12:44:09.2766667+00:00 Hello, apparently I have the same error as Jeoffrey NGO, since I still can't create an automation account, The error details shown to me are:
Could you explain to me how to fix it, I've been with this problem since the beginning of the post. Thank you
-
Ryan Hill 25,821 Reputation points • Microsoft Employee
2024-02-28T00:47:34.77+00:00 @Salvador Doménech send me an email to AzCommunity[at]microsoft[dot]com ATTN: Ryan with your subscription id and link to this post. Could be something specific with your subscription.
-
Tehc-4212 0 Reputation points
2024-03-03T21:35:23.1066667+00:00 Still broken.
{ "code": "BadRequest", "message": "{\"Message\":\"Something went wrong. Please contact support.\"}" }
-
Jeoffrey NGO 0 Reputation points
2024-03-03T22:00:33.22+00:00 Hi @Ryan Hill
I just sent you an email to AzCommunity[at]microsoft[dot]com ATTN: Ryan with my subscription id and link to this post.
I executed the following command:
az automation account create --automation-account-name sntpp-automation --resource-group sntpp-mgmt --sku Free --debug
Subscription in France Central (command is failing in a single of all of my subscriptions)
I hope you can do something as I am still facing the same error than @Salvador Doménech:
Thansk!
-
Ryan Hill 25,821 Reputation points • Microsoft Employee
2024-03-05T23:04:58.9566667+00:00 @Jeoffrey NGO check @Troy C's response down below, see if that workaround resolves your issue.
Sign in to comment -
-
Troy C 0 Reputation points
2024-03-03T21:41:46.3633333+00:00 If it's any help to people still experiencing this issue: I was advised by Microsoft that the problem was due to my subscription originally being a free trial.
To get around the problem, I had to create a brand new subscription that was Pay-as-you-go from the beginning and delete the other subscription. Then the error went away.