Draft updates

Author: Esther Fan

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

@@ -3,7 +3,7 @@ title: Set Up CI and CD for Business Processes
 description: Learn how to set up continuous integration and continuous deployment for business processes in different environments without rebuilding or remapping.
 ms.service: azure-business-process-tracking
 ms.topic: how-to
-ms.reviewer: estfan, keweare, azla
+ms.reviewer: estfan, kewear, azla
 ms.date: 06/09/2025
 # Customer intent: As an integration developer, I want to set up continuous integration and continuous delivery for business processes without having to rebuild and map business stages to workflows across different environments, such as development, test, and production.
 ---
@@ -12,164 +12,95 @@ ms.date: 06/09/2025
 
 To deploy a business process across various environments, such as development, test, and production, without having to remap business stages to workflow operations and rebuild logic app projects, you can set up continuous integration (CI) and continuous deployment (CD)
 
-This guide shows how to set up a CI-CD pipeline by using the Azure Logic Apps Standard Tasks for Azure DevOps.
+This guide shows how to set up a CI/CD pipeline by using the Azure Logic Apps Standard Tasks for Azure DevOps.
 
 ## Prerequisites
 
 - An Azure account and subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
-  > [!NOTE]
-  >
-  > If you're using an [Azure integration environment and application groups](../integration-environments/overview.md) 
-  > to organize your Azure resources, and you want to map your business process to Azure resources in your 
-  > integration environment, all your Azure resources must use the same subscription, including your business 
-  > processes and integration environment. If you're not using an Azure integration environment, you can map 
-  > your business process to Azure resources where you have access.
+- Visual Studio Code and the required prerequisites.
 
