BizTalk estate inventory2026-11-09

What the application actually connects to

Parsed from the bindings export: every send port, receive location and adapter, with the target-platform mapping for each.

25 ports across 9 adapters, 3 orchestration(s), 4 findings.

Ports25 Adapters9 Orchestrations3 Effort floor24.0 days

Adapters, and what each becomes

AdapterPortsLogic Apps equivalentDifficulty
FILE12Azure Blob or SFTPeasy
WCF-SQL3SQL Server connectormedium
MQS3IBM MQ (ISE only)hard
FTP2FTP connectoreasy
SFTP1SFTP connectoreasy
SMTP1Office 365 Outlookeasy
WCF-BasicHttp1HTTP connectoreasy
WCF-SAP1SAP connectorhard
WCF-Custom1varieshard

Ports

PortAdapterAddressBecomes
SP_Walmart_850_Out
send
FILE\\fileserver01\edi\out\walmart\850\%MessageID%.xmlAzure Blob or SFTP
SP_Walmart_856_Out
send
FILE\\fileserver01\edi\out\walmart\856\%MessageID%.xmlAzure Blob or SFTP
SP_Target_850_Out
send
FILE\\fileserver01\edi\out\target\850\%MessageID%.xmlAzure Blob or SFTP
SP_Target_810_Out
send
FILE\\fileserver01\edi\out\target\810\%MessageID%.xmlAzure Blob or SFTP
SP_Kroger_855_Out
send
FILE\\fileserver01\edi\out\kroger\855\%MessageID%.xmlAzure Blob or SFTP
SP_Asn_Archive
send
FILE\\fileserver01\edi\archive\asn\%MessageID%.xmlAzure Blob or SFTP
SP_Invoice_Archive
send
FILE\\fileserver01\edi\archive\invoice\%MessageID%.xmlAzure Blob or SFTP
SP_Legacy_Backup
send
FILE\\nas02\legacy\drop\%MessageID%.xmlAzure Blob or SFTP
SP_SQL_OrderStatus
send
WCF-SQLmssql://sqlprod01/OrdersSQL Server connector
SP_SQL_InventorySync
send
WCF-SQLmssql://sqlprod01/InventorySQL Server connector
SP_MQ_Walmart
send
MQSMQ://mqhost01/QM1/WALMART.REPLYIBM MQ (ISE only)
SP_MQ_Kroger
send
MQSMQ://mqhost01/QM1/KROGER.REPLYIBM MQ (ISE only)
SP_FTP_Target
send
FTPftp://ftp.target.example/outboundFTP connector
SP_SFTP_Amazon
send
SFTPsftp://sftp.amazon.example/outboundSFTP connector
SP_SMTP_Alerts
send
SMTPsmtp://mail.example.comOffice 365 Outlook
SP_HTTP_TaxService
send
WCF-BasicHttphttps://tax.example.com/rateHTTP connector
SP_SAP_Customer
send
WCF-SAPsap://sap01/00/SAP connector
SP_Legacy_Custom
send
WCF-Customcustom://legacy-bridgevaries
RL_Walmart_850
receive
FILE\\fileserver01\edi\in\walmart\*.xmlAzure Blob or SFTP
RL_Target_810
receive
FILE\\fileserver01\edi\in\target\*.xmlAzure Blob or SFTP
RL_Kroger_855
receive
FILE\\fileserver01\edi\in\kroger\*.xmlAzure Blob or SFTP
RL_Amazon_ASN
receive
FILE\\fileserver01\edi\in\amazon\*.xmlAzure Blob or SFTP
RL_MQ_Inbound
receive
MQSMQ://mqhost01/QM1/INBOUNDIBM MQ (ISE only)
RL_FTP_Inbound
receive
FTPftp://ftp.partner.example/inFTP connector
RL_SQL_Poll
receive
WCF-SQLmssql://sqlprod01/OrdersSQL Server connector

Findings

HIGH Adapters with no clean Logic Apps equivalent

5 port(s): MQS ×3, WCF-SAP ×1, WCF-Custom ×1. IBM MQ and SAP need an Integration Service Environment or an on-premises gateway; neither is a consumption-plan connector.

Do this: Price these before the rest of the migration. They decide whether the project is a lift or a redesign.

HIGH File ports on a UNC share

12 of 12 file ports read or write \\server\share paths. Moving to Blob or SFTP changes the operational model: no more 'drop it in the folder and watch'.

Do this: Inventory who watches those folders today. That is the workflow that breaks first.

MEDIUM 11 file ports depend on one host (fileserver01)

A single file server is both a single point of failure and a throughput ceiling. In the new design the equivalent is one storage account, which is better, but only if the concurrency was not load-bearing.

Do this: Check for ports that poll the same folder. Blob triggers and polling connectors behave differently under contention.

LOW Wide adapter surface

9 distinct adapters: FILE, FTP, MQS, SFTP, SMTP, WCF-BasicHttp, WCF-Custom, WCF-SAP, WCF-SQL. Each one is a separate connector, credential and failure mode in the target platform.

Do this: Group the migration by adapter, not by trading partner; it makes the cutover testable in slices.

What the bindings cannot see

This file proves the wiring. It does not contain orchestration logic, maps, pipeline components, business rules, or the credentials behind each adapter. Ask for the orchestration names, one map per document type, and the list of custom pipeline components before quoting the build.