I learnt something new about SOAP adapter today so thought of sharing. I never realised but BizTalk SOAP adapter by default is configured to look into Orchestration proxy code while creating a SOAP request. In other words message natively formed within orchestartion is mapped to the body (SOAP:Body) part by the adapter by using proxy code embedded in the orchestartion assembly. This became obvious when we tried to create a web request using BizTalk WCF adapter which required mapping applied on a send port to create the request (a bit clunky way in my opinion). Thanks to collegue Nick Heppleston (http://www.modhul.com/) in helping to figure this out