Draft updates

Author: Esther Fan

articles/business-process-tracking/set-up-continuous-integration-deployment.md

@@ -56,6 +56,10 @@ This guide shows how to set up a CI/CD pipeline by using the Azure Logic Apps St
 
   This extension provides automated, build, connections deployment, and release tasks for Azure Logic Apps (Standard). For more information, see [**Azure Logic Apps Standard Tasks**](https://marketplace.visualstudio.com/items?itemName=ms-logicapps-ado.azure-logic-apps-devops-tasks).
 
+- The appropriate user role permissions to create, view, use, or manage a service connection between the pipelines that you create later in this article.
+
+  For more information, see [Set service connection security in Azure Pipelines](/azure/devops/pipelines/policies/permissions#set-service-connection-security-in-azure-pipelines).
+
 ## Generate deployment scripts
 
 Now, generate deployment scripts for your logic app project. This approach lets you create the required infrastructure with the CI and CD scripts that help you deploy your logic app to Azure. For more information, see [Automate build and deployment for Standard logic app workflows with Azure DevOps](automate-build-deployment-standard.md). 
@@ -84,9 +88,9 @@ Now, generate deployment scripts for your logic app project. This approach lets
    `git commit -m "<your-commit-comment>"`<br>
    `git push`
 
-## Create the infrastructure pipeline
+## Create an infrastructure pipeline
 
-Now, create a pipeline in your repository for your logic app infrastructure. For the general steps, see [Create your first pipeline](/azure/devops/pipelines/create-first-pipeline?view=azure-devops&tabs=java%2Cbrowser), but use the following custom steps:
+Now, create a pipeline in your repository for your logic app infrastructure. For the general steps, see [Create your first pipeline](/azure/devops/pipelines/create-first-pipeline), but use the following custom steps:
 
 1. Select **Existing Azure Pipeline YAML File**.
 
@@ -98,9 +102,105 @@ Now, create a pipeline in your repository for your logic app infrastructure. For
 
    **/pipelines/infrastructure-pipeline.yaml**
 
-1. Select **Continue** > **Review**. Provide the name for the pipeline, but the pipeline folder is optional. 
+1. Select **Continue** > **Review**. Provide the name for the pipeline, but the pipeline folder is optional.
 
 1. To complete this task, select **Save**.
 
+## Create a continuous integration (CI) pipeline
+
+Create a pipeline in your repository for continuous integration. For the general steps, see [Create your first pipeline](/azure/devops/pipelines/create-first-pipeline), but use the following custom steps:
+
+1. Select **Existing Azure Pipeline YAML File**.
+
+1. Select **CI-pipeline.yml**.
+
+1. Provide the name for the pipeline, but the pipeline folder is optional.
+
+## Create a continuous deployment (CD) pipeline
+
+In Azure DevOps, create another Pipeline in your repository. For additional information, please refer to Azure DevOps documentation. When creating a Pipeline, use the following configuration: 
+
+1. Select **Existing Azure Pipeline YAML File**.
+
+1. Select **CD-pipeline.yml**.
+
+1. Provide the name for the pipeline, but the pipeline folder is optional.
+
+## Create a service connection
+
+A service connection is an authenticated connection between Azure Pipelines and external or remote services that you use to complete tasks. In this scenario, the service connection lets your CI/CD process create and manage resources in Azure. These steps create a Microsoft Entra ID app registration that you use as an authentication credential.
+
+1. Follow the steps in [Create Azure Resource Manager service connection that uses workload identity federation](/azure/devops/pipelines/library/connect-to-azure#create-an-azure-resource-manager-service-connection-that-uses-workload-identity-federation).
+
+1. Make sure that you select **Azure Resource Manager** as the service connection type, and then select **Next**.
+
+1. Provide the following information:
+
+   | Parameter | Description |
+   |-----------|-------------|
+   | **Identity type** | Select **App registration (automatic)**. | 
+   | **Credential** | Select **Workload identity federation (Recommended)**. |
+   | **Scope** | Select **Subscription**. |
+   | **Subscription** | Your Azure subscription. |
+   | **Resource group** | The Azure resource group. |
+   | **Service Connection Name** | The name for the service connection. |
+   | **Service Management Reference** (optional) | Context information. |
+
+1. When you're done, select **Save**.
+
+1. Note the name for the created Microsoft Entra ID app registration.
+
+## Find the Microsoft Entra ID application registration
+
+Confirm that your Microsoft Entra ID application has the necessary role and permissions for your scenario and get the object ID for later use.
+
+1. In the Azure portal search box, enter the name for the Microsoft Entra ID application.
+
+1. Confirm that the Microsoft Entra ID application has **Contributor** access for the resource group. If not, assign that access.
+
+## Update pipelines to use the service connection
+
+Now, specify the service connection to use with your pipelines.
+
+1. In each file listed, find the property named **`serviceConnectionName`**. Set the property value to the service connection name.
+
+   - Infrastructure pipeline: Update the **infrastructure-pipeline-variables.yml** file.
+   - CI pipeline: Update the **CI-pipeline-variables.yml** file.
+   - CD pipeline: Update the **CD-pipeline-variables.yml** file.
+
+1. In the **CI-pipeline-variables.yml** file, add a new property named **`subscriptionId`**. Set the property value to your Azure subscription ID, for example:
+
+   `subscriptionId: '<Azure-subscription-ID>'`
+
+1. Make sure to save all the updated .yml pipeline files.
+
+1. In Visual Studio Code, run the following Git commands from the command prompt:
+
+   `git add -A`<br>
+   `git commit -m "<your-commit-comment>"`<br>
+   `git push`
+
+## Run infrastructure pipeline
+
+To create your Standard logic app in Azure, follow these steps:
+
+1. In Azure DevOps, select the appropriate branch, and then select **Run**.
+
+1. If prompted, provide the permissions necessary to run the pipeline.
+
+After the pipeline completes, you have an empty Standard logic app resource without any workflows in Azure.
+
+## Run CI and CD pipelines
+
+1. Before you run the CD pipeline, update this pipeline to include the source value, which is the name for your CI pipeline.
+
+   You can directly commit to the branch, but then run **`git pull`** on your local source to locally synchronize this change.
+
+1. In Azure DevOps, run the CI pipeline, then run the CD pipeline.
+
+1. If prompted, provide the permissions necessary to run the pipelines.
+
+After the CD pipeline completes, you have the content from your Standard logic app project deployed to the logic app resource previously created in Azure. 
+
 ## Related content