What Microsoft released
On 20 November, during Ignite week, Microsoft's integration team published three related updates for Azure Logic Apps. Firms run Hybrid Logic Apps on infrastructure they manage themselves. The first update makes SQL Server as the storage provider for Hybrid Logic Apps generally available. That means workflow runs, execution state, triggers, jobs and queue processing can all sit in a SQL Server database the business owns.
The second post adds semi-connected support for Integration Accounts. Integration Accounts hold the schemas, maps, trading partner records and agreements behind EDI and XML workflows. Hybrid Logic Apps can now cache those items in the local SQL database and keep using them when the Azure connection drops. The cache refreshes once the connection comes back.
The third post puts a built-in MSMQ connector for Logic Apps Standard into public preview. Workflows can now send messages to Microsoft Message Queuing and be triggered by them, through a broker service that the customer runs on a Windows server. Microsoft's Ignite roundup on 17 November also said hybrid deployments now support more Kubernetes environments, naming RKE2 and Red Hat OpenShift, and that the HL7 healthcare messaging connector is generally available.
Why the three updates belong together
Each post looks minor on its own. Read together, they're aimed at organisations still running BizTalk Server, Microsoft's on-premises integration product. Plenty of NZ distributors, manufacturers and health providers use BizTalk to pass orders and invoices between their ERP and their trading partners. The MSMQ post says outright that the connector is "particularly useful for BizTalk Server modernization."
The timing is set by Microsoft's lifecycle page for BizTalk Server 2020: mainstream support ends in April 2028 and extended support in April 2030. April 2028 is about 17 months away. In our experience, the slow part of moving an integration estate off BizTalk is retesting every trading partner, and rebuilding the workflows takes less time than that.
Two objections have kept many integration teams on BizTalk. Moving EDI to the cloud means an Azure or internet outage stops orders flowing. Older line-of-business applications that talk through MSMQ also had no clean path into Logic Apps. The semi-connected cache goes part of the way on the outage problem, and the MSMQ connector gives the legacy applications a bridge while they're replaced.
What the fine print says
Microsoft's semi-connected post includes the line "Semi-connected does not mean fully disconnected," and the limits back that up. The first sync needs Azure access, and only items already synced are available during an outage. Changes made in Azure don't reach the local cache until the connection returns. Operations that need live access to private certificate keys in Azure Key Vault, which covers some signing and decryption, still need the cloud. Trading partners who require signed or encrypted messages may therefore still be cut off during an outage. The post gives no maximum time a hybrid runtime can stay offline.
The SQL storage post puts a lot of operational work back on the customer. Provisioning, capacity planning, availability, backup and disaster recovery, security and patching all belong to the organisation running the database. Microsoft warns against changing runtime tables or deleting records directly to free up space. The post also says SQL storage doesn't replace source control for workflow definitions. The feature only applies to Hybrid Logic Apps, so Logic Apps Standard hosted by Microsoft doesn't use it.
The MSMQ connector has preview limits that matter for older order and dispatch flows. Messages are delivered at least once, so a workflow that receives the same message twice must handle the duplicate safely. Ordered delivery isn't supported during the preview. The broker isn't cluster-aware, so failover isn't fully covered, and the trigger handles messages one at a time. Each message is capped at about 4 MB including overhead. The broker needs Windows Server 2019 or later and private network access from Logic Apps.
None of the three posts mention pricing.
What it means for NZ businesses
The updates make hybrid a credible option. Hybrid also asks more of your own team than BizTalk on a pair of virtual machines did. Running Logic Apps on Kubernetes and keeping a production SQL Server highly available are skills many mid-sized NZ IT teams don't have in house. For most interfaces, Logic Apps hosted in Azure will be simpler to run. Hybrid earns its extra overhead in three cases: a site with unreliable connectivity, such as a plant or a regional depot; a hard requirement to keep run data on your own servers; or partner flows that can't stop for the length of a likely outage.
Microsoft's roundup cites the Kentucky Cabinet for Health and Family Services, which moved from BizTalk to Azure Integration Services and now processes about 7 million transactions a day across more than 60 partners. A typical NZ estate is a fraction of that size, which helps the case for keeping the design simple. BizTalk orchestrations that rely on ordered message handling will need to be redesigned rather than copied across, at least until the MSMQ connector supports ordering. Integration work like this is usually tied to an ERP upgrade, so it's worth planning the two together on one ERP timeline.
Next steps
- List every BizTalk interface by partner and message type. Mark the ones that use MSMQ, need ordered delivery or exchange signed or encrypted messages.
- Choose Azure-hosted or hybrid for each interface. Pick hybrid only where connectivity, data location or outage tolerance justifies it.
- If you're testing hybrid, fill the Integration Account cache and then cut the Azure connection in a test environment. Run real sample transactions and record which ones fail, signed messages in particular.
- Before the first production workload goes live, name an owner for the SQL Server behind Hybrid Logic Apps, covering backups, high availability and patching.
- Treat the MSMQ connector as a bridge while it's in preview. Make receiving workflows safe to run twice on the same message, and keep flows that depend on message order on BizTalk until ordering is supported.
- Get hybrid and Integration Account pricing from your Microsoft partner in writing, and compare it with the BizTalk licensing and server costs you pay now.
- Work back from April 2028 and leave enough time to retest every trading partner. Our process and automation team can help scope that inventory.
Sources
- Announcing general availability of SQL as a storage provider for Hybrid Logic Apps
- Announcing semi-connected Integration Account support for Hybrid Logic Apps
- Announcing the MSMQ built-in connector for Azure Logic Apps Standard
- What's new in Azure Logic Apps at Microsoft Ignite 2026
- BizTalk Server 2020 - Microsoft Lifecycle
- Ignite 2026 Day 1: What Changes for Power Platform Makers and Admins
- matts-ignite-2026-list (GitHub)
Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.
Get my free assessment How we help