Create Rich Messaging Endpoints on Azure
Important
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:
-
Create your first logic app, or quickly get started using a pre-built template
-
View all the available connectors you can use in your logic apps
The topic Add Source, Destination, and Bridge Messaging Endpoints discusses how such endpoints provide the ability to connect to disparate LOB applications and the ability to validate, transform, and extract properties from a message. The topic Tools for Creating Message Schemas provides information on the BizTalk Service project design surface that can be used to configure such endpoints.
An end-to-end message processing entity may contain a message source (for receiving the message), message processing unit (such as a bridge), and finally a message destination (where the message is routed). So, configuring a rich messaging endpoint might include configuring all three components. This section provides the procedural information on how to configure all these components using the BizTalk Service project.
Note
Even though Transforms are a part of rich messaging endpoints, they can either be configured as part of the BizTalk Service project or created separately before they are added to the message flow.