-- An Azure DevOps repository for your source code and artifacts
+  For more information, see [Create Standard logic app workflows with Visual Studio Code](create-standard-workflows-visual-studio-code.md#prerequisites).
 
-  If you don't have a repository, follow these steps:
+- A Visual Studio Code workspace with an undeployed Standard logic app project.
 
-  1. 
+- An Azure DevOps Services Git repository where you store your source code and artifacts.
 
+  If you don't have a repository, follow the steps in [Set up a Git repository](/devops/develop/git/set-up-a-git-repository).
 
-- The most recent **Azure Logic Apps Standard Tasks** extension for Azure Pipelines
+  After you create your repository, follow these steps to initialize your repository, so you can push your local changes to Azure DevOps:
 
-  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).
-
-- An updeployed Standard logic app project in Visual Studio Code
-
-
-
-<a name="create-business-process"></a>
-
-## Create a business process
-
-1. In the [Azure portal](https://portal.azure.com) search box, enter and select **Business Process Tracking**.
-
-   :::image type="content" source="media/create-business-process/select-business-process-tracking.png" alt-text="Screenshot shows Azure portal search box with business process tracking entered." lightbox="media/create-business-process/select-business-process-tracking.png":::
-
-1. On the **Business Process Tracking** toolbar, select **Create**.
-
-1. On the **Create business process** page, on the **Basics** tab, provide the following information:
-
-   | Property | Required | Value | Description |
-   |----------|----------|-------|-------------|
-   | **Subscription** | Yes | <*Azure-subscription*> | The Azure subscription to use for your business process. |
-   | **Resource group** | Yes | <*Azure-resource-group-name*> | A new or existing Azure resource group. <br><br>This example uses **City-Power-and-Light-RG**. |
-   | **Business process name** | Yes | <*process-name*> | A name for your business process. Use only alphanumeric characters, hyphens, underscores, parentheses, or periods. <br><br>This example uses **Resolve-Power-Outage**. |
-   | **Description** | No | <*process-description*> | The purpose for your business process. |
-   | **Region** | Yes | <*Azure-region*> | The Azure region for your business process. |
-
-   The following example shows the information for the sample business process:
-
-   :::image type="content" source="media/create-business-process/business-process-details.png" alt-text="Screenshot shows page for Create business process with Basics tab selected." lightbox="media/create-business-process/business-process-details.png":::
-
-1. When you're done, select **Next: Transaction ID**. On the **Transaction ID** tab, provide the following information:
+  1. Clone your repository. Find and save the clone URL. 
 
-   | Property | Required | Value | Description |
-   |----------|----------|-------|-------------|
-   | **Transaction ID** | Yes | <*transaction-ID*> | This important and unique ID identifies a transaction, such as an order number, ticket number, case number, or another similar business identifier that's available across all stages in your business process. <br><br>This example uses the transaction ID named **TicketNumber** to correlate events across the different systems in the example business process, which include CRM, Work Order Management, and Marketing. <br><br>**Note**: Azure Business Process Tracking automatically includes and records the transaction timestamp so that you don't have to separately add this value. Although you can define only a single transaction ID when you create a business process, you can later define other business properties in each stage that you want to record. |
-   | **Data type** | Yes | <*transaction-ID-data-type*> | The data type for your transaction ID: **String** or **Integer**. <br><br>This example uses the **Integer** data type. |
+     For more information, see [Clone an existing Git repo](/azure/devops/repos/git/clone).
 
-   The following example shows the sample transaction ID:
+  1. In Visual Studio Code, open your Standard logic app project.
 
-   :::image type="content" source="media/create-business-process/define-transaction-id.png" alt-text="Screenshot shows page for Create business process page with Transaction ID tab selected." lightbox="media/create-business-process/define-transaction-id.png":::
+  1. From the **Terminal** menu, select **New Terminal**.
 
-1. When you're done, select **Next: Data storage**. On the **Data storage** tab, provide the following information:
+  1. From the command prompt, go to the folder that has your project's workspace file. 
 
-   | Property | Required | Value | Description |
-   |----------|----------|-------|-------------|
-   | **Subscription** | Yes | <*Azure-subscription*> | The Azure subscription for your Data Explorer instance. |
-   | **Cluster** | Yes | <*cluster-name*> | The name for the cluster in your Data Explorer instance. |
-   | **Database** | Yes | <*database-name*> | The name for the database in your Data Explorer instance. |
-   | **Table** | Yes | <*table-name*> | The name for the table to create or use. To update an existing table, select the option to **Use an existing table**. <br><br>**Note**: Although you can use the same name as an existing table, which updates that table, for security purposes, create a unique and separate table for each business process. This practice helps you avoid mixing sensitive data with non-sensitive data and is useful for redeployment scenarios. |
-   | **Use an existing table** | No | Enabled or disabled | To update an existing table, select this option. |
+     A workspace is a text file with the **.code-workspace** extension. To find the folder with this file, open the **.vscode** folder in your root folder. 
 
-1. When you're done, select **Create**.
+  1. At the command prompt, run the following Git commands:
 
-   After the Azure portal completes deployment for your new **Business Process** resource, the portal automatically opens the resource's **Overview** page.
+     `git init`<br>
+     `git add -A`<br>
+     `git commit -m "<your-commit-comment>"`<br>
+     `git remote add origin <clone-URL>`<br>
+     `git push --set-upstream origin main`<br>  
 
-1. Now, continue on to add the stages for your business process.
+  1. At the prompt, provide your Git credentials to the Git Credential Manager.
 
-<a name="add-stage"></a>
+- The latest **Azure Logic Apps Standard Tasks** extension for Azure Pipelines
 
-## Add a business process stage
-
-After you create your business process, add the stages for that process. For example, suppose you're an integration developer at a power company. You manage a solution for a customer work order processor service that's implemented by multiple Standard logic app resources and their workflows. Your customer service team follows the following business process to resolve a customer ticket for a power outage:
-
-:::image type="content" source="media/create-business-process/business-process-stages-example.png" alt-text="Conceptual diagram shows example power outage business process stages for customer service at a power company." lightbox="media/create-business-process/business-process-stages-example.png":::
-
-1. In the [Azure portal](https://portal.azure.com), open your business process resource, if not already open.
-
-1. On the resource menu, under **Business process tracking**, select **Editor**.
-
-1. In the editor, select **Add stage**.
-
-   :::image type="content" source="media/create-business-process/add-stage.png" alt-text="Screenshot shows business process editor with Add stage selected." lightbox="media/create-business-process/add-stage.png":::
-
-1. On the **Add stage** pane, provide the following information:
-
-   > [!TIP]
-   >
-   > To quickly draft the stages in your business process, just provide the stage 
-   > name, select **Add**, and then return later to provide the remaining values 
-   > when you [map the business process to a Standard logic app workflow](map-business-process-workflow.md).
-
-   | Property | Required | Value | Description |
-   |----------|----------|-------|-------------|
-   | **Stage name** | Yes | <*stage-name*> | The name for this process stage. Use only alphanumeric characters, hyphens, underscores, parentheses, or periods. |
-   | **Description** | No | <*stage-description*> | The purpose for this stage. |
-
-   This example creates a stage named **Create_ticket**:
-
-   :::image type="content" source="media/create-business-process/add-stage-quick.png" alt-text="Screenshot shows pane named Add stage with stage name, description, and properties to track." lightbox="media/create-business-process/add-stage.png":::
-
-   In the **Properties to track** table, on the **Success** tab, your previously defined transaction ID is automatically included. This value is required for correlation across stages and workflows. 
+  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).
 
-   On the **Success** and **Failure** tabs, you can optionally define and map other business property values that you want to record. You can use these property values to correspondingly identify a successful or failed stage, which is left entirely to your interpretation, business scenarios, or needs.
+## Generate deployment scripts
 
-   - **Success** tab: Define and map other business property values to identify and record from a successful stage.
+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). 
 
