Dynamics 365 Customer Insights - Journeys (the marketing app that used to be Dynamics 365 Marketing, for those keeping score at home) is an interesting platform with a lot of potential. I'd also say it isn't complete. We talk internally about whether it's really a product or a platform, and it's a lot more like SharePoint. You can do some stuff with it out of the box, but the real value is in configuring it, and you configure it a lot.
Why we run it ourselves
The number one reason we picked Journeys for TruNova is that we want to be customer zero. We take that seriously: if we're going to help clients with it, we should be using it first. As a Microsoft partner our license comes with our partner benefits, so we're not paying what you'd pay. Even so, it's not really designed for a small company. We're 26 people.
We've been on it for about two months, using it for client newsletters, partner newsletters and some cold outreach, so a lot of different jobs for different parts of the business. Customer zero mostly means we get to find the potholes before our clients do. With our own car. But it's better to have that happen to us first, so we can help our clients avoid those challenges.
The problem
It really doesn't do much out of the box, and there are no easy buttons. Before a typical marketing team can do the basics, somebody has to work through a list like this:
- Authenticate your own sending domain, which means adding a TXT record and several CNAME records in DNS, because the default domain Microsoft provides is only meant for testing
- Set up compliance profiles, purposes and topics, and decide whether the default consent models fit your business, because Microsoft is clear that those defaults aren't legal recommendations
- Build your own forms, the preference center and email templates so they look like your brand
- Get a developer to wire custom triggers into your website or app
Events are the same story. If you want to run events it takes a lot of configuration, forms and changes, and the Teams webinar integration is a one-way sync, so you pretty much have to pick whether Teams or Customer Insights runs registration. It sort of integrates, but it feels bolted on and clunky, and I was not impressed.
The licensing math
The base license is $1,700 a month ($1,000 if you already own qualifying Dynamics 365 licenses). I had $1,500 in my head, so I was being generous. Either way it's way more than getting started with something like HubSpot. It includes 10,000 "interacted people," and once you send somebody a single email they count against that 10,000 until they've gone 12 months without another one. So you send one newsletter, somebody unsubscribes the same day, and they're still taking up a slot for the next year. Cold outreach is worse, because somebody can ignore your email completely and still hold a slot for a year.
We're two months in and we're already at 10,000. If you're not extremely careful, you get there way faster than you'd expect, and the rules around it are not super customer-friendly. It really punishes you for doing any kind of non-transactional email.
The reporting
The reporting is embarrassingly bad. The built-in analytics are pretty limited, and we couldn't get to any of the statistics through the API, so the real answer ends up being the data lake and Power BI, without much documentation to get you there. As a small company, building a data lake to find out whether a newsletter worked doesn't totally make sense. For a marketing tool, not being able to easily see what's working and what's not is easily the worst part.
It doesn't feel like one application
Journeys sits on the same Dynamics data as Sales, and technically it integrates, but it really doesn't. There's not clear visibility between the two. This is common with Microsoft, they sort of integrate. It's the same with Teams: they sync and so on, but they're not fully integrated.
Just because it's two different applications doesn't mean it shouldn't feel like one. Journeys has segments, so why doesn't Sales have segments? The two should have the same kind of setup and configuration and be connected in a way that makes sense, and right now they feel like two separate applications that do quite a bit different and sort of integrate.
Who it's for
For a smaller company I would absolutely not recommend it. It's $1,700 a month just to start, and there are definitely cheaper options. We get it through our partner benefits and it's still a lot of platform for our size.
For a bigger company that's already on Dynamics, it can absolutely get there, but be prepared to spend some real money configuring it so it works great for your business. If you go for it, plan the setup like a project: domains, consent and branding first, a few starter journeys and templates the team can copy, a plan for who gets emailed so you don't burn through your 10,000, and enough training that marketing isn't opening a ticket every time they want to change a footer.
The ask
Microsoft's own release plans talk about teams launching campaigns without deep technical expertise, and I'd love for that to be true. Keep the power, but make it something a marketing team can pick up and use in week one, and make it a little more customer-friendly:
- Easier, quicker setup so you get to something useful fast
- Real starter templates for forms and emails that actually look nice, not just empty samples
- Email analytics and reporting that are easier to use, and available through the API
- Events and Teams fully integrated, working both ways and working well
- Journeys and Sales that feel like one application, with segments in both
- Licensing that doesn't punish you for sending a newsletter
It has a lot of potential, and most of the engineering is there.
Signed, somebody who'd love to stop calling week one "phase zero."



