How Messages get Routed from a Bridge
Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.
If you're brand new to Logic Apps, then we suggest getting started here:
There can be many aspects to a simple routing operation between two components of a message flow. These could be:
Where to route the message to? As part of this, you define the destination of the message that has been processed by the bridge. See The Routing Destination
On what condition will the routing be done? This typically is driven by the business scenario which describes the parameters on which the routing is done. For example, all requests for mobile phone divisions should be passed on to department A, and so on. See The Routing Condition.
In which order should the routing be done? If there is more than one condition for routing, you must also set the order in which the routing conditions are honored. See The Routing Order.
Do any specific actions need to be performed on the message before routing? This is especially targeted for protocol bridging scenarios where the message sender and the message receiver operate on different message protocols. To bridge such protocol mismatch, you can perform certain actions on the message before it is finally routed. For more information on how the protocol mismatch is bridged, see Route and Reply Actions: Bridging Protocol Mismatch.
All these points are discussed in detail, with instructions on how to achieve them, at Routing Messages from Bridges to Destinations in the BizTalk Service Project.