Publish BizTalk SOAP endpoints in API Management
Expose your BizTalk SOAP endpoints as services within Azure API Management.
Starting with BizTalk Server 2016 Feature Pack 1, you can expose a SOAP endpoint through API Management from BizTalk. You can do this using API Management in the Azure portal.
Starting with BizTalk Server 2016 Feature Pack 2, you can expose a WCF-BasicHTTP receive location as an endpoint within Azure API Management using BizTalk Administration.
What is API Management? is a great resource to understand and learn more about this Azure service.
- Configure and set up Azure API Management
- Create a virtual network between your BizTalk computer and the API Management instance
- Install Feature Pack 2 on the BizTalk Server
Create using API Management in Azure portal
In the Azure portal, open up your API management, and select APIs:
Configure your WSDL properties:
WSDL specification : Enter the full URI to your BizTalk SOAP endpoint. For example, enter something like
SOAP pass-through or SOAP to REST : Select your preference:
- SOAP to REST: Create REST-based HTTP APIs from an existing SOAP-based web service
- SOAP pass-through: Acts as a proxy for the SOAP API
Enter your preferred Display Name, Name, Description, API Url suffix, Products, and Version.
When finished, your WSDL configuration looks something like the following:
Create using the BizTalk Administration
This feature is supported with WCF-BasicHTTP receive locations.
In the BizTalk Administration Console, right-click your WCF-BasicHTTP receive location, and select Publish to API Management:
Configure your API management properties:
Sign-in to your Azure subscription, select the Subscription and Resource Group that has your API management service, and then select your service.
The WSDL specification link is automatically populated with your WSDL file. Replace localhost with the DNS name or IP address of the BizTalk Server.
Select SOAP pass-through or SOAP to REST:
- SOAP to REST: Create REST-based HTTP APIs from an existing SOAP-based web services
SOAP pass-through: Acts as a proxy for the SOAP API
The API can be published both ways by changing the API URL suffix, and then publishing again using a different API type.
The API name is automatically populated with the receive location name.
Select an API URL suffix that is to be used by consumers of the API.
When finished, your properties look similar to the following:
Select Publish. When successful, the receive location is displayed as a service in API Management in the Azure portal.
Azure API Management is a powerful service that is used by a lot of Azure services, including Logic Apps. API Management includes many features, including rate limits and quotas, who has access to your APIs, caching, and more. See What is API Management? to get started.