Merge pull request #302044 from mumian/0626-using-none

Document using none

Author: denrea

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

@@ -1,21 +1,27 @@
 ---
-title: Using statement
-description: Learn how to use the `using` statement in Bicep.
+title: Using and using none statements
+description: Learn how to use the `using` and `using none` statements in Bicep.
 ms.topic: conceptual
-ms.date: 01/10/2025
+ms.date: 06/30/2025
 ms.custom: devx-track-bicep
 ---
 
-# Using statement
+# Using and using none statements
 
-The `using` statement in [Bicep parameters files](./parameter-files.md) ties 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). A `using` declaration must be present in all Bicep parameters files.
+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.
+
+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]
-> The Bicep parameters file is only supported in the [Bicep CLI](./install.md#visual-studio-code-and-bicep-extension) version 0.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.
+> 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.
 >
-> To use the statement with JSON ARM templates, Bicep modules, and template specs, you need to have [Bicep CLI](./install.md#visual-studio-code-and-bicep-extension) version 0.22.6 or later and [Azure CLI](/cli/azure/install-azure-cli) version 2.53.0 or later.
+> To use the statement with JSON ARM templates, Bicep modules, and template specs, you need to have [Bicep CLI version 0.22.6](https://github.com/Azure/bicep/releases/tag/v0.22.6) or later and [Azure CLI](/cli/azure/install-azure-cli) version 2.53.0 or later.
 
-## Syntax
+## The using statement
+
+The syntax of the `using` statement:
 
 - To use Bicep files:
 
@@ -91,6 +97,40 @@ The `using` statement in [Bicep parameters files](./parameter-files.md) ties the
   using 'ts/myStorage:storageSpec:1.0'
   ```
 
+## The using none statement
+
+The `using none` statement in a Bicep parameters file (.bicepparam) indicates that the file isn't tied to a specific Bicep template during authoring or compilation. This decouples the parameter file from a particular template, enabling greater flexibility in how parameters are defined and used across deployments.
+
+The syntax of the `using none` statement:
+
+```bicep
+using none
+```
+
+This statement is placed at the beginning of a Bicep parameters file to signal that no specific template is referenced.
+
+The primary benefit of `using none` in Bicep lies in scenarios where parameter files are generalized, shared, or dynamically integrated with templates. Common use cases include:
+
+- **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.
+  
+  For example, a shared Bicep parameters file might define:
+
+  ```bicepparam
+  using none
+  
+  param location = 'westus2'
+  param environmentTag = 'production'
+  param projectName = 'myApp'
+  ```
+
+- **Dynamic Generation and Runtime Integration**
+
+  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.
+
 ## Next steps
 
 - Learn about Bicep parameters files in [Create parameters files for Bicep deployment](./parameter-files.md).

articles/azure-resource-manager/bicep/parameter-files.md

@@ -3,7 +3,7 @@ title: Create a parameters file for bicep deployment
 description: Learn how to create Bicep parameters files instead of passing parameters as inline values in your script.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 03/25/2025
+ms.date: 06/30/2025
 ---
 
 # Create a parameters file for Bicep deployment
@@ -15,9 +15,9 @@ These parameter files also help enable a streamlined CI/CD deployment approach.
 This article shows you how to create a parameters file, which you can use instead of passing parameters as inline values in your script. You can use either a Bicep parameters file with the `.bicepparam` file extension or a JSON parameters file that contains the parameter value.
 
 > [!NOTE]
-> Bicep parameters files are supported only in [Bicep CLI](./install.md#visual-studio-code-and-bicep-extension) version 0.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.
+> 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.
 
-A single Bicep file can have multiple Bicep parameters files associated with it. However, each Bicep parameters file is intended for one particular Bicep file. You can establish this relationship by applying the [`using` statement](./bicep-using.md) within the Bicep parameters file.
+A single Bicep file can be associated with multiple parameter files. However, each parameter file is typically linked to one specific Bicep file—unless `using none` is specified. This association is established using the [`using` statement](./bicep-using.md) within the parameter file.
 
 You can compile Bicep parameters files into JSON parameters files that you can deploy by using a Bicep file. For more information, see [`build-params`](./bicep-cli.md#build-params). You can also decompile a JSON parameters file into a Bicep parameters file. For more information, see [`decompile-params`](./bicep-cli.md#decompile-params).
 
@@ -28,7 +28,7 @@ A parameters file uses the following format:
 ### [Bicep parameters file](#tab/Bicep)
 
 ```bicep
-using '<path>/<file-name>.bicep'
+using '<path>/<file-name>.bicep' | using none
 
 param <first-parameter-name> = <first-value>
 param <second-parameter-name> = <second-value>
@@ -61,8 +61,11 @@ using 'ts:00000000-0000-0000-0000-000000000000/myResourceGroup/storageSpec:1.0'
 ...
 ```
 
-For more information, see [Using statement](./bicep-using.md).
+For more information, see [Using statement](./bicep-using.md#the-using-statement).
 
+You can apply the `using none` statement to indicate that the parameters file is not tied to a specific Bicep template during authoring or compilation. This decouples the parameter file from a particular template, enabling greater flexibility in how parameters are defined and used across deployments. For more information, see [Using none statement](./bicep-using.md#the-using-none-statement).
+
+```bicep
 You can use expressions with the default value. For example:
 
 ```bicep

articles/azure-resource-manager/bicep/toc.yml

@@ -272,8 +272,8 @@ items:
   - name: Modules (module)
     displayName: scopes,consume,registry,module registry,private module registry,public module registry,avm,azure verified modules
     href: modules.md
-  - name: Using (using)
-    displayName: avm,azure verified modules
+  - name: Using (using/using none)
+    displayName: avm,azure verified modules,using none
     href: bicep-using.md
   - name: Import (import)
     href: bicep-import.md