Automation Account Create Issue

Abdullah ÇELEBİ 5 Reputation points
2024-01-13T17:40:37.25+00:00

Hello everyone, I am using a scheduled runbook via Powershell in my Azure account. But recently my runbooks were showing as queued. I thought there might be a problem with my automation account and I wanted to delete my automation account and add it again. After deleting my Automation account, I could never add it back. Currently, I cannot create an automation account from any region except "South Africa West". I get an error saying "Something went wrong. Please contact support. Click here for details" and my automation account cannot be deployed. I thought there might be a problem with my account or my Azure account, so I opened a new account. However, I could not add a runbook from any region there either.

Azure Automation
Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
1,120 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dillon Silzer 54,636 Reputation points
    2024-01-13T20:42:38.86+00:00

    Hi Abdullah,

    This seems like it is more of an account issue.

    I'd recommend opening a ticket with Azure Support:

    https://azure.microsoft.com/en-ca/support/create-ticket

    If this is helpful please accept answer.

  2. AnuragSingh-MSFT 20,016 Reputation points
    2024-01-17T09:05:28.0133333+00:00

    Abdullah ÇELEBİ, thank you for posting this question on Microsoft Q&A.

    As I notice from the error message provided above, you have created both - the automation account and the resource group with the name "australiacentral".

    This seems to be causing the issue as "australiacentral" is the location name (sort of reserved for internal use in Azure). I tried to replicate the issue by creating a resource group with this name and then created Azure Automation account in this resource group and it always fails. When the resource group name is something else, not internally used by Azure, it works as expected.

    Here are the suggestions that can be followed to resolve this issue:

    1. Create a resource group with a non-reserved/internal azure keyword (like "australiacentral")
    2. Create an automation account with a different name as well, than using the reserved keywords.

    In case you are still facing this issue, you may review the activity logs to try to get some more details of issues related to resource provisioning. You can access the activity log by searching for "Monitor" in Azure portal --> "Activity log" from resource menu.

    In case the above steps still do not help you resolve this issue, as Dillon suggested in his answer, please reach out to Azure Support for more information about this failure as backend logs will be required to be reviewed to figure out the cause.

    Hope this helps.

    If the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.