-   - **Failure** tab: Define and map other business property values to identify and record from a failed stage.
+1. If your logic app project isn't currently visible, in Visual Studio Code, on the Activity Bar, select **Explorer**.
 
-   To define other business property values to use for this stage, follow these steps:
+1. In the **Explorer** window, open the shortcut menu for the project folder, and select **Generate Deployment Scripts**.
 
-   1. Under **Properties to track**, select **Success** or **Failure** as appropriate.
+1. Follow the prompts to provide the following deployment information for your logic app:
 
-   1. Under the **Properties to track** table, select **Add property**.
+   | Parameter | Description |
+   |-----------|-------------|
+   | **Subscription** | The Azure subscription. |
+   | **Resource Group** | The Azure resource group. |
+   | **Location** | The Azure region. |
+   | **Logic App Name** | The name for your logic app resource. |
+   | **Storage Account Name** | The name for the Azure storage account to use with your logic app. |
 
-   1. Enter the property name and type, which is either a **String** or **Integer**.
+   The deployment process creates the infrastructure (CI) and application (CD) pipelines and parameters files in a deployment folder, for example:
 
-   For example, this stage specifies a few more properties, such as **CustomerName**, **CustomerEmail**, and **CustomerPhone**, to record from a successfully completed stage:
+   <**SCREENSHOT**>
 
-   :::image type="content" source="media/create-business-process/add-properties.png" alt-text="Screenshot shows pane named Add stage with stage name, description, and more properties to track." lightbox="media/create-business-process/add-properties.png":::
+1. After the generated deployment scripts appear in your project, synchronize these updates to Azure DevOps by running the following Git commands from the command prompt:
 
-1. When you're done, select **Add stage**.
+   `git add -A`<br>
+   `git commit -m "<your-commit-comment>"`<br>
+   `git push`
 
-   Now, you can continue adding more stages or [map each business property in your stage to the respective operation and outputs in a Standard logic app workflow](map-business-process-workflow.md).
+## Create the infrastructure pipeline
 
-1. To add another stage, choose one of the following options on the process editor:
+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:
 
-   - Under the last stage, select the plus sign (**+**) for **Add a stage**.
- 
-   - Between stages, select the plus sign (**+**), and then select either **Add a stage** or **Add a parallel stage**, which creates a branch in your business process.
+1. Select **Existing Azure Pipeline YAML File**.
 
-   > [!TIP]
-   >
-   > To delete a stage, open the stage's shortcut menu, and select **Delete**.
+1. Select the appropriate branch.
 
-1. Repeat the preceding steps to add another stage as needed.
+   Earlier, you pushed local changes to Azure DevOps. Now, you can select the infrastructure pipeline that is created in Visual Studio Code.
 
-   The following example shows a completed business process:
+1. To find the pipeline, go to the following location:
 
-   :::image type="content" source="media/create-business-process/business-process-stages-complete.png" alt-text="Screenshot shows process editor with completed business process stages." lightbox="media/create-business-process/business-process-stages-complete.png":::
+   **/pipelines/infrastructure-pipeline.yaml**
 
-1. When you're done, on the process editor toolbar, select **Save**.
+1. Select **Continue** > **Review**. Provide the name for the pipeline, but the pipeline folder is optional. 
 
-1. Now, continue on to [map each business property to the respective operation and outputs in a Standard logic app workflow](map-business-process-workflow.md) so that you can get insights about your deployed resource.
+1. To complete this task, select **Save**.
 
-## Next step
+## Related content
 
-> [!div class="nextstepaction"]
-> [Map a business process to a Standard logic app workflow](map-business-process-workflow.md)