In this talk, Mark shared his experience in translating BizTalk Server maps into Logic Apps.

1. Migrating BizTalk Maps To Azure
Some personal experiences
Mark Brimble
Integration Architect
BidOne Ltd
1

2. Premise for this talk
You can migrate BizTalk maps to Azure.
9/1/2020
2

3. Topics for Discussion
•A migration strategy.
•Migrating BizTalk Maps to Azure.
9/1/2020
3

4. A Migration Strategy
•http://www.integrationusergroup.com/migrating-biztalk-
solutions-to-azure/
9/1/2020
4

5. A Migration Strategy
•https://www.youtube.com/watch?v=z6FJ1qsbDeA&t=5s
9/1/2020
5

6. A Migration Strategy
AU Blob
Storage
AU Service Bus
each Customer Invoice has a
different property
AU Invoice Pre-
Processing
AU Customer 1 AU Customer 2 AU Customer 3 AU Customer 4
AU Customer 2
Invoice Post-
Processing
AU Customer 3
Invoice Post-
Processing
AU Customer 4
Invoice Post-
Processing
AU Customer 1
Invoice Post-
Processing

7. Key Design Assumptions
1. Using BizTalk Schemas, Maps and Trading Partner Agreements will
make migration quicker.
2. Azure Service Topics & Azure Storage to provide points of persistence.
• For retries in case of micro internet outages
• Publish subscribe model to replace the same in BizTalk Server.
3. Solutions can be migrated without touching any third –party
applications.
4. Transport protocols and message formats do not need to change.
7

8. Migrating BizTalk Maps
•Reuse BizTalk Maps with an Integration Account.
•Integration Account Pricing considerations
•Other Azure mapping techniques
9/1/2020
8

9. Integration Accounts
9

10. Why I need an Integration Account
• Reuse BizTalk schemas and maps
• XML ->XML maps
• Flat file schemas
• AS2/EDIFACT message exchange
• Certificates
• Trading partners
• Trading partner agreements
10

11. Integration Accounts – XSLT Maps
The problem of XSLT extension objects.
• Custom functoids
• Microsoft Database lookup functoids
• Helper classes
I deconstructed into C# scripting functoids and separate database actions.

13. Integration Accounts – Liquid Templates
https://shopify.github.io/liquid/basics/introduction/

14. https://www.connected-pawns.com/2019/03/25/azure-
xml-json-liquid-templates/

15. Integration Account Tiers – Aug 2019
FREE BASIC STANDARD
EDI Trading Agreements 10 1 1,000
EDI Trading Partners 25 2 1,000
Maps 25 500 1,000
Schemas 25 500 1,000
Assemblies 10 25 1,000
Certificates 25 2 1,000
Batch Configs 5 1 50
Price/Hour ? US$0.63 US$2.08
15

16. Other Azure Mapping Techniques
•Use a Logic App compose action.
•Use APIM transformation policy.
•Use an Azure Function + Custom C#.
• Liquid Templates
• XSLT Maps
• Other Mapping Frameworks
“I don’t want to pay for an Integration Account”
9/1/2020
16

17. APIM transformation policy

18. XSLT Maps with Azure Functions
https://social.technet.microsoft.com/wiki/contents/articles
/40231.biztalk-maps-migrating-to-azure-logic-apps-
shortcomings-solutions-part-2.aspx
9/1/2020
18

20. XSLT Maps with Azure Functions
20

21. Azure Functions with Liquid Maps
https://github.com/olafloogman/functions-dotnet-
liquidtransform
9/1/2020
21

22. Conclusions
1. Using BizTalk Maps makes migration quicker.
2. Using Liquid Templates is hard for complex maps.
3. Integration Accounts are expensive.
4. Other custom solutions are not very well supported.
“We need a consistent tool to map messages in Azure.”
You can migrate BizTalk maps to Azure