Reliable B2B Tracking using Premium SKU Integration Account

In the world of enterprise integration, accurate and reliable tracking of B2B transactions is crucial for maintaining compliance, troubleshooting issues, and ensuring smooth business operations. Organizations that rely on Logic Apps for EDI X12, EDIFACT, or AS2 transactions need robust tracking capabilities to monitor their B2B exchanges effectively.

Currently, in Logic Apps Consumption, B2B tracking is powered by Azure Log Analytics, which provides basic telemetry and logging capabilities. However, this approach has some key limitations:

• Limited Query Capabilities – Searching for transactions in Log Analytics can be cumbersome, especially when dealing with large-scale enterprise data.
• Retention and Performance Issues – Log Analytics is optimized for general telemetry, not for high-volume, structured B2B transaction tracking, making it challenging for organizations with strict compliance requirements. 

To address these challenges, we are introducing Reliable B2B Tracking in Logic Apps Standard using a Premium SKU Integration Account. This new feature ensures that all B2B transactions are reliably tracked and ingested into an Azure Data Explorer (ADX) cluster, providing a lossless tracking mechanism with powerful querying and visualization capabilities. With data in ADX, customers can extend their existing PowerBI dashboards or easily build custom dashboards on this data if they need detailed analysis on any issue.

Additionally, a tracking dashboard is available, enabling customers to monitor, search, and analyze B2B transactions efficiently. This enhancement significantly improves reliability, visibility, and troubleshooting for mission-critical B2B integrations. 

How It Works

Reliable B2B Tracking in Logic Apps Standard ensures that every AS2, X12, and EDIFACT transaction is accurately recorded and stored in an Azure Data Explorer (ADX) cluster database instead of relying on Azure Log Analytics, which may drop events. Here’s how the system works:

1. Event Collection – Whenever a B2B transaction occurs, tracking data is generated from the built-in AS2, X12, and EDIFACT actions in Logic Apps Standard.
2. Data Ingestion – Instead of sending logs to Log Analytics, the tracking data is directly pushed to an Azure Data Explorer (ADX) cluster via integration account transactionally to ensure reliable, lossless storage.
3. Structured Storage – ADX provides fast indexing and query capabilities, allowing enterprises to search, filter, and analyze their transactions efficiently.
4. Tracking Dashboard – A dedicated B2B monitoring dashboard visualizes transaction flow, helping customers track acknowledgments (997, MDN), detect failures, and troubleshoot issues in real time.

Requirements for Using Reliable B2B Tracking

To enable this feature, customers must meet the following prerequisites:

1. Premium SKU Integration Account – This feature is only available with a Premium SKU Integration Account in Logic Apps Standard.
2. Built-in AS2, X12, or EDIFACT Actions – Only transactions processed through Logic Apps Standard using built-in B2B actions will be tracked reliably.
3. Azure Data Explorer Cluster – Customers must provide their own ADX cluster database, where all transaction logs will be stored and queried.

Please note that B2B tracking for EDIFACT transactions are not supported yet and will be available in near future.

How to Use Reliable B2B Tracking

1. Create a Tracking Store Artifact in the Integration Account

• In the Integration Account, create a tracking store artifact that points to an existing Azure Data Explorer (ADX) cluster database.

      

 

• Currently, only one default tracking store is supported per integration account.
• The ADX database must be pre-created before setting up the tracking store.

2. Enable or Disable Tracking in the Agreement Settings

• B2B tracking is also managed at the agreement level.
• By default, tracking is enabled for an agreement.
• To disable tracking, user can set a setting named TrackingState to Disabled in send or receive agreement. To enable again, TrackingState value needs to set to Enabled. Please note that this setting can be updated in JSON view only.

 

 

For tracking to function correctly, both the tracking store in the integration account be configured and TrackingState needs to be set to Enabled in agreement.

Using the Tracking Dashboard

• Before using tracking dashboard, please ensure that some B2B actions are executed so that tracking data is available in tracking store.
• To view the tracking dashboard, please click the

 

 

 

