Microsoft has several postings which document deprecated adapters:
- What's New in BizTalk Server 2013 and 2013 R2
- BizTalk 2010 Deprecated Features, Tools, and APIs
- BizTalk 2009 Deprecated Features, Tools, and APIs
- BizTalk 2006R2 Deprecated Features, Tools, and APIs
None of the above Microsoft links discuss HTTP. I would suspect that there is some confusion because the SOAP adapter is indeed deprecated.
That being the case, I decided to open a ticket with Microsoft Support and get the story directly from Microsoft. Here's the reply:
Hello Bruce,
Thank you for contacting Microsoft Support. My name is Nikhil Jain. I am the Support Professional who will be working with you on this Service Request. You may reach me using the contact information listed below, referencing the SR number (xxxxxxxxxxx).Regarding your query I would like to inform you that Microsoft never deprecated HTTP adapter. We still support it. It is the SOAP adapter which is deprecated not the HTTP. I tried calling you @ +1 (xxx)xxx-xxxx however reached voice mail.If you have any questions or concerns, please let me know.
Thanks and RegardsNikhil Jain| Support Engineer | Microsoft Developer Support | BizTalk Server, WFM and MSMQ
So this puts the question to bed. The legacy HTTP adapter is still supported and is NOT deprecated.
Although it does make sense to migrate to WCF, there isn't a need to rush the migration from HTTP to WCF as some would think.