Deploy a business process and tracking profile to Azure (preview)

Important

This capability is in public preview and isn't ready yet for production use. For more information, see the Supplemental Terms of Use for Microsoft Azure Previews.

After you define the key business property values to capture for tracking and map your business process stages to the operations and data in Standard logic app workflows, you're ready to deploy your business process and tracking profile to Azure.

Prerequisites

• An Azure account and subscription. If you don't have an Azure subscription, sign up for a free Azure account.

• An integration environment that contains an application group, which has at least the Standard logic app resources, workflows, and operations that you mapped to your business process stages

  Before you can deploy your business process, you must have access to the Standard logic app resources and workflows that are used in the mappings. This access is required because deployment creates and adds a tracking profile to each logic app resource that participates in the business process.

• A business process with stages mapped to actual operations and property values in a Standard logic app workflow

• The Azure Data Explorer database associated with your application group must be online.

  Deployment creates or uses a table with your business process name in your instance's database to add and store the data captured from the workflow run. Deployment also causes all the participating Standard logic app resources to automatically restart.

Deploy business process and tracking profile

1. In the Azure portal, open your integration environment, application group, and business process that you want to deploy, if they're not already open.

2. On the process designer toolbar, select Deploy.

   

   In the Deploy business process section, the Cluster and Database properties show prepopulated values for the Azure Data Explorer instance associated with your application group.

   

3. For the Table property, choose either of the following options:

   • Keep and use the prepopulated name for your business process to create a table in your database.

   • Provide the name for an existing table in your database, and select Use an existing table.

   Important

   If you want each business process to have its own table for security reasons, provide a unique name to create a new and separate table. This practice helps you avoid mixing sensitive data with non-sensitive data and is useful for redeployment scenarios.

4. When you're ready, select Deploy.

   Azure shows a notification based on whether the deployment succeeds.

5. Return to the Business processes page, which now shows the business process with a checkmark in the Deployed column.

   

View recorded transactions

After the associated Standard logic app workflows run and emit the data that you specified to capture, you can view the recorded transactions.

1. On the Business processes page, next to the business process with the transactions that you want, select View transactions (table with magnifying glass).

   

   The Transactions page shows any records that your solution tracked.

   

2. Sort the records based on Business identifier, Time executed, or Business process.

3. To review the status for your business process, on a specific transaction row, select the business identifier value.

   For a specific transaction, the Transaction details pane shows the status information for the entire business process, for example:

   

4. To review the status for a specific stage, on the Transaction details pane, select that stage.

   The Transaction details pane now shows the tracked properties for the selected stage, for example:

   

5. To create custom experiences for the data provided here, check out Azure Workbooks or Azure Data Explorer with Power BI.

Next steps

What is Azure Integration Environments?