What happens when the people who build D365 Field Service sit down with the people who implement it every day? You get this episode.

Jason Cohen has been on the Microsoft Field Service product team for nearly eight years — going all the way back to the FieldOne acquisition — and he joins Scott and Will for one of the most candid conversations the Service X Factor has had yet.

The big headline: Field Service and Project Operations are now deeply integrated, and Jason believes this changes the implementation equation permanently. The old sales-order-based model worked for some scenarios, but it left internal work, milestone-based projects, and mixed billable/non-billable jobs out in the cold. The new FSPO integration — built on dual-write — closes that gap and gives implementers the flexibility to extend, map, and connect across the full Microsoft stack, with or without Finance & Supply Chain.

Jason and the crew also dig into:

• Scheduling improvements — the ”paper cuts” initiative delivering real dispatcher UX wins, performance gains, and smarter defaults
• Mobile — where the focus is going (bigger touch targets, faster loads, more reliable offline sync)
• Licensing — persona-based and simpler than you might think
• The overlapping bookings saga — why one of the most-requested ”features” would actually break everything
• Change management vs. customization — and why the product almost never fails when you implement it right

Plus the obligatory shoutouts to Ben Vollmer, Dan Gittler, and the legend himself — Shawn Tabor — and a reminder that Field Service has always been better when the community and the product team are talking to each other.

If you're a D365 partner, implementer, or architect, this one's worth your full attention. Subscribe, share with your team, and tell us in the comments: what's the one Field Service improvement that would change your life next quarter?

Send a text