Merge pull request #212906 from mumian/0928-parameters-limit

add limits

Author: prmerger-automator[bot]

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

@@ -2,12 +2,12 @@
 title: Outputs in Bicep
 description: Describes how to define output values in Bicep
 ms.topic: conceptual
-ms.date: 09/16/2022
+ms.date: 09/28/2022
 ---
 
 # Outputs in Bicep
 
-This article describes how to define output values in a Bicep file. You use outputs when you need to return values from the deployed resources.
+This article describes how to define output values in a Bicep file. You use outputs when you need to return values from the deployed resources. You are limited to 64 outputs in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
 
 ## Define output values
 

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

@@ -4,7 +4,7 @@ description: Describes how to define parameters in a Bicep file.
 author: mumian
 ms.author: jgao
 ms.topic: conceptual
-ms.date: 09/06/2022
+ms.date: 09/28/2022
 ---
 
 # Parameters in Bicep
@@ -15,7 +15,7 @@ Resource Manager resolves parameter values before starting the deployment operat
 
 Each parameter must be set to one of the [data types](data-types.md).
 
-You are limited to 256 parameters. For more information, see [Template limits](../templates/best-practices.md#template-limits).
+You are limited to 256 parameters in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
 
 For parameter best practices, see [Parameters](./best-practices.md#parameters).
 

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

@@ -2,12 +2,12 @@
 title: Declare resources in Bicep
 description: Describes how to declare resources to deploy in Bicep.
 ms.topic: conceptual
-ms.date: 02/04/2022
+ms.date: 09/28/2022
 ---
 
 # Resource declaration in Bicep
 
-This article describes the syntax you use to add a resource to your Bicep file.
+This article describes the syntax you use to add a resource to your Bicep file. You are limited to 800 resources in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
 
 ## Declaration
 

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

@@ -4,7 +4,7 @@ description: Describes how to define variables in Bicep
 author: mumian
 ms.author: jgao
 ms.topic: conceptual
-ms.date: 11/12/2021
+ms.date: 09/28/2022
 ---
 
 # Variables in Bicep
@@ -13,6 +13,8 @@ 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 are limited to 256 variables in a Bicep file. For more information, see [Template limits](../templates/best-practices.md#template-limits).
+
 ## Define variable
 
 The syntax for defining a variable is:

articles/azure-resource-manager/templates/outputs.md

@@ -2,7 +2,7 @@
 title: Outputs in templates
 description: Describes how to define output values in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
-ms.date: 09/16/2022
+ms.date: 09/28/2022
 ms.custom: devx-track-azurepowershell
 ---
 
@@ -15,6 +15,8 @@ The format of each output value must resolve to one of the [data types](data-typ
 > [!TIP]
 > We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [outputs](../bicep/outputs.md).
 
+You are limited to 64 outputs in a template. For more information, see [Template limits](./best-practices.md#template-limits).
+
 ## Define output values
 
 The following example shows how to return a property from a deployed resource.

articles/azure-resource-manager/templates/parameters.md

@@ -2,7 +2,7 @@
 title: Parameters in templates
 description: Describes how to define parameters in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
-ms.date: 09/06/2022
+ms.date: 09/28/2022
 ---
 
 # Parameters in ARM templates
@@ -16,9 +16,9 @@ Each parameter must be set to one of the [data types](data-types.md).
 > [!TIP]
 > We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [parameters](../bicep/parameters.md).
 
-You are limited to 256 parameters. For more information, see [Template limits](./best-practices.md#template-limits).
+You are limited to 256 parameters in a template. For more information, see [Template limits](./best-practices.md#template-limits).
 
-For parameter best practices, see [Parameters](./best-practices.md#parameters). 
+For parameter best practices, see [Parameters](./best-practices.md#parameters).
 
 ## Minimal declaration
 

articles/azure-resource-manager/templates/resource-declaration.md

@@ -2,7 +2,7 @@
 title: Declare resources in templates
 description: Describes how to declare resources to deploy in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
-ms.date: 01/19/2022
+ms.date: 09/28/2022
 ---
 
 # Resource declaration in ARM templates
@@ -12,6 +12,8 @@ To deploy a resource through an Azure Resource Manager template (ARM template),
 > [!TIP]
 > We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [resource declaration](../bicep/resource-declaration.md).
 
+You are limited to 800 resources in a template. For more information, see [Template limits](./best-practices.md#template-limits).
+
 ## Set resource type and version
 
 When adding a resource to your template, start by setting the resource type and API version. These values determine the other properties that are available for the resource.

articles/azure-resource-manager/templates/syntax.md

@@ -2,7 +2,7 @@
 title: Template structure and syntax
 description: Describes the structure and properties of Azure Resource Manager templates (ARM templates) using declarative JSON syntax.
 ms.topic: conceptual
-ms.date: 07/18/2022
+ms.date: 09/28/2022
 ---
 
 # Understand the structure and syntax of ARM templates
@@ -48,7 +48,7 @@ Each element has properties you can set. This article describes the sections of
 
 ## Parameters
 
-In the `parameters` section of the template, you specify which values you can input when deploying the resources. You're limited to 256 parameters in a template. You can reduce the number of parameters by using objects that contain multiple properties.
+In the `parameters` section of the template, you specify which values you can input when deploying the resources. You're limited to [256 parameters](../management/azure-subscription-service-limits.md#general-limits) in a template. You can reduce the number of parameters by using objects that contain multiple properties.
 
 The available properties for a parameter are:
 
@@ -87,7 +87,7 @@ In Bicep, see [parameters](../bicep/file.md#parameters).
 
 ## Variables
 
-In the `variables` section, you construct values that can be used throughout your template. You don't need to define variables, but they often simplify your template by reducing complex expressions. The format of each variable matches one of the [data types](data-types.md).
+In the `variables` section, you construct values that can be used throughout your template. You don't need to define variables, but they often simplify your template by reducing complex expressions. The format of each variable matches one of the [data types](data-types.md). You are limited to [256 variables](../management/azure-subscription-service-limits.md#general-limits) in a template.
 
 The following example shows the available options for defining a variable:
 
@@ -171,7 +171,7 @@ In Bicep, user-defined functions aren't supported. Bicep does support a variety
 
 ## Resources
 
-In the `resources` section, you define the resources that are deployed or updated.
+In the `resources` section, you define the resources that are deployed or updated. You are limited to [800 resources](../management/azure-subscription-service-limits.md#general-limits) in a template.
 
 You define resources with the following structure:
 
@@ -259,7 +259,7 @@ In Bicep, see [resources](../bicep/file.md#resources).
 
 ## Outputs
 
-In the `outputs` section, you specify values that are returned from deployment. Typically, you return values from resources that were deployed.
+In the `outputs` section, you specify values that are returned from deployment. Typically, you return values from resources that were deployed. You are limited to [64 outputs](../management/azure-subscription-service-limits.md#general-limits) in a template.
 
 The following example shows the structure of an output definition:
 

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

@@ -2,7 +2,7 @@
 title: Variables in templates
 description: Describes how to define variables in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
-ms.date: 01/19/2022
+ms.date: 09/28/2022
 ---
 
 # Variables in ARM templates
@@ -14,6 +14,8 @@ Resource Manager resolves variables before starting the deployment operations. W
 > [!TIP]
 > We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [variables](../bicep/variables.md).
 
+You are limited to 256 variables in a template. For more information, see [Template limits](./best-practices.md#template-limits).
+
 ## Define variable
 
 When defining a variable, you don't specify a [data type](data-types.md) for the variable. Instead provide a value or template expression. The variable type is inferred from the resolved value. The following example sets a variable to a string.