Update md file metadata

Author: mumian

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

@@ -1,9 +1,9 @@
----
+---
 title: Learn best practices when developing Bicep files
 description: Describes practices to follow when creating your Bicep files so they work well and are easy to maintain.
 author: johndowns
 ms.author: jodowns
-ms.topic: conceptual
+ms.topic: article
 ms.custom: devx-track-bicep
 ms.date: 10/30/2025
 ---
@@ -119,3 +119,4 @@ You can't create policies or role assignments at the [tenant scope](deploy-to-te
 
 * For an introduction to Bicep, see [Bicep quickstart](quickstart-create-bicep-use-visual-studio-code.md).
 * For information about the parts of a Bicep file, see [Understand the structure and syntax of Bicep files](file.md).
+

articles/azure-resource-manager/bicep/bicep-config-linter.md

@@ -1,7 +1,7 @@
----
+---
 title: Linter settings for Bicep config
 description: Describes how to customize configuration values for the Bicep linter
-ms.topic: conceptual
+ms.topic: article
 ms.custom: devx-track-bicep
 ms.date: 06/19/2025
 ---
@@ -212,3 +212,4 @@ For the rule about hardcoded environment URLs, you can customize which URLs are
 - [Configure your Bicep environment](bicep-config.md)
 - [Add module settings in Bicep config](bicep-config-modules.md)
 - Learn about the [Bicep linter](linter.md)
+

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

@@ -1,7 +1,7 @@
----
+---
 title: Module setting for Bicep config
 description: Describes how to customize configuration values for modules in Bicep deployments.
-ms.topic: conceptual
+ms.topic: article
 ms.custom: devx-track-bicep
 ms.date: 04/28/2025
 ---
@@ -177,3 +177,4 @@ Bicep uses the [Azure.Identity SDK](/dotnet/api/azure.identity) to do authentica
 - [Configure your Bicep environment](bicep-config.md)
 - [Add linter settings to Bicep config](bicep-config-linter.md)
 - Learn about [modules](modules.md)
+

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

@@ -1,7 +1,7 @@
----
+---
 title: Configure your Bicep environment
 description: Learn how to configure your environment for Bicep file deployments.
-ms.topic: conceptual
+ms.topic: article
 ms.date: 10/30/2025
 ms.custom: devx-track-bicep
 ---
