An Azure service that is used to automate, configure, and install updates across hybrid environments.
Hello @Sem van Deventer@Sem van Deventer Thank you for reaching out and for sharing the screenshot.
The error you're seeing is caused by an Azure Automation service-level restriction specific to Free Trial and Azure for Student subscriptions. Regardless of which regions your subscription's Azure Policy allows for general resource deployment, the Azure Automation service enforces its own stricter limit for these subscription types. Automation accounts can only be created in the following regions:
- EastUS
- EastUS2
- WestUS
- NorthEurope
- SoutheastAsia
- JapanWest
This is documented here: Azure Automation subscription limits and quotas
In your case, the regions assigned to your subscription by Azure Policy (polandcentral, swedencentral, uaenorth, switzerlandnorth, germanywestcentral) do not overlap with the Automation-allowed regions listed above which is why you're getting this error even though the portal lets you select those regions during creation.
Please have a look into below provided resolution:
- Check if your subscription policy can be updated: Navigate to Azure Portal → Policy → Authoring → Assignments → "Allowed resource deployment regions" and check whether any of the Automation-allowed regions (e.g.,
NorthEurope,EastUS) are included. If not, and you have the ability to modify the policy, add at least one of those regions. - If you cannot modify the policy : You may need to upgrade your subscription to a Pay-As-You-Go plan, which removes both the region restrictions and the one-Automation-account limit. You can do this from the Azure portal under Subscriptions → Upgrade. Your remaining student credits will still be consumed first before pay-as-you-go billing applies.
An Azure Automation account does not need to be in the same region as the resources it manages. For example, an Automation account in NorthEurope can run runbooks against VMs in SwedenCentral or any other region without any issues.
We have raised support case with Backend Billing team for further assistance on this issue.
I hope this helps clarify the situation. Please let me know if you have any further questions.
Thanks,
Suchitra.