One-to-one mapping of every BizTalk Server component (adapters, pipeline components, orchestration shapes, expressions, custom code, engine features) to its Azure Logic Apps Standard equivalent. Covers 170+ mappings with service provider IDs, operation names, connection parameters, and deployment scopes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
One-to-one mapping of every BizTalk Server component (adapters, pipeline components, orchestration shapes, expressions, custom code, engine features) to its Azure Logic Apps Standard equivalent. Covers 170+ mappings with service provider IDs, operation names, connection parameters, and deployment scopes.
BizTalk Server to Azure Logic Apps Standard — Component Migration Reference
One-to-one mapping of every BizTalk Server component to its Azure Logic Apps Standard equivalent.
Azure Logic Apps Standard provides built-in service provider connectors that run in-process within the runtime, replacing BizTalk Server adapters, pipeline components, accelerators, and engine features. This document maps every BizTalk component to its Logic Apps Standard equivalent, including available triggers and actions.
Key Concepts
Concept
BizTalk Server
Logic Apps Standard
Transport
Adapter (Send/Receive)
Service Provider Connector
Message Processing
Pipeline Component
Built-in Action (XML Operations, Flat File, etc.)
Routing
Publish/Subscribe (MessageBox)
Workflow triggers + conditions
Orchestration
XLANG/s Orchestration
Workflow definition (JSON)
Trading Partners
Party / Agreement
Integration Account
Business Rules
Business Rules Engine (BRE)
Rules Engine action
Maps / Transforms
XSLT Map
XML Operations → Xslt action
Schema Validation
XML Validator pipeline
XML Operations → XmlValidation action
When to Use Integration Account
Use an Integration Account only when the target design requires Integration Account-specific capabilities, such as:
B2B/EDI processing with X12, EDIFACT, or AS2 actions
Trading partners, agreements, and partner resolution
Shared enterprise artifact management where schemas/maps/partner artifacts are centrally managed outside the workflow project
Do NOT choose Integration Account for ordinary XML/XSLT/schema usage if Logic Apps Standard artifact folders are sufficient.
If Integration Account is chosen:
use it consistently for the flow's deployable artifacts; do not split artifacts between Integration Account and Logic App artifact folders
plan for the required app setting WORKFLOWS_INTEGRATION_ACCOUNT_ID
plan for the required app setting WORKFLOW_INTEGRATION_ACCOUNT_CALLBACK_URL
deploy the Integration Account first, then set WORKFLOWS_INTEGRATION_ACCOUNT_ID to the deployed Integration Account resource ID, for example /subscriptions/{subId}/resourceGroups/{rg}/providers/Microsoft.Logic/integrationAccounts/{name}
retrieve the deployed callback URL and set WORKFLOW_INTEGRATION_ACCOUNT_CALLBACK_URL to that real value
plan a separate follow-on task to upload the required Integration Account artifacts after provisioning
Note: No triggers available. Use a workflow with recurrence to poll.
Connection Parameters:ConnectionString (required)
Messaging & Eventing
Azure Service Bus
BizTalk
Logic Apps Standard
Adapter / Connector
ServiceBus, MSMQ, NetMsmq, SB
Azure Service Bus
Service Provider
—
/serviceProviders/serviceBus
Deployment Scope
—
Cloud Only
Category
—
Messaging
Migration Note: BizTalk MSMQ and NetMsmq adapters have no direct cloud equivalent. Azure Service Bus is the recommended replacement for all on-premises queuing patterns.
Migration Note: All WCF-based adapters and the SOAP adapter are consolidated into the single HTTP connector. WCF-specific bindings (NetTcp, etc.) are not natively supported — migrate to HTTP/HTTPS REST or SOAP-over-HTTP patterns.
Migration Note: BizTalk's SMTP adapter is mapped here. For richer Outlook/Gmail/Exchange scenarios, consider the corresponding managed API connectors in Logic Apps.
Type
Operation
Description
Action
sendEmail(default)
Send an email
Note: No triggers available for SMTP. Use a Request trigger or another trigger to initiate email sending.
The following BizTalk adapters are not covered by the connector registry. This table provides recommended migration paths.
#
BizTalk Adapter
Recommended Logic Apps Equivalent
Migration Notes
1
POP3
Office 365 Outlook / Gmail connector (managed API)
BizTalk POP3 receive adapter → use managed API connector for email receive. No built-in service provider.
2
Windows SharePoint Services
SharePoint connector (managed API)
Use the SharePoint Online managed API connector. On-premises SharePoint requires on-premises data gateway.
3
WCF-NetNamedPipe
— (no equivalent)
Inter-process communication only. Migrate to HTTP/HTTPS for service-to-service calls.
4
TIBCO Rendezvous
— (no equivalent)
No Logic Apps connector. Consider Azure Service Bus as messaging middleware, or use Custom Code (local function) with TIBCO SDK.
5
TIBCO EMS
Azure Service Bus / RabbitMQ
No direct connector. Migrate messaging patterns to Service Bus or RabbitMQ.
6
JD Edwards OneWorld
HTTP connector + JDE REST APIs
No direct connector. Use HTTP action to call JD Edwards REST/JSON APIs.
7
JD Edwards EnterpriseOne
HTTP connector + JDE REST APIs
No direct connector. Use HTTP action to call JD Edwards REST/JSON APIs.
8
PeopleSoft Enterprise
HTTP connector + PeopleSoft REST APIs
No direct connector. Use HTTP action to call PeopleSoft Integration Broker REST services.
9
Siebel
HTTP connector + Siebel REST APIs
No direct connector. Use HTTP action to call Siebel REST/SOAP APIs.
10
Oracle E-Business Suite
Oracle Database connector (partial)
Only database operations available via /serviceProviders/oracledb. EBS-specific APIs (Concurrent Programs, etc.) require HTTP + Oracle REST.
Non-Adapter Mappings
These Logic Apps connectors have no BizTalk adapter equivalent (BizTalkAdapters: []). They replace functionality that was embedded in BizTalk pipeline components, accelerators, or engine features.
Pipeline Components (from Registry)
XML Operations
BizTalk Equivalent
Logic Apps Connector
XML Assembler (pipeline)
XmlCompose action
XML Disassembler (pipeline)
XmlParse action
XML Validator (pipeline)
XmlValidation action
XSLT Transform (map)
Xslt action
Type
Operation
Description
Action
XmlParse(default)
Parse XML using a schema
Action
XmlCompose
Compose XML from structured data
Action
XmlValidation
Validate XML against a schema
Action
Xslt
Transform XML using XSLT map
Flat File Operations
BizTalk Equivalent
Logic Apps Connector
Flat File Assembler (pipeline)
FlatFileEncoding action
Flat File Disassembler (pipeline)
FlatFileDecoding action
Type
Operation
Description
Action
FlatFileDecoding(default)
Decode flat file to XML using schema
Action
FlatFileEncoding
Encode XML to flat file using schema
Pipeline Components (Not in Registry)
The following BizTalk pipeline components are not in the connector registry but have Logic Apps equivalents or workarounds.
#
BizTalk Pipeline Component
Logic Apps Equivalent
Migration Notes
1
MIME/SMIME Encoder
Custom Code — local function
No built-in action. Use a Logic Apps native local function (custom code action) to perform S/MIME encryption/signing. Runs in-process within the workflow app.
2
MIME/SMIME Decoder
Custom Code — local function
No built-in action. Use a Logic Apps native local function (custom code action) to perform S/MIME decryption/verification. Runs in-process within the workflow app.
3
Party Resolution
Integration Account partners + agreements
Trading partner resolution is handled through Integration Account configuration, not a pipeline component.
4
JSON Encoder
Built-in (native JSON)
Logic Apps is JSON-native. Use the json() expression to convert strings to JSON. No special component needed.
5
JSON Decoder
Built-in (native JSON)
Logic Apps is JSON-native. Use @json(triggerBody()) or similar expressions. No special component needed.
6
Property Promotion / Demotion
Expressions / Variables / Tracked Properties
Use triggerOutputs(), body(), Compose, Initialize Variable actions. Use tracked properties for visibility.
7
Message Compression (zip/gzip)
extractArchive action (partial) / Custom Code — local function
File System, FTP, and SFTP connectors have extractArchive. For custom compression/decompression, use a Logic Apps native local function (custom code action).
Accelerators
HL7
BizTalk Equivalent
Logic Apps Connector
HL7 Accelerator pipeline components
HL7Decode / HL7Encode actions
Type
Operation
Description
Action
HL7Decode(default)
Decode an HL7 message
Action
HL7Encode
Encode an HL7 message
Note: For transport (MLLP), see MLLP (HL7) above. HL7 connector handles message parsing only.
Expression functions: utcNow(), addDays(), formatDateTime(), etc.
24
Functoids (Conversion)
Expression functions: int(), float(), string(), base64(), etc.
25
Functoids (Cumulative)
XSLT sum(), count() / For Each + Append to Array
No direct visual equivalent; use XSLT or workflow loops.
26
Functoids (Database)
SQL Server action inside Data Mapper / workflow
Call database mid-transform using workflow actions.
27
Functoids (Advanced — Scripting)
XSLT inline scripts / Custom Code — local function
Use <msxsl:script> in XSLT or call a Logic Apps native local function (custom code action) for complex logic.
28
Functoids (Cross Referencing)
Integration Account maps / lookup actions
Use Integration Account for partner-specific value mapping.
29
Liquid Templates
Liquid template action (built-in)
JSON-to-JSON, JSON-to-text transforms. Upload templates to Integration Account.
BizTalk Expressions → Logic Apps Expressions
BizTalk orchestrations use XLANG/s expressions (a C#-like syntax) for string manipulation, message construction, property access, and logic. Logic Apps Standard uses the Workflow Definition Language (WDL) expression syntax.
