Upgrade existing on-premises BizTalk Solutions
If the business is already invested in BizTalk solutions, we have two migration paths:
- Lift and Shift:
By this approach, we move all BizTalk Servers and dependent systems to Azure VMs. It is recommended to move all dependent systems to Azure VMs too to avoid network connectivity issues between Azure VMs and on-premises systems.
The benefits are:
- Reduced infrastructure costs: we can provision the VMs with basic load requirements and scale them upon demand. Azure VM gives the option to BYOL (Bring your own license), i.e. we don’t need to buy new Windows, BizTalk Server and SQL Server for Azure VMs as we can use existing license from an on-premises setup.
- Reliability: we should deploy Azure VMs with an Availability Set. Azure makes sure that the VMs you place within an Availability Set run across multiple physical servers, compute racks, storage units, and network switches. If a hardware or software failure happens, only a subset of your VMs is impacted and your overall solution stays operational. Azure VMs also provide periodic backups that are saved in geo-redundant storage.
- Hybrid Integration
Hybrid Integration means that some legs of integration solution are running on on-premises BizTalk Server and some parts of the solution are up in the Cloud. BizTalk 2016+ offers adapters to connect to Azure iPaaS components like Logic Apps, Service Bus and Azure Functions.
Logic Apps adapter in BizTalk provides seamless and secure connectivity to Azure-hosted Serverless Logic Apps. With Service Bus Messaging and Event Hub adapters in BizTalk, we can exchange messages with Azure Service Bus and Event Hub. Essentially, we can keep some of our processes within on-premises environments and move integrations with SaaS products on Azure.
This diagram illustrates the end-to-end (E2E) architecture of B2B integration in the cloud. The left side shows an external trading partner, while the right side shows internal line-of-business (LOB) partners. The middle highlights the heart of the integration pipeline, in this case, B2B processing using Azure Logic Apps.
A core principle for any migration is putting minimal to zero impact on partners and systems, both upstream and downstream. This principle is the reason why BizTalk Server still appears in the pipeline. Here, the BizTalk Server is only used as a proxy for connecting from Azure to LOB apps on the corporate network without requiring any changes from downstream systems. This approach is an interim strategy, so we plan to remove the BizTalk Server in the next phases.
If you need help in deploying them in your current infrastructure, get in touch with our Microsoft Certified Experts and schedule a 15-minute assessment by filling out your contact information below.
You may read Part 1 of the ‘BizTalk migration to Azure iPaaS’ series here.