Create and Manage Hybrid Connections

Important

BizTalk Hybrid Connections is retired, and replaced by App Service Hybrid Connections. For more information, including how to manage your existing BizTalk Hybrid Connections, see Azure App Service Hybrid Connections.

Important

BizTalk Services is deprecated in the Azure portal. To manage your MABS instances, see REST API for Managing BizTalk Services on Azure.

Overview of the Steps

  1. Create a Hybrid Connection by entering the host name or FQDN of the on-premises resource in your private network.
  2. Link your Azure web apps or Azure mobile apps to the Hybrid Connection.
  3. Install the Hybrid Connection Manager on your on-premises resource and connect to the specific Hybrid Connection. The Azure portal provides a single-click experience to install and connect.
  4. Manage Hybrid Connections and their connection keys.

This topic lists these steps.

Important

It is possible to set a Hybrid Connection endpoint to an IP address. If you use an IP address, you may or may not reach the on-premises resource, depending on your client. The Hybrid Connection depends on the client doing a DNS lookup. In most cases, the client is your application code. If the client does not perform a DNS lookup, (it does not try to resolve the IP address as if it were a domain name (x.x.x.x)), then traffic is not sent through the Hybrid Connection.

For example (pseudocode), you define 10.4.5.6 as your on-premises host:

The following scenario works:
Application code -> GetHostByName("10.4.5.6") -> Resolves to 127.0.0.3 -> Connect("127.0.0.3") -> Hybrid Connection -> on-prem host

The following scenario doesn't work:
Application code -> Connect("10.4.5.6") -> ?? -> No route to host

Create a Hybrid Connection

A Hybrid Connection can be created in Azure App Service Hybrid Connections or using BizTalk Services REST APIs.

Additional

  • Multiple Hybrid Connections can be created. See the BizTalk Services: Editions Chart for the number of connections allowed.
  • Each Hybrid Connection is created with a pair of connection strings: Application keys that SEND and On-premises keys that LISTEN. Each pair has a Primary and a Secondary key.

Link your Azure App Service Web App or Mobile App

To link a Web App or Mobile App in Azure App Service to an existing Hybrid Connection, select use an existing Hybrid Connection in the Hybrid Connections blade.

Install the Hybrid Connection Manager on-premises

After a Hybrid Connection is created, install the Hybrid Connection Manager on the on-premises resource. It can be downloaded from your Azure web apps or from your BizTalk Service.

Important

BizTalk Services is deprecated in the Azure portal. To manage your MABS instances, see REST API for Managing BizTalk Services on Azure.

Azure App Service Hybrid Connections is also a good resource.

Additional

  • Hybrid Connection Manager can be installed on the following operating systems:

    • Windows Server 2008 R2 (.NET Framework 4.5+ and Windows Management Framework 4.0+ required)
    • Windows Server 2012 (Windows Management Framework 4.0+ required)
    • Windows Server 2012 R2
  • After you install the Hybrid Connection Manager, the following occurs:

    • The Hybrid Connection hosted on Azure is automatically configured to use the Primary Application Connection String.
    • The On-Premises resource is automatically configured to use the Primary On-Premises Connection String.
  • The Hybrid Connection Manager must use a valid on-premises connection string for authorization. The Azure Web Apps or Mobile Apps must use a valid application connection string for authorization.
  • You can scale Hybrid Connections by installing another instance of the Hybrid Connection Manager on another server. Configure the on-premises listener to use the same address as the first on-premises listener. In this situation, the traffic is randomly distributed (round robin) between the active on-premises listeners.

Manage Hybrid Connections

Important

BizTalk Services is deprecated in the Azure portal. To manage your MABS instances, see REST API for Managing BizTalk Services on Azure.

Azure App Service Hybrid Connections is also a good resource.

Copy/regenerate the Hybrid Connection Strings

Important

BizTalk Services is deprecated in the Azure portal. To manage your MABS instances, see REST API for Managing BizTalk Services on Azure.

Azure App Service Hybrid Connections is also a good resource.

Use Group Policy to control the on-premises resources used by a Hybrid Connection

  1. Download the Hybrid Connection Manager Administrative Templates.
  2. Extract the files.
  3. On the computer that modifies group policy, do the following:

    • Copy the .ADMX files to the %WINROOT%\PolicyDefinitions folder.
    • Copy the .ADML files to the %WINROOT%\PolicyDefinitions\en-us folder.

Once copied, you can use Group Policy Editor to change the policy.

Next

Hybrid Connections Overview

See Also

REST API for Managing BizTalk Services on Microsoft Azure
BizTalk Services: Editions Chart
Create a BizTalk Service
BizTalk Services: Dashboard, Monitor and Scale tabs