Stewart Rutledge2025-05-22

Using Azure for M3 Integrations

After a few great days at WTC, it’s clear that integrations remain a major question mark for many companies, especially as they move to the cloud.

In the spirit of our recent H5 app posts, I thought I’d share some thoughts on integrations, along with a practical example of how we approach them at Beredo.

M3 comes with strong built-in tools for integrations, IEC/MEC, ION, and others. These are solid and cover many standard scenarios. But once things get more complex, especially when connecting to third-party systems, these tools can start to show their limits.

And while many customers want to explore other options, we’ve noticed that stepping outside the default toolset is easier said than done. Either they don’t have much experience with alternative integration platforms, or the tools they do have come with the same kinds of limitations.

So, we’re going to walk through an integration, step-by-step, over a few posts, to show how we approach this in real-world projects.

A few guiding principles:

1. We’re building this in Azure. Not just because it’s powerful, but because most customers already have access to it, getting started is simple.

2. We’re using BODs wherever we can. BODs aren’t always perfect, but they offer out-of-the-box events and messages that cover many use cases. That means less complexity on the M3/ION side and faster delivery.

Stay tuned! We’ll start with a basic Azure setup for an integrations platform, and how to start moving data from M3 into Azure.

As always, reach out if you’re curious or want to talk about your integration challenges:

hello@beredo.net