Merge pull request #287318 from mumian/0925-max-variable

Update the variable limit

Author: prmerger-automator[bot]

articles/azure-resource-manager/bicep/variables.md

@@ -3,7 +3,7 @@ title: Variables in Bicep
 description: Describes how to define variables in Bicep
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 08/20/2024
+ms.date: 09/25/2024
 ---
 
 # Variables in Bicep
@@ -12,7 +12,7 @@ This article describes how to define and use variables in your Bicep file. You u
 
 Resource Manager resolves variables before starting the deployment operations. Wherever the variable is used in the Bicep file, Resource Manager replaces it with the resolved value.
 
-You're limited to 256 variables in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
+You're limited to 512 variables in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
 
 ## Define variables
 

articles/azure-resource-manager/templates/best-practices.md

@@ -3,7 +3,7 @@ title: Best practices for templates
 description: Describes recommended approaches for authoring Azure Resource Manager templates (ARM templates). Offers suggestions to avoid common problems when using templates.
 ms.topic: best-practice
 ms.custom: devx-track-arm-template
-ms.date: 09/22/2023
+ms.date: 09/25/2024
 ---
 # ARM template best practices
 
@@ -16,7 +16,7 @@ Limit the size of your template to 4 MB, and each resource definition to 1 MB. T
 You're also limited to:
 
 * 256 parameters
-* 256 variables
+* 512 variables
 * 800 resources (including [copy count](copy-resources.md))
 * 64 output values
 * 10 unique locations per subscription/tenant/management group scope