Feature/zaidmark infra docs (#520)

* -remove mentions of old variable to lower confusion

* ~add minor clarification

* +Add link again

* ~try fix

* ~fix link

* Update docs/workloads/azure/data/getting_started/core_data_platform_deployment_azure.md

Co-authored-by: Andy Durkan <108685738+adurkan-amido@users.noreply.github.com>

* Update asciidoc/workloads/azure/data/getting_started/core_data_platform_deployment_azure.adoc

Co-authored-by: Andy Durkan <108685738+adurkan-amido@users.noreply.github.com>

---------

Co-authored-by: Radu Gherman <radu.gherman@ensono.com>
Co-authored-by: Andy Durkan <108685738+adurkan-amido@users.noreply.github.com>

asciidoc/workloads/azure/data/getting_started/core_data_platform_deployment_azure.adoc

@@ -29,10 +29,6 @@ Open the project locally and create a new feature branch e.g.:
 git checkout -b feat/infra-pipeline
 ----
 
-The file `deploy/azure/infra/vars.tf` contains a variable `enable_private_networks`:
-
-* If you want to provision infrastructure within a link:../architecture/infrastructure_data_azure.adoc#networking[private network], ensure this variable is set to `true`. This is the approach currently supported by Ensono Stacks.
-
 == Step 2: Add Infrastructure pipeline in Azure DevOps
 
 A YAML file containing a template Azure DevOps CI/CD pipeline for building and deploying the core infrastructure is provided in `build/azDevOps/azure/air-infrastructure-data.yml` - this should be added as the definition for a new pipeline in Azure DevOps.
@@ -41,7 +37,8 @@ A YAML file containing a template Azure DevOps CI/CD pipeline for building and d
 2. Go to Pipelines, and then select *New pipeline*
 3. Name the new pipeline, e.g. `amido.stacks-data-infrastructure`
 4. For the pipeline definition, specify the YAML file in the project repository feature branch (`air-infrastructure-data.yml`) and save
-5. The new pipeline will require access to any Azure DevOps pipeline variable groups specified in the pipeline YAML. Under each variable group, go to 'Pipeline permissions' and add the pipeline.
+5. Make sure that the Enable Private Networks box is set to your preferred deployment method. If you want to provision infrastructure within a link:../architecture/infrastructure_data_azure.adoc#networking[private network], ensure this variable is ticked. Unticking the box will issue a public network deployment.
+6. The new pipeline will require access to any Azure DevOps pipeline variable groups specified in the pipeline YAML. Under each variable group, go to 'Pipeline permissions' and add the pipeline.
 
 == Step 3: Deploy Infrastructure in non-production environment
 

docs/workloads/azure/data/getting_started/core_data_platform_deployment_azure.md

@@ -30,10 +30,6 @@ Open the project locally and create a new feature branch e.g.:
 git checkout -b feat/infra-pipeline
 ```
 
-The file `deploy/azure/infra/vars.tf` contains a variable `enable_private_networks`:
-
-* If you want to provision infrastructure within a [private network](../architecture/infrastructure_data_azure#networking), ensure this variable is set to `true`. This is the approach currently supported by Ensono Stacks.
-
 ## Step 2: Add Infrastructure pipeline in Azure DevOps
 
 A YAML file containing a template Azure DevOps CI/CD pipeline for building and deploying the core infrastructure is provided in `build/azDevOps/azure/air-infrastructure-data.yml` - this should be added as the definition for a new pipeline in Azure DevOps.
@@ -42,7 +38,9 @@ A YAML file containing a template Azure DevOps CI/CD pipeline for building and d
 2. Go to Pipelines, and then select **New pipeline**
 3. Name the new pipeline, e.g. `amido.stacks-data-infrastructure`
 4. For the pipeline definition, specify the YAML file in the project repository feature branch (`air-infrastructure-data.yml`) and save
-5. The new pipeline will require access to any Azure DevOps pipeline variable groups specified in the pipeline YAML. Under each variable group, go to 'Pipeline permissions' and add the pipeline.
+5. Make sure that the Enable Private Networks box is set to your preferred deployment method. If you want to provision infrastructure within a [private network](../architecture/infrastructure_data_azure#networking), ensure this variable is ticked. Unticking the box will issue a public network deployment.
+6. The new pipeline will require access to any Azure DevOps pipeline variable groups specified in the pipeline YAML. Under each variable group, go to 'Pipeline permissions' and add the pipeline.
+
 
 ## Step 3: Deploy Infrastructure in non-production environment