Skip to content

Commit bb35c45

Browse files
committed
added new article and updated TOC
1 parent 4ce68c6 commit bb35c45

File tree

2 files changed

+59
-0
lines changed

2 files changed

+59
-0
lines changed

articles/automation/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,8 @@
5959
href: automation-runbook-types.md
6060
- name: Automation Runtime environment
6161
href: runtime-environment-overview.md
62+
- name: Azure Automation limits and quotas
63+
href: automation-subscription-limits-faq.md
6264
- name: PowerShell DSC
6365
href: /powershell/dsc/overview
6466
- name: Automation network configuration details
Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
title: Azure Automation subscription limits and quotas
3+
description: This article provides automation subscription and service limits and includes answers to frequently asked questions.
4+
services: automation
5+
ms.topic: faq
6+
ms.date: 12/04/2024
7+
#Customer intent: As an implementer, I want answers to various questions.
8+
---
9+
10+
# Azure Automation limits and quotas
11+
12+
Azure Automation will soon revise its Service and Subscription limits to ensure fair distribution of cloud resources across all customers. This change is another step to improve the reliability and performance of the service while optimizing resource utilization. Since the resource requirements vary across organizations and evolve over time, we aim to empower customers to configure their quotas based on actual usage. [Learn more](https://techcommunity.microsoft.com/blog/AzureGovernanceandManagementBlog/azure-automation-is-revising-service-and-subscription-limits/4351067).
13+
14+
## Revised limits
15+
16+
For more information on the current service and subscription limits, see [Automation limits](../azure-resource-manager/management/azure-subscription-service-limits#process-automation).
17+
18+
The following limits would be changed:
19+
- Maximum number of Automation accounts in a subscription in a region
20+
- Maximum number of concurrent running jobs at the same instance of time per Automation account
21+
22+
You will get an error message when you exceed the limits mentioned below.
23+
24+
**Resource** | **Limit** | **Notes** |
25+
|---|--- | --- |
26+
|Maximum number of active Automation accounts in a subscription in a region | 10 </br></br> 2 </br></br></br> 1 | Enterprise and CSP subscriptions would be able to create accounts in any of the [regions supported](https://azure.microsoft.com/pricing/details/automation/) by the service. </br> Pay-as-you-go, Sponsored, MSDN, MPN, Azure Pass subscriptions can create Automation accounts in any of the [regions supported](https://azure.microsoft.com/pricing/details/automation/) by the service. </br> Free trial, Azure for Student, Azure in Open subscriptions can create only one Automation account per region per subscription. Allowed list of regions: EastUS, EastUS2, WestUS, NorthEurope, SoutheastAsia, and JapanWest2 |
27+
|Maximum number of concurrent running jobs at the same instance of time per Automation account per region | 50 </br> 10 </br> 5 | Enterprise and CSP subscriptions </br> Pay-as-you-go, Sponsored, MSDN, MPN, Azure Pass subscriptions </br> Free trial, Azure for Student, Azure in Open subscriptions.|
28+
29+
30+
## Frequently asked questions
31+
32+
**When will the new limits come into effect?**
33+
34+
New limits would be effective starting 7th January 2025 across all commercial regions. Your patience during the transition period is appreciated.
35+
36+
**How do I check my current resource usage?**
37+
38+
You will be able to check your usage of Automation accounts and concurrently running jobs through Quotas service on Azure Portal or by creating a support request under the category ‘Service and Subscription limits (Quotas)’. Portal would be enabled once deployment starts in January 2025.
39+
40+
**My current usage is more than the revised limits. What should I do?**
41+
42+
Rest assured that your current usage of both resources - Automation accounts and concurrently running jobs - will be honored and will not be impacted. For example, consider you are an Enterprise customer. Your new limit is 10 Automation accounts and current usage is 12 accounts. Even though your usage is higher than the new limit, your usage of 12 accounts would be honored and then considered as your new limit. When you exceed the new limit of 12 accounts, you would get an error.
43+
44+
**I need more resources than my current limits. What should I do?**
45+
46+
You will be able to request for quota increase and decrease based on your changing business requirements. Once the changes are deployed, you will be able to check your current usage, current limit and request for quota changes by creating a support request under the category *Service and Subscription limits (Quotas) for Azure Automation*. Detailed steps to request for quota changes would be shared once deployment starts in January 2025.
47+
48+
**How do quota requests impact my subscription’s billing?**
49+
50+
Support requests for quota changes do not have any additional impact on your subscription billing. You can use your existing support plan to request for quota changes.
51+
52+
## Next steps
53+
54+
If your question isn't answered here, you can refer to the following sources for more questions and answers.
55+
56+
- [Azure Automation](/answers/topics/azure-automation.html)
57+
- [Feedback forum](https://feedback.azure.com/d365community/forum/721a322e-bd25-ec11-b6e6-000d3a4f0f1c)

0 commit comments

Comments
 (0)