Recap of Day 3: Integrate 2022

INTEGRATE 2022 brings together experts in the Microsoft Integration Space for a Hybrid event in London. These are the highlights from day 3, from the perspective of the Codit staff following the event.

Azure is Consistent in Being Inconsistent

Azure is always in evolution, new features are being added, security is being updated and old components are being deprecated. You don’t have to wait on release cycles for new functionality as they automatically become available in your region.

You should regularly check if the components you’re using aren’t being deprecated. The Azure Deprecation Notices website can be a useful tool for that.

Use Managed Identity Wherever Possible

Managed identities create an automatically managed identity within Azure Active Directory (Azure AD) for resources to use when connecting to other resources that support AD authentication.

Your application itself won’t have to manage credentials and passwords any longer, and even better if it’s free, simple and easy to get started.

Make Sure to Backup Your API Management Instances

Azure API Management has a very important place in most integration architectures, losing your API Management instance for whatever can be disastrous and is not something you can easily recover from.

Therefore, creating a (nightly) backup of your API Management instance is an important step within your disaster recovery procedure, check out these scripts to backup and restore your Azure API Management instance:

There are Six Different Ways of Mapping Your Data, Choose the Right One Based on Your Requirements

There are 6 different ways to map data with the Azure Integration Services:

  1. Migrate BizTalk maps to Azure
  2. Write your own XSLT
  3. Use Liquid
  4. Use Azure Functions (mappings can be done in C#, XSLT, Liquid)
  5. Use APIM
  6. Azure Data Factory

They all have their pros and cons. For example, Liquid is very easy to use with JSON and migrating your BizTalk maps to Azure allows you to re-use earlier mappings.

Keep your requirements and team capabilities in mind when choosing which option to use. For example, if your team has limited XSLT experience, migrating your BizTalk maps might be a good option. On the other hand, if you are working mainly with JSON there is a good chance Liquid is the way to go.

The Only Wrong Naming Standard is Not Having a Naming Standard

Naming standards are important to keep your environments clean, understandable and deployments predictable. Make sure to define your naming standards at the start of your project and define a peer-reviewing process, to ensure your naming standards are being used correctly.

Thanks for attending Integrate 2022! We hope you enjoyed our takeaways.

Thanks, we've sent the link to your inbox

Invalid email address


Your download should start shortly!

Stay in Touch - Subscribe to Our Newsletter

Keep up to date with industry trends, events and the latest customer stories

Invalid email address


Great you’re on the list!