• When the B2B tracking dashboard is opened, the dashboard displays message overview data for 7 days by default.
• To change the data scope to a different time interval, use the TimeRange at the top of the page.
• After the Message Overview Status dashboard loads, users can drill down into specific message types (AS2 or X12) for a more detailed view.
• Selecting the AS2 or X12 tabs provides insights into message processing details, including transaction status, acknowledgments, and failures.

 

 

Managing Tracking Stores via REST API

Reliable B2B Tracking supports a REST API for managing tracking stores. Users can create, update, delete, and retrieve tracking stores programmatically using the following API endpoints.

If users choose to use rest API to create tracking store in integration account, then two ADX database tables named AS2TrackRecords and EdiTrackRecords  need to be created manually in the ADX database with a specific schema and integration account needs to have 'Ingester' permission to the database.

1. Get All Tracking Stores

Retrieves all tracking stores configured in an Integration Account.

GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/integrationAccounts/{integrationAccountName}/groups/default/trackingstores?api-version=2016-06-01

Parameters:

• {subscriptionId} – Azure subscription ID.
• {resourceGroupName} – Name of the resource group.
• {integrationAccountName} – Name of the integration account.

Response:

Returns a list of tracking stores associated with the integration account. Please note that currently only one tracking store per integration account is supported.

2. Get a Specific Tracking Store

Retrieves details of a specific tracking store.

GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/integrationAccounts/{integrationAccountName}/groups/default/trackingstores/{trackingstoreName}?api-version=2016-06-01

Parameters:

• {trackingstoreName} – Name of the tracking store to retrieve.

Response:

Returns details of the specified tracking store.

3. Create or Update a Tracking Store

Creates a new tracking store or updates an existing one.

PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/integrationAccounts/{integrationAccountName}/groups/default/trackingstores/{trackingstoreName}?api-version=2016-06-01

Request Body:

json

{
  "properties": {
    "adxClusterUri": "https://youradxcluster.kusto.windows.net",
    "databaseName": "YourDatabaseName"
  }
}

Parameters:

• adxClusterUri – The Azure Data Explorer cluster URI.
• databaseName – The database name within the ADX cluster.

Response:

Returns the details of the created or updated tracking store.

4. Delete a Tracking Store

Deletes an existing tracking store from the integration account.

DELETE https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/integrationAccounts/{integrationAccountName}/groups/default/trackingstores/{trackingstoreName}?api-version=2016-06-01

Parameters:

• {trackingstoreName} – Name of the tracking store to delete.

Response:

Returns a success response if the tracking store is deleted successfully.

Tracking Database Table Schema

The Azure Data Explorer (ADX) cluster database used for Reliable B2B Tracking stores transaction data in a structured format.

• AS2 transactions are stored in a table named AS2TrackRecords.
• X12 and EDIFACT transactions are stored in a table named EdiTrackRecords.

These tables enable efficient querying and retrieval of B2B tracking data, providing structured insights into message flow, processing status, and troubleshooting details.

Since B2B tracking data is stored in an Azure Data Explorer database, users can leverage Azure Workbook to create visually rich custom dashboards for analyzing their B2B transactions.

If users choose to use rest API to create tracking store in integration account, then these two tables need to be created manually in the ADX database and integration account needs to have 'Ingester' permission to the database. 

For more information, see Reliable B2B Tracking Database Schema

Future Enhancements

To further improve Reliable B2B Tracking, the following enhancements are planned for future releases:

1. Drill into Workflow Run Details from the Tracking Dashboard

Users will be able to navigate directly from the tracking dashboard to the corresponding Logic Apps workflow run details. This feature will allow for faster troubleshooting by linking B2B transactions to their underlying workflow executions.

2. EDIFACT Transaction Tracking

In the future, EDIFACT message tracking will be fully supported, enabling detailed monitoring of EDIFACT interchanges, functional groups, and message transactions.