Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: Azure Logic Apps (Standard)
The validation process can be difficult because you can easily miss behavior differences between source and target systems. After you generate the Standard logic app project, workflows, and other artifacts, verify the workflow behavior against the source system's behavior before you deploy them to Azure Logic Apps. In the Validation stage, the Azure Logic Apps Migration Agent in Visual Studio Code helps run the generated workflows and check whether the triggers, actions, transformations, and connections work correctly.
This article describes the general process that the migration agent follows to test the generated Standard workflows against the source behavior, compare the results, and identify any problems or gaps you need to resolve.
Validation actions
The Validation stage tests your generated Standard workflows against the original source specifications and behavior. The @migration-converter agent follows the generated validation tasks, while you provide representative inputs and expected results and review the evidence.
Important
Before you start, make sure that you reviewed the workflows, connections, and any .NET local functions for correct information and configuration compared to the source behavior.
For more information, see:
| Step | Action | Description |
|---|---|---|
| 1 | Validate the runtime | Runs func start --verbose, fixes startup errors, and reruns the command until the runtime starts cleanly. |
| 2 | Prepare test resources | Uses Azurite and local resources where possible, Docker containers for supported local services, and Azure resources only for connectors without a local alternative. |
| 3 | Test behavior | Runs happy-path, failure-path, cross-workflow, retry, timeout, resubmission, and other applicable scenarios. Compares field-level output values with expected source behavior. |
| 4 | Report and resolve discrepancies | Treats incorrect, empty, or truncated output values as failures, records expected and actual results, fixes the cause, and reruns affected tests. |
Validation isn't complete until all required tests pass and the agent creates TEST-REPORT.md in the generated project root. Review this report for per-workflow results, field-level checks, test adaptations, design deviations, provisioned Azure resources, and exact retest commands.
Related content
- Migration automation from integration platforms to Azure Logic Apps
- Quickstart: Migrate an integration project using the Azure Logic Apps Migration Agent