Episode Details

What if you could hand off invoice approvals in Dynamics 365 without lifting a finger—and know your leads and cases are always routed to the right team? This isn’t wishful thinking—it’s what you’ll learn to automate today, using Power Automate and Copilot. Let’s break down the system holding your business back, and see how a few smart triggers can connect your D365 modules, save hours, and finally let your team focus on the work that matters. Ready to rethink the way your workflows actually work?Why D365 Automation Still Feels DisconnectedIf you’ve ever built a workflow in D365 and wondered why things still slip through the cracks, you’re not alone. Most organizations use Power Automate to handle one process at a time—move a lead, assign a case, send out an approval—but those quick fixes start to pile up. You end up with a patchwork of rules, each living in its own silo. The result? Processes that technically “work,” but add friction of their own. The reality is, these isolated automations are like putting band-aids on plumbing leaks—you’re not solving the deeper issue, just shuffling work around and hoping it holds.Let’s talk about where these silos show up. You automate the lead assignment. The lead goes to the right rep, but now the sales ops team has to manually update the case status, since no trigger covers that handoff. Meanwhile, your finance team approves an invoice and assumes the system will handle the rest. In practice, payment reminders and updated payment statuses often lag behind—because the automation ends as soon as one step is complete. That’s time lost and opportunities missed, buried under all those “just one more” manual steps that keep people from focusing on their real jobs. If you picture your D365 environment as a set of islands, each automation lives on its own, with very few bridges between them.Now here’s the strange part—D365 was designed to connect your business, not keep it split apart. But most automations treat each module as a separate world. Why? Some of it is technical, but more often it’s about how teams set up their flows. Instead of seeing the system as a whole, they carve out workflows for just one business group or department. For example, cases get routed in Customer Service, but there’s no automatic sync with Sales if that customer suddenly changes status. Or a Payment Approved trigger in Finance doesn’t speak to the project ops team, leaving them guessing if they can start work. It’s like running a relay race where each runner hands off the baton—except here, nobody actually runs to meet you, so you have to walk the baton over yourself every time.If this sounds familiar, you’re in good company. According to recent user research, more than 60 percent of D365 users say their workflow automations don’t really help cut down manual tracking between business roles. It’s a bit like ordering same-day delivery, only to find out every item in your order is shipped separately, days apart—it was all supposed to arrive together, but instead, it makes more work for everyone. These gaps may not sound dramatic, but they stack up. Reminders to the finance team get lost. A customer case sits idle because sales never sees that the deal was approved. Maybe an invoice sits in limbo, waiting for a team that never even knew it was ready.The friction becomes even clearer when you look at the transfer points. Take lead assignment again. Sure, you’ve got a trigger that routes leads from Marketing to Sales, based on region or product interest. But what about the next step? Does that same flow update account managers? Does it ping the support team if there’s an open case? Often, the answer is no—so someone, somewhere, has a notepad or an Excel file just to keep track of what’s still outstanding. The promise of automation was to end this, but most setups stop right before the finish line.And here’s the result: teams end up with workarounds. Maybe you use Power Automate to shoot off an email when an invoice is pa