| author | mumian |
|---|---|
| ms.service | azure-resource-manager |
| ms.topic | include |
| ms.date | 10/25/2024 |
| ms.author | jgao |
| Resource | Limit |
|---|---|
| Resources per resource group | Resources aren't limited by resource group. Instead, they're limited by resource type in a resource group. See next row. |
| Resources per resource group, per resource type | 800 - Some resource types can exceed the 800 limit. See Resources not limited to 800 instances per resource group. |
| Deployments per resource group in the deployment history | 8001 |
| Resources per deployment | 800 |
| Management locks per unique scope | 20 |
| Number of tags per resource or resource group | 50 |
| Tag key length | 512 |
| Tag value length | 256 |
1Deployments are automatically deleted from the history as you near the limit. Deleting an entry from the deployment history doesn't affect the deployed resources. For more information, see Automatic deletions from deployment history.
| Value | Limit |
|---|---|
| Parameters | 256 |
| Variables | 256 |
| Resources (including copy count) | 800 |
| Outputs | 64 |
| Template expression | 24,576 chars |
| Resources in exported templates | 200 |
| Template size | 4 MB |
| Resource definition size | 1 MB |
| Parameter file size | 4 MB |
You can exceed some template limits by using a nested template. For more information, see Use linked templates when you deploy Azure resources. To reduce the number of parameters, variables, or outputs, you can combine several values into an object. For more information, see Objects as parameters.
You may get an error with a template or parameter file of less than 4 MB, if the total size of the request is too large. For more information about how to simplify your template to avoid a large request, see Resolve errors for job size exceeded.