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)
Note
This preview feature is subject to the Supplemental Terms of Use for Microsoft Azure Previews.
Before you can start a migration, you need to understand the artifacts in your source integration projects. In Visual Studio Code, the Azure Logic Apps Migration Agent helps automate this task by scanning your source project files during the Discovery stage, detecting the source platform, and cataloging artifacts and dependencies. The agent then identifies logical flow groups, architecture, and migration gaps so you have the information you need to move to the Planning stage.
This article explains how the Azure Logic Apps Migration Agent scans your source, inventories your project assets, and generates a visualization that describes your integration architecture with its components and dependencies.
Discovery stage actions
In Visual Studio Code, after you open the Azure Logic Apps Migration Agent on the Activity Bar, and select the source folder, the migration agent automatically completes the following steps by using the @migration-analyser GitHub Copilot agent:
| Step | Action | Description |
|---|---|---|
| 1 | Detect platform | Examines file patterns to identify the source platform. For example, .btproj and .odx files indicate a BizTalk Server project, while mule-*.xml files indicate a MuleSoft Anypoint project. For more information, see: - BizTalk artifact support - MuleSoft artifact support |
| 2 | Scan files | Scans source files and extracts metadata into Intermediate Representation (IR) format by using a built-in parser for the detected platform. |
| 3 | Catalog artifacts | Inventories discovered artifacts, including the following items: - Orchestrations and workflows - Schemas (XSD, JSON) - Maps and transformations - Pipelines - Send ports and receive ports - Bindings and endpoint configurations |
| 4 | Build dependency graph | Generates a dependency graph that shows how artifacts relate to each other. For example, the graph shows which orchestrations reference which schemas and maps. |
Source design analysis and results
After the migration agent completes the initial scan, the agent performs a deeper, AI-powered analysis by using the @migration-analyser GitHub Copilot agent:
| Action | Description |
|---|---|
| Detect flow groups | Groups related artifacts into logical flow groups, which are sets of artifacts that work together to implement a business process. |
| Visualize architecture | Generates interactive Mermaid diagrams that show the overall system architecture. |
| Map message flows | Traces message flows starting with trigger event, through processing, and to completion for each flow group. |
| Analyze dependencies | Identifies missing or unresolved dependencies that might affect migration. |
| Identify gaps | Reports source platform features without direct equivalents in Azure Logic Apps (Standard) and recommended workarounds. |
| Detect patterns | Identifies common integration patterns such as publish-subscribe, request-reply, scatter-gather, and batch processing. |
For more information, see Migration stage 1: Discovery.
Flow visualization and results
After you start the source design analysis for a logical flow group, the migration agent generates and opens a flow visualization where you can explore your integration architecture through the following interactive views:
| View | Shows |
|---|---|
| Architecture Diagram | A system architecture diagram with all artifacts and connections, rendered as a Mermaid diagram. |
| Message Flow | One or multiple per-artifact message flows from trigger to completion. |
| Components | A components inventory with details such as adapters, endpoints, and pipelines. |
| Missing Dependencies | Any dependencies that were missing or unresolvable during discovery. |
| Gap Analysis | Any source platform features without a direct equivalent in Azure Logic Apps, including suggested resolutions. |
| Patterns | Any detected integration patterns such as publish-subscribe, request-reply, and batch processing. |
| Learn BizTalk | A discovery report based on the findings, for example, about any existing message flow layers and proposed mappings to Azure Logic Apps or other services alternatives. |
The following example shows a sample flow visualization and results:
You can switch between the interactive tabs to review your integration architecture. To learn more about this architecture, you can use the GitHub Copilot chat window to ask the @migration-analyser agent questions about the detected architecture, request corrections, and regenerate the analysis.
For more information, see Discovery stage - Step 3: Analyze source design.
Related content
- Migration automation from integration platforms to Azure Logic Apps
- Quickstart: Migrate an integration project using the Azure Logic Apps Migration Agent