update

Author: mumian

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

@@ -106,29 +106,29 @@ In a module, you can specify a scope that is different than the scope for the re
 
 ## Decorator
 
-You can add one or more decorators for each of the following element:
+You can add one or more decorators for each of the following elements:
 
-* Parameters
-* Variables
-* Resources
-* Modules
-* Ouputs
-* Types
+* [Parameter](#parameters)
+* [Variable](#variables)
+* [Resource](#resources)
+* [Module](#modules)
+* [Output](#outputs)
+* [Type](#types)
 
 | Decorator | Apply to element | Apply to data type | Argument | Description |
 | --------- | ---- | ----------- | ------- |
 | allowed | [parameter](./parameters.md#allowed-values) | all | array | Use this decorator to make sure the user provides correct values. This decorator is only permitted on `param` statements. To declare that a property must be one of a set of predefined values in a [`type`](./user-defined-data-types.md) or [`output`](./outputs.md) statement, use [union type syntax](./data-types.md#union-types). Union type syntax can also be used in `param` statements.|
 | batchSize |[resource](./resource-declaration.md#batchsize), [module](./modules.md#batchsize)| N/A | integer | Set up instances to deploy sequentially. |
-| description | [parameter](./parameters.md#description), [variable](./variables.md#description), [resource](./resource-declaration.md#description), [module](./modules.md#description), [output](./outputs.md#description), [user-defined data type](./user-defined-data-types.md#description) | all | string | Text that explains how to use the element. |
-| discriminator | parameter | object | string | Use this decorator to ensure the correct subclass is identified and managed. For more information, see [Custom-tagged union data type](./data-types.md#custom-tagged-union-data-type).|
-| export | variable, type, function ||||
-| maxLength | parameter | array, string | int | The maximum length for string and array parameters. The value is inclusive. |
-| maxValue | parameter | int | int | The maximum value for the integer parameter. This value is inclusive. |
-| metadata | parameter | all | object | Custom properties to apply to the parameter. Can include a description property that is equivalent to the description decorator. |
-| minLength | parameter | array, string | int | The minimum length for string and array parameters. The value is inclusive. |
-| minValue | parameter | int | int | The minimum value for the integer parameter. This value is inclusive. |
-| sealed | parameter, type, output | object | none | Elevate [BCP089](./diagnostics/bcp089.md) from a warning to an error when a property name of a use-define data type is likely a typo. For more information, see [Elevate error level](./user-defined-data-types.md#elevate-error-level). |
-| secure | parameter | string, object | none | Marks the parameter as secure. The value for a secure parameter isn't saved to the deployment history and isn't logged. For more information, see [Secure strings and objects](data-types.md#secure-strings-and-objects). |
+| description | [parameter](./parameters.md#description), [variable](./variables.md#description), [resource](./resource-declaration.md#description), [module](./modules.md#description), [output](./outputs.md#description), [type](./user-defined-data-types.md#description), [function](./user-defined-functions.md#description) | all | string | Text that explains how to use the element. |
+| discriminator | [parameter](./parameters.md#discriminator, [type](./user-defined-data-types.md#discriminator), [output](./outputs.md#discriminator) | object | string | Use this decorator to ensure the correct subclass is identified and managed. For more information, see [Custom-tagged union data type](./data-types.md#custom-tagged-union-data-type).|
+| export | [variable](./variables.md#export), [type](./user-defined-data-types.md#export), [function](./user-defined-functions.md#export) | all | none| Indicates that the element can be imported by another Bicep file. |
+| maxLength | [parameter](./parameters.md#length-constraints), [output](./outputs.md#length-constraints) | array, string | int | The maximum length for string and array elemenets. The value is inclusive. |
+| maxValue | [parameter](./parameters.md#integer-constraints), [output](./outputs.md#integer-constraints) | int | int | The maximum value for the integer elements. This value is inclusive. |
+| metadata | [parameter](./parameters.md#metadata), [output](./outputs.md#metadata) | all | object | Custom properties to apply to the elements. Can include a description property that is equivalent to the description decorator. |
+| minLength | [parameter](./parameters.md#length-constraints), [output](./outputs.md#length-constraints) | array, string | int | The minimum length for string and array elements. The value is inclusive. |
+| minValue | [parameter](./parameters.md#integer-constraints), [output](./outputs.md#integer-constraints) | int | int | The minimum value for the integer elements. This value is inclusive. |
+| sealed | [parameter](./parameters.md#sealed), [type](./user-defined-data-types.md#sealed), [output](./outputs.md#sealed) | object | none | Elevate [BCP089](./diagnostics/bcp089.md) from a warning to an error when a property name of a use-define data type is likely a typo. For more information, see [Elevate error level](./user-defined-data-types.md#elevate-error-level). |
+| secure | [parameter](./parameters.md#secure-parameters) | string, object | none | Marks the parameter as secure. The value for a secure parameter isn't saved to the deployment history and isn't logged. For more information, see [Secure strings and objects](data-types.md#secure-strings-and-objects). |
 
 ## Parameters
 

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

@@ -25,11 +25,12 @@ Bicep modules are converted into a single Azure Resource Manager template with [
 
 If you would rather learn about modules through step-by-step guidance, see [Create composable Bicep files by using modules](/training/modules/create-composable-bicep-files-using-modules/).
 
-## Definition syntax
+## Define modules
 
 The basic syntax for defining a module is:
 
 ```bicep
+@<decorator>(<argument>)
 module <symbolic-name> '<path-to-file>' = {
   name: '<linked-deployment-name>'
   params: {
@@ -274,7 +275,7 @@ Decorators are written in the format `@expression` and are placed above module d
 
 | Decorator | Argument | Description |
 | --------- | ----------- | ------- |
-| [description](#description) | string | Text that explains how to use the variable.|
+| [description](#description) | string |Provide descriptions for the module.|
 | [batchSize](./bicep-import.md#export-variables-types-and-functions) | none | Set up instances to deploy sequentially. |
 
 Decorators are in the [sys namespace](bicep-functions.md#namespaces-for-functions). If you need to differentiate a decorator from another item with the same name, preface the decorator with `sys`. For example, if your Bicep file includes a parameter named `description`, you must add the sys namespace when using the **description** decorator.

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

@@ -10,7 +10,7 @@ ms.date: 08/20/2024
 
 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
+## Define outputs
 
 The syntax for defining an output value is:
 
@@ -62,7 +62,7 @@ Decorators are written in the format `@expression` and are placed above ouput de
 
 | Decorator | Apply to | Argument | Description |
 | --------- | ---- | ----------- | ------- |
-| [description](#description) | all | string | Text that explains how to use the output. |
+| [description](#description) | all | string | Provide descriptions for the output. |
 | [discriminator](#discriminator) | object | string | Use this decorator to ensure the correct subclass is identified and managed. For more information, see [Custom-tagged union data type](./data-types.md#custom-tagged-union-data-type).|
 | [maxLength](#length-constraints) | array, string | int | The maximum length for string and array outputs. The value is inclusive. |
 | [maxValue](#integer-constraints) | int | int | The maximum value for the integer output. This value is inclusive. |

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

@@ -22,11 +22,12 @@ For parameter best practices, see [Parameters](./best-practices.md#parameters).
 
 If you would rather learn about parameters through step-by-step guidance, see [Build reusable Bicep templates by using parameters](/training/modules/build-reusable-bicep-templates-parameters).
 
-## Declare parameters
+## Define parameters
 
 Each parameter has a name and [data type](data-types.md). Optionally, you can provide a default value for the parameter.
 
 ```bicep
+@<decorator>(<argument>)
 param <parameter-name> <parameter-data-type> = <default-value>
 ```
 

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

@@ -10,7 +10,7 @@ ms.date: 08/20/2024
 
 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
+## Define resources
 
 Add a resource declaration by using the `resource` keyword. You set a symbolic name for the resource. The symbolic name isn't the same as the resource name. You use the symbolic name to reference the resource in other parts of your Bicep file.
 
@@ -66,7 +66,7 @@ Decorators are written in the format `@expression` and are placed above resource
 
 | Decorator | Argument | Description |
 | --------- | ----------- | ------- |
-| [description](#description) | string | Text that explains how to use the variable.|
+| [description](#description) | string | Provide descriptions for the resource. |
 | [batchSize](./bicep-import.md#export-variables-types-and-functions) | none | Set up instances to deploy sequentially. |
 
 Decorators are in the [sys namespace](bicep-functions.md#namespaces-for-functions). If you need to differentiate a decorator from another item with the same name, preface the decorator with `sys`. For example, if your Bicep file includes a parameter named `description`, you must add the sys namespace when using the **description** decorator.
@@ -123,7 +123,7 @@ resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
 }
 ```
 
-## Location
+## Resource location
 
 Many resources require a location. You can determine if the resource needs a location either through intellisense or [template reference](/azure/templates/). The following example adds a location parameter that is used for the storage account.
 
@@ -167,11 +167,11 @@ az provider show \
 
 ---
 
-## Tags
+## Resource tags
 
 You can apply tags to a resource during deployment. Tags help you logically organize your deployed resources. For examples of the different ways you can specify the tags, see [ARM template tags](../management/tag-resources-bicep.md).
 
-## Managed identities for Azure resources
+## Managed identities for resources
 
 Some resources support [managed identities for Azure resources](../../active-directory/managed-identities-azure-resources/overview.md). Those resources have an identity object at the root level of the resource declaration.
 

articles/azure-resource-manager/bicep/user-defined-data-types.md

@@ -12,11 +12,12 @@ Learn how to create user-defined data types in Bicep. For system-defined data ty
 
 [Bicep CLI version 0.12.X or higher](./install.md) is required to use this feature.
 
-## Syntax
+## Define types
 
 You can use the `type` statement to create user-defined data types. In addition, you can also use type expressions in some places to define custom types.
 
 ```bicep
+@<decorator>(<argument>)
 type <user-defined-data-type-name> = <type-expression>
 ```
 
@@ -233,8 +234,8 @@ Decorators are written in the format `@expression` and are placed above the decl
 
 | Decorator | Argument | Description |
 | --------- | ----------- | ------- |
+| [description](#description) | string | Provide descriptions for the user-defined data type. |
 | [discriminator](#discriminator) | string | Use this decorator to ensure the correct subclass is identified and managed. |
-| [description](#description) | string | Text that explains how to use the user-defined data type. |
 | [export](#export) | none | Indicates that the user-defined data type can be imported by another file. |
 | [sealed](#sealed) | none | Elevate [BCP089](./diagnostics/bcp089.md) from a warning to an error when a property name of a use-define data type is likely a typo. For more information, see [Elevate error level](#elevate-error-level).|
 
@@ -352,22 +353,6 @@ output config object = serviceConfig
 
 For more information, see [Custom tagged union data type](./data-types.md#custom-tagged-union-data-type).
 
-## Import types between Bicep files
-
-Only user-defined data types that bear the `@export()` decorator can be imported to other templates.
-
-The following example enables you to import the two user-defined data types from other templates:
-
-```bicep
-@export()
-type myStringType = string
-
-@export()
-type myOtherStringType = myStringType
-```
-
-For more information, see [Import user-defined data types](./bicep-import-providers.md#import-user-defined-data-types-preview).
-
 ## Next steps
 
 - For a list of the Bicep data types, see [Data types](./data-types.md).

articles/azure-resource-manager/bicep/user-defined-functions.md

@@ -21,11 +21,12 @@ There are some restrictions when defining a user function:
 * The function can't use the [reference](bicep-functions-resource.md#reference) function or any of the [list](bicep-functions-resource.md#list) functions.
 * Parameters for the function can't have default values.
 
-## Define the function
+## Define functions
 
 Use the `func` statement to define user-defined functions.
 
 ```bicep
+@<decorator>(<argument>)
 func <user-defined-function-name> (<argument-name> <data-type>, <argument-name> <data-type>, ...) <function-data-type> => <expression>
 ```
 
@@ -101,18 +102,31 @@ The output from the preceding example is:
 | ---- | ---- | ----- |
 | elements | positiveInt | 3 |
 
-## Import functions between Bicep files
+## Use decorators
 
-Only functions that bear the `@export()` decorator can be imported to other templates.
+Decorators are written in the format `@expression` and are placed above function declarations. The following table shows the available decorators for functions.
 
-The following example enables you to import the user-defined function from other templates:
+| Decorator | Argument | Description |
+| --------- | ----------- | ------- |
+| [description](#description) | string | Provide descriptions for the function. |
+| [export](#export) | none | Indicates that the function can be imported by another file. |
+
+Decorators are in the [sys namespace](bicep-functions.md#namespaces-for-functions). If you need to differentiate a decorator from another item with the same name, preface the decorator with `sys`. For example, if your Bicep file includes a variable named `description`, you must add the sys namespace when using the **description** decorator.
+
+### Description
+
+To add explaination, add a description to function declaration. For example:
 
 ```bicep
-@export()
-func sayHello(name string) string => 'Hello ${name}!'
+@description('The say hello function.')
+func sayHelloString(name string) string => 'Hi ${name}!'
 ```
 
-For more information, see [Import variables, functions, and types](./bicep-import.md#import-types-variables-and-functions).
+Markdown-formatted text can be used for the description text.
+
+### Export
+
+Use `@export()` to share the function with other Bicep files. For more information, see [Export variables, types, and functions](./bicep-import.md#export-variables-types-and-functions).
 
 ## Next steps
 

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

@@ -19,6 +19,7 @@ You are limited to 256 variables in a Bicep file. For more information, see [Tem
 The syntax for defining a variable is:
 
 ```bicep
+@<decorator>(<argument>)
 var <variable-name> = <variable-value>
 ```
 
@@ -120,7 +121,7 @@ Decorators are written in the format `@expression` and are placed above variable
 
 | Decorator | Argument | Description |
 | --------- | ----------- | ------- |
-| [description](#description) | string | Text that explains how to use the variable. |
+| [description](#description) | string | Provide descriptions for the variable. |
 | [export](#export) | none | Indicates that the variable can be imported by another file. |
 
 Decorators are in the [sys namespace](bicep-functions.md#namespaces-for-functions). If you need to differentiate a decorator from another item with the same name, preface the decorator with `sys`. For example, if your Bicep file includes a variable named `description`, you must add the sys namespace when using the **description** decorator.
@@ -164,19 +165,6 @@ output stgOutput string = storageName
 
 Because storage account names must use lowercase letters, the `storageName` variable uses the `toLower` function to make the `storageNamePrefix` value lowercase. The `uniqueString` function creates a unique value from the resource group ID. The values are concatenated to a string.
 
-## Import variables between Bicep files
-
-Only variables that bear the `@export()` decorator can be imported to other templates.
-
-The following example enables you to import the variable from other templates:
-
-```bicep
-@export()
-var myConstant = 'This is a constant value'
-```
-
-For more information, see [Import variables, types, and functions](./bicep-import.md#import-variables-types-and-functions).
-
 ## Configuration variables
 
 You can define variables that hold related values for configuring an environment. You define the variable as an object with the values. The following example shows an object that holds values for two environments - **test** and **prod**. Pass in one of these values during deployment.