Exposing On-Premise BizTalk Service to Internet with Service Bus & WCF-Relay Adapter

In this article, I would walk through on how to leverage WCF-Relay adapter to expose on-premise BizTalk service for public access.

Refer my earlier article for Boomerang pipeline component, as I would use the same component over here.

Lets create a two way service which receives the request and renders a transformed message. As show below create receive port  and a receive location with WCF-BasicHttpRelay binding, then provide the relay URL and configure the SAS Policy under Bindings Tabs.

Here is simple token provider console application, which generates the access token. This token has to be passed as authentication header in order to access the service.

Lets generate the token and using post man, these test the on-premise BizTalk service by posting a HTTP request with a valid request body.

As shown, transformed response would be rendered back to the client. By this way, we can access our on-premise service over the internet. Key take is that we can leverage BizTalk transformations from Azure Functions/Logic Apps instead of writing custom API to achieve complex transformation involving functiods.

Hybrid Adapters BizTalk Server 2016 | Event Hub & Service Bus Messaging Adapters

In this article, I would brief on configuring BizTalk 2016 Hybrid Adapters like Service Bus Message(Queues) and EventHub. These adapaters can be configured at receive and send ports.

Here, I have a Azure function which would act as a publisher to Event Hub and Service Bus Queue, you can refer my earlier Azure Function blog post.

Lets create a simple messaging solution for our demo purpose; then add and configure EventHub adapter as shown below, By Signing into Azure Account, we can configure the appropriate EventHub instance and its related SAS policy. 

Now, lets configure the SB Messaging Adapter, please provide the SB namespace and the queue name; In authentication tab provide relevant SAS Policy.

Let create a subscription inside BizTalk at the Sendports with ReceivePortName for EventHub and SB Messages; let test and verify the end to end flow.