::This is an interesting direction from Microsoft, and I think the key for organizations is not to anchor planning to a specific future feature set.
In asset-heavy and rental-driven businesses, ERP challenges are rarely caused by missing functionality alone. They usually come from fragmented processes. Contracts living in one place, assets tracked in another, maintenance managed separately, and finance trying to reconcile everything at the end of the month.
With Dynamics 365 evolving toward a more connected and intelligent platform, the real question becomes.<br data-start=”1028″ data-end=”1031″> Are current processes ready to be connected?
A few practical thoughts based on what Iāve seen:
<ul data-start=”1128″ data-end=”1896″>
Organizations should focus less on <em data-start=”1165″ data-end=”1171″>when rental capabilities arrive and more on whether their asset lifecycle, billing logic, and operational ownership are clearly defined today.
Future capabilities will amplify what already exists. Clean asset data, consistent contract structures, and disciplined process ownership will benefit far more than waiting for new modules.
For project-based and rental-heavy scenarios, itās worth designing ERP with the assumption that rental, projects, finance, and service will increasingly overlap, not remain separate tracks.
Keeping implementations close to standard now is a strategic advantage. It gives room to adopt new functionality later without being locked into heavy custom logic that becomes technical debt.
From a long-term planning perspective, Iād treat Microsoftās roadmap as an opportunity to simplify and align processes now, so future intelligent features feel like natural extensions rather than disruptive changes.
Curious how others are approaching this. Especially those managing assets across multiple entities or long-term project lifecycles.