Merge pull request #222638 from nayef-yassin/patch-40

Update ci-cd-custom-deploy.md

Author: prmerger-automator[bot]

articles/sentinel/ci-cd-custom-deploy.md

@@ -156,6 +156,23 @@ For more information, see the [Azure DevOps documentation](/azure/devops/pipelin
 > In both GitHub and Azure DevOps, make sure that you keep the trigger path and deployment path directories consistent.
 >
 
+## Scale your deployments with parameter files
+
+Rather than passing parameters as inline values in your content files, you can [use a JSON file that contains the parameter values](../azure-resource-manager/templates/parameter-files.md). You can then map those parameter JSON files to their associated Sentinel content files to better scale your deployments across different workspaces. There are a number of ways to map parameter files to Sentinel files, and the repositories deployment pipeline considers them in the following order: 
+ 
+:::image type="content" source="media/ci-cd-custom-deploy/deploy-parameter-file-precedence.svg" alt-text="A diagram showing the precedence of parameter file mappings.":::
+
+1. Is there a mapping in the sentinel-deployment.config? [Customize your connection configuration](ci-cd-custom-deploy.md#customize-your-connection-configuration) to learn more.
+1. Is there a workspace-mapped parameter file? This would be a parameter file in the same directory as the content files that ends with .parameters-<WorkspaceID>.json
+1. Is there a default parameter file? This would be any parameter file in the same directory as the content files that ends with .parameters.json
+     
+It is encouraged to map your parameter files through through the configuration file or by specifying the workspace ID in the file name to avoid clashes in scenarios with multiple deployments.
+
+> [!IMPORTANT]
+> Once a parameter file match is determined based on the above mapping precedence, the pipeline will ignore any remaining mappings.
+> 
+
+Modifying the mapped parameter file listed in the sentinel-deployment.config will trigger the deployment of its paired content file. Adding or modifying a *.parameters-\<workspaceID\>.json* file or *.parameters.json* file will also trigger a deployment of the paired content file(s) along with the newly modified parameters, unless a higher precedence parameter mappings is in place. Other content files won't be deployed as long as the smart deployments feature is still enabled in the workflow/pipeline definition file.
 
 ## Customize your connection configuration
 
@@ -203,19 +220,11 @@ Here's an example of the entire contents of a valid *sentinel-deployment.config*
 
     Add full path names to the `"prioritizedcontentfiles":` section. Wildcard matching is not supported at this time.
 
-- **To exclude content files**, modify the `"excludecontentfiles":` section with full path names of individual .json deployment files.
+- **To exclude content files**, modify the `"excludecontentfiles":` section with full path names of individual .json content files.
 
 - **To map parameters**:
 
-    The deployment script will accept three methods to map parameters. The precedence is determined for each included .json deployment file in your repository as follows: 
- 
-    :::image type="content" source="media/ci-cd-custom-deploy/deploy-parameter-file-precedence.svg" alt-text="A diagram showing the precedence of parameter file mappings.":::
-
-     1. Is there a mapping in the sentinel-deployment.config?
-     1. Is there a workspace parameter file?
-     1. Is there a default parameter file?
-
-Modifying the mapped parameter file listed in the sentinel-deployment.config will trigger the deployment of its paired content file. Adding or modifying a *.parameters-\<workspaceID\>.json* file or *.parameters.json* file triggers a deployment of that corresponding content file along with the newly modified parameters, unless a higher precedence parameter mappings is in place. Other content files won't be deployed if the smart deployments feature is still enabled.
+    The deployment script will accept three methods of mapping parameters as described in [Scale your deployments with parameter files](ci-cd-custom-deploy.md#scale-your-deployments-with-parameter-files). Mapping parameters through the sentinel-deployment.config takes the highest precedence and will guarantee that a given parameter file will be mapped to its associated content files. Simply modify the `"parameterfilemappings":` section with your target connection's workspace ID and full path names of individual .json files.
 
 
 ## Next steps
@@ -226,4 +235,4 @@ For more information, see:
 
 - [Sentinel CICD repositories sample](https://github.com/SentinelCICD/RepositoriesSampleContent)
 - [Create Resource Manager parameter file](../azure-resource-manager/templates/parameter-files.md)
-- [Parameters in ARM templates](../azure-resource-manager/templates/parameters.md)
+- [Parameters in ARM templates](../azure-resource-manager/templates/parameters.md)