Navigating the Migration from BizTalk to Azure: Overcoming the Business Rule Engine Challenge

As organisations continue their journey towards digital transformation, moving away from legacy systems like BizTalk and migrating to cloud solutions has become a priority. At 345 Technology, one of our key services is helping businesses transition from their old BizTalk servers to the modern cloud. However, this migration often comes with its own set of challenges, and one of the common hurdles is dealing with the business rule engine (BRE) that BizTalk users rely on. 

Understanding the Business Rule Engine (BRE) 

The BRE in BizTalk is a powerful tool that allows users to implement and manage business logic through rules that can be dynamically updated without redeploying applications. This flexibility makes it an attractive option for many organisations, as it enables rapid changes and configurations on the fly. The BRE consists of a database and a Windows service that sits over it, allowing interaction through orchestrations or code. It’s not just used for traditional rule-setting; many users have leveraged it for broader configuration tasks, making it an integral part of their BizTalk infrastructure. 

The Migration Challenge 

The challenge arises because BizTalk’s BRE has not historically been natively supported in Azure. As organisations look to move their workloads to the cloud, they find themselves grappling with the lack of a direct equivalent in Azure. While rules engines were once seen as a core part of an integration toolset, the market has grown quieter on this front, leaving many organisations in search of viable alternatives. However, the need for such engines remains strong—after all, business rules are fundamental, with many still needing that “if this, then that” functionality. 

The Good News: Azure’s Business Rule Engine 

The good news is that Azure’s business rule engine is now in public preview. This marks a significant step forward, as it allows businesses to directly migrate their BizTalk BRE rulesets into Azure. However, it’s important to note that it’s not yet generally available, so if you’re looking to deploy this solution in a live environment, you’ll need to wait until it’s GA. 

Do You Really Need the Business Rule Engine? 

As you consider your migration options, it’s worth asking whether you truly need the BRE in its traditional form. If your use of BRE is primarily for configuration purposes—such as making changes without redeploying applications—there are now alternatives within Azure that might suit your needs better. The modern cloud stack offers a variety of tools that can provide similar functionality, often with greater flexibility and integration potential.  Perhaps your rules would be better expressed as code and deployed as Azure Functions, or as microservices.  Perhaps you should be using Azure App Configuration for configuration. 

Innovate and Explore Alternatives 

Now is the perfect time to innovate. Instead of simply replicating what you have in BizTalk, take a moment to analyse how you’re using the BRE. Are there more modern, efficient tools in Azure that could serve your needs just as well, or even better? This could be an opportunity to streamline your solution, reduce complexity, and fully utilise the capabilities of the cloud. 

Next steps...

At 345 Technology, we’re here to help guide you through these decisions. Whether you’re considering waiting for Azure’s BRE to become generally available or exploring alternative solutions, our team can provide the expertise and support you need to make the best choice for your business. Contact us today to discuss your migration journey and how we can help you overcome the challenges of moving from BizTalk to the cloud. 

Further reading

BizTalk Migration Funding