Learn and create Message Maps and Transforms
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:
Transforms in Microsoft Azure BizTalk Services are designed to manipulate data. Consider the following scenario:
An incoming message contains customer data, including First Name, Last Name, Street Address, City, State, and Zip Code. When this data is received, you want to manipulate the data. For example, you want to combine First Name and Last Name into a single Name value.
Microsoft Azure BizTalk Services is your answer. Using a Transform, the incoming message data can be manipulated to the desired output.
XSLT Support: You can:
Import an .xslt or .xsl file or directly enter XSLT syntax
Import an XML extension file or directly enter XML syntax
Use the XslCompiledTransform property for better performance
Use XSLT in every Transform file (.trfm)
When XSLT is used, the Transform design area is grayed out.
Built-in Map Operations: Many Transform scenarios are handled by the built-in Map Operations, including string manipulation, looping with set scope, expressions, list functionality, Date/Time, CSharp scripting, and so on.
xs:extension and xs:restriction: Use complex types in your schemas.
Choose your project: In Visual Studio, you can create a new Transform in its own project (BizTalk Service Artifacts) or create a new Transform in a BizTalk Service project. When created in its own project, a Transform can be added to an X12 agreement between EDI partners.
Add the Transform to a bridge: After a Transform is created, the Transform can be added to the Transform stage within a XML One-Way Bridge or a XML Request-Reply Bridge.