Skip to content

Commit eba004e

Browse files
committed
update resource group limit error
1 parent 9f7f77a commit eba004e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/azure-resource-manager/templates/error-invalid-template.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Invalid template errors
33
description: Describes how to resolve invalid template errors when deploying Azure Resource Manager templates.
44
ms.topic: troubleshooting
5-
ms.date: 03/08/2018
5+
ms.date: 05/22/2020
66
---
77
# Resolve errors for invalid template
88

@@ -109,7 +109,7 @@ Getting the segments right can be tricky with Resource Manager types that are ap
109109

110110
## Solution 3 - parameter is not valid
111111

112-
If you provide a parameter value that is not one of the allowed values, you receive a message similar to the following error:
112+
If you provide a parameter value that isn't one of the allowed values, you receive a message similar to the following error:
113113

114114
```
115115
Code=InvalidTemplate;
@@ -124,7 +124,7 @@ Double check the allowed values in the template, and provide one during deployme
124124

125125
## Solution 4 - Too many target resource groups
126126

127-
If you specify more than five target resource groups in a single deployment, you receive this error. Consider either consolidating the number of resource groups in your deployment, or deploying some of the templates as separate deployments. For more information, see [Deploy Azure resources to more than one subscription or resource group](cross-resource-group-deployment.md).
127+
You may see this error in earlier deployments because you were limited to five target resource groups in a single deployment. In May 2020, that limit was increased to 800 resource groups. For more information, see [Deploy Azure resources to more than one subscription or resource group](cross-resource-group-deployment.md).
128128

129129
<a id="circular-dependency" />
130130

@@ -137,7 +137,7 @@ To solve a circular dependency:
137137
1. In your template, find the resource identified in the circular dependency.
138138
2. For that resource, examine the **dependsOn** property and any uses of the **reference** function to see which resources it depends on.
139139
3. Examine those resources to see which resources they depend on. Follow the dependencies until you notice a resource that depends on the original resource.
140-
5. For the resources involved in the circular dependency, carefully examine all uses of the **dependsOn** property to identify any dependencies that are not needed. Remove those dependencies. If you are unsure that a dependency is needed, try removing it.
140+
5. For the resources involved in the circular dependency, carefully examine all uses of the **dependsOn** property to identify any dependencies that aren't needed. Remove those dependencies. If you're unsure that a dependency is needed, try removing it.
141141
6. Redeploy the template.
142142

143143
Removing values from the **dependsOn** property can cause errors when you deploy the template. If you get an error, add the dependency back into the template.

0 commit comments

Comments
 (0)