See how much of your BizTalk solution converts to Azure Logic Apps
Upload a zipped BizTalk solution. We read its orchestrations, maps, schemas, pipelines and binding files, convert it to an Azure Logic Apps (Consumption) workflow, and sort every item into what the demo converts now, what needs the full converter, and what does not convert.
Most migration estimates start with a spreadsheet of orchestrations and a guess. This one starts with your source.
What converts
The demo covers what we have run on Azure Logic Apps (Consumption) end to end: a FILE receive of typed XML, one map, and a flat-file FILE send, over SFTP. The full converter covers more.
Converts in the demo
Adapters and ports
- FILE receive locations (polled over SFTP)
- FILE send ports (written over SFTP)
Pipelines
- XMLReceive on FILE receive locations (typed XML)
- Flat File assembler on send pipelines
Schemas
- XML schemas (the received message type)
- Flat-file schemas used for sending
Maps
- Maps: links between fields
Orchestrations
- Receive (activating, typed XML)
- Construct and Transform
- Send
Needs the full converter
Adapters and ports
- HTTP send ports
- WCF-WebHttp send ports
- SMTP send ports
- Scheduled task receive locations
- HTTP and WCF receive locations
- SOAP, WCF-BasicHttp and WCF-WSHttp send ports
- Dynamic send ports
- Ports without a physical binding
- Request-response receive ports (the orchestration replies)
- Delivery notification on send ports
- Messaging-only routing (send port subscriptions and filters)
- Direct-bound ports (MessageBox publish and subscribe)
Pipelines
- Other default pipelines (XMLTransmit, PassThru)
- Custom pipelines with the XML disassembler or assembler
- Envelope splitting (receive pipeline run in an orchestration)
Schemas
- Property schemas (promoted properties for routing and correlation)
- Envelope schemas
- Flat-file schemas not used by a send pipeline
Maps
- Maps: scripting functoids
- Maps: custom XSLT and compiled code-behind
- Maps with several input messages
Orchestrations
- Message Assignment
- Expression
- Decide
- Loop
- Delay
- Scope with exception handlers
- Throw Exception
- Terminate
- Several orchestrations in one solution
- Call Orchestration
- Correlation sets and convoys
- Listen
- Parallel Actions
- Suspend
- Atomic and long-running transactions
- .NET helper classes called from expressions
- SSO configuration store reads
Pilot benchmark
Single pilot application (Contoso). Experimental, Contoso-specific Azure target; deploymentReady=false. Results are provisional.
Reference: the same Contoso solution run on native BizTalk Server 2020. Two orders produce two flat-file lines (21 and 30 bytes) in files named with a braced GUID.
| Converter | Unchanged output | After recorded repairs |
|---|---|---|
| EuclidEngine (this converter) to Azure Logic Apps Consumption | Matched native BizTalk byte for byte on both orders, with braced-GUID file names (v4 Azure run) | No repairs |
| Microsoft Migration Agent to Logic Apps | First-pass output did not run | Passed 2/2 only after manual repairs |
| Apache Camel Kit (AI-guided) to Camel | Route failed on both inputs | Passed 2/2 after one repair |
| Art2link ESB Starter | Not tested | Not tested |
- The current v12 target was checked with separate Azure provider controls; the original two orders were not rerun on v12.
- Regenerating the Azure package is deterministic and takes about 0.2 s (median 0.212 s over 3 runs), excluding Azure setup.
- Scripted Azure setup to the first workflow run took at most about 34 s (v4 trial).
Move your BizTalk portfolio to Azure
Tell us about your BizTalk estate. The full converter takes whole solutions to Azure Logic Apps: several orchestrations, other adapters and richer maps included.