@@ -152,3 +152,4 @@ See [Experimental Features](https://aka.ms/bicep/experimental-features) for more
 
 - Learn how to add [module settings](bicep-config-modules.md) and [linter settings](bicep-config-linter.md) in the Bicep config file.
 - Learn about the [Bicep linter](linter.md).
+

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

@@ -1,7 +1,7 @@
----
+---
 title: Use extensions in Bicep
 description: This article describes how to use Bicep extensions.
-ms.topic: conceptual
+ms.topic: article
 ms.custom:
   - devx-track-bicep
   - build-2025
@@ -35,3 +35,4 @@ For examples, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md)
 - To learn how to use the Bicep Kubernetes extension, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
 - To go through a Kubernetes extension tutorial, see [Quickstart: Deploy Azure applications to Azure Kubernetes Services by using the Bicep Kubernetes extension](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).
 - To learn Microsoft Graph extension, see [Microsoft Graph extension](https://aka.ms/graphbicep).
+

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

@@ -1,7 +1,7 @@
----
+---
 title: Imports in Bicep
 description: This article describes how to import shared functionality and namespaces in Bicep.
-ms.topic: conceptual
+ms.topic: article
 ms.custom:
   - devx-track-bicep
   - build-2025
@@ -102,3 +102,4 @@ Both `az` and `sys` are Bicep built-in namespaces. They're imported by default.
 - To learn about how to use the Kubernetes extension, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
 - To go through a Kubernetes extension tutorial, see [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes extension.](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).
 - To learn about how to use the Microsoft Graph extension, see [Bicep files for Microsoft Graph](https://aka.ms/graphbicep).
+

articles/azure-resource-manager/bicep/bicep-kubernetes-extension.md

@@ -1,7 +1,7 @@
----
+---
 title: Bicep Kubernetes extension
 description: Learn how to Bicep Kubernetes extension to deploy .NET applications to Azure Kubernetes Service clusters.
-ms.topic: conceptual
+ms.topic: article
 ms.custom:
   - devx-track-bicep
   - devx-track-dotnet
@@ -85,3 +85,4 @@ From Visual Studio Code, you can import Kubernetes manifest files to create Bice
 
 - To walk through a quickstart, see [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes extension](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).
 - To learn about how to use the Microsoft Graph extension, see [Bicep files for Microsoft Graph](https://aka.ms/graphbicep).
+

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

@@ -1,7 +1,7 @@
----
+---
 title: Using and using none statements
 description: Learn how to use the `using` and `using none` statements in Bicep.
-ms.topic: conceptual
+ms.topic: article
 ms.date: 06/30/2025
 ms.custom: devx-track-bicep
 ---
@@ -10,9 +10,9 @@ ms.custom: devx-track-bicep
 
 A `using` or a `using none` declaration must be present in all Bicep parameters files.
 
-A Bicep parameter file typically uses a `using` statement to tie the file to a [Bicep file](./file.md), a [JSON Azure Resource Manager template (ARM template)](../templates/syntax.md), a [Bicep module](./modules.md), or a [template spec](./template-specs.md). This linkage allows the Bicep language server and compiler to validate the parameter file—checking for correct names, types, and required values based on the template’s inputs.
+A Bicep parameter file typically uses a `using` statement to tie the file to a [Bicep file](./file.md), a [JSON Azure Resource Manager template (ARM template)](../templates/syntax.md), a [Bicep module](./modules.md), or a [template spec](./template-specs.md). This linkage allows the Bicep language server and compiler to validate the parameter file—checking for correct names, types, and required values based on the template’s inputs.
 
-In contrast, the `using none` statement explicitly indicates that the parameter file isn't tied to any particular template at compile time. This means the parameters aren't validated against a specific template and are instead intended for more general use—such as being consumed by external tools or serving as shared, reusable parameter sets.
+In contrast, the `using none` statement explicitly indicates that the parameter file isn't tied to any particular template at compile time. This means the parameters aren't validated against a specific template and are instead intended for more general use—such as being consumed by external tools or serving as shared, reusable parameter sets.
 
 > [!NOTE]
 > Bicep parameters files are supported only in [Bicep CLI version 0.18.4](https://github.com/Azure/bicep/releases/tag/v0.18.4) or later, [Azure CLI](/cli/azure/install-azure-cli) version 2.47.0 or later, and [Azure PowerShell](/powershell/azure/install-azure-powershell) version 9.7.1 or later. The `using none` feature is supported in [Bicep CLI version 0.31.0](https://github.com/Azure/bicep/releases/tag/v0.31.92) or later.
@@ -113,7 +113,7 @@ The primary benefit of `using none` in Bicep lies in scenarios where parameter f
 
 - **Centralized Parameter Repositories**
 
-  Organizations often maintain standard parameter values—such as default regions, naming conventions, or global tags—used across multiple Bicep deployments. A Bicep parameters file with using none can act as a central store for these shared values, improving consistency and minimizing duplication. These parameters can then be programmatically merged with template-specific values at deployment time.
+  Organizations often maintain standard parameter values—such as default regions, naming conventions, or global tags—used across multiple Bicep deployments. A Bicep parameters file with using none can act as a central store for these shared values, improving consistency and minimizing duplication. These parameters can then be programmatically merged with template-specific values at deployment time.
 
   For example, a shared Bicep parameters file might define:
 
@@ -129,9 +129,10 @@ The primary benefit of `using none` in Bicep lies in scenarios where parameter f
 
   In CI/CD pipelines or automation scripts, parameter files may be created on-the-fly or associated with templates at runtime. By omitting a fixed template reference, `using none` allows these files to remain flexible and adaptable to different deployment contexts.
 
-When `using none` is specified in a Bicep parameter file, the compiler doesn't validate the parameters against a specific Bicep template, meaning no compile-time warnings or errors are raised for mismatched names or types due to the absence of a linked template. However, this decoupling applies only during authoring and compilation—at deployment time, Azure Resource Manager (ARM) still requires both a Bicep template and a parameter file. The ARM engine performs validation during deployment by resolving the parameters in the file against those defined in the target template.
+When `using none` is specified in a Bicep parameter file, the compiler doesn't validate the parameters against a specific Bicep template, meaning no compile-time warnings or errors are raised for mismatched names or types due to the absence of a linked template. However, this decoupling applies only during authoring and compilation—at deployment time, Azure Resource Manager (ARM) still requires both a Bicep template and a parameter file. The ARM engine performs validation during deployment by resolving the parameters in the file against those defined in the target template.
 
 ## Next steps
 
 - Learn about Bicep parameters files in [Create parameters files for Bicep deployment](./parameter-files.md).
 - Learn about configuring aliases in _bicepconfig.json_ files in [Configure your Bicep environment](./bicep-config.md).
+

articles/azure-resource-manager/bicep/child-resource-name-type.md

@@ -1,7 +1,7 @@
----
+---
 title: Child resources in Bicep
 description: Describes how to set the name and type for child resources in Bicep.
-ms.topic: conceptual
+ms.topic: article
 ms.custom: devx-track-bicep
 ms.date: 04/28/2025
 ---
@@ -177,3 +177,4 @@ resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2025-06-01
 
 * To learn about creating Bicep files, see [Understand the structure and syntax of Bicep files](./file.md).
 * To learn about the format of the resource name when referencing the resource, see the [reference function](./bicep-functions-resource.md#reference).
+

articles/azure-resource-manager/bicep/compare-template-syntax.md

@@ -1,7 +1,7 @@
----
+---
 title: Compare syntax for Azure Resource Manager templates in JSON and Bicep
 description: Compares Azure Resource Manager templates developed with JSON and Bicep, and shows how to convert between the languages.
-ms.topic: conceptual
+ms.topic: article
 ms.custom: devx-track-bicep, devx-track-arm-template
 ms.date: 04/28/2025
 ---
@@ -325,3 +325,4 @@ To separate a solution into multiple files:
 
 * For information about the Bicep, see [Bicep quickstart](./quickstart-create-bicep-use-visual-studio-code.md).
 * To learn about converting templates between the languages, see [Converting ARM templates between JSON and Bicep](decompile.md).
+