Microsoft Dynamics 365 for Finance and Operations start One Version era

Microsoft Dynamics 365 for finance and operations has entered the version age, in which customers say farewell to traditional ERP updates and apply a continuous and compulsory series of monthly.

Microsoft has ruled in favor of the transition and Expects to convince present Finance and Operations (D365FO) customers that the new strategy will benefit them in the long term and that upgrading Dynamics AX customers won't benefit them to come up. A new update project should be carried out in the future. This is in line with Microsoft Office 365's upgrade philosophy.

The transition occurs at a time when D365FO at the ERP product family is growing and adapting in a faster speed than ever.

Client mix

·        30% business and 70% middle class.

·        77% are new implementations versus 23% updates.

·        Production environments that are D365FO are used in by functional

·        Finance: 98 percent

·        Supply chain management: 82 percent SCM

·        Human capital management: 81%

·        Warehouse management: 63 percent

·        Project bookkeeping: 16%

Another reason is that the improvement of the update and Migration tools and the end of the lifespan of the versions of AX.

The present model provides that clients apply an Update at least every three months. This means that two monthly upgrades can be ignored by a client, but need to then install the subsequent one. For each update, the customer can define the week, the day (for many Saturdays or Sundays, but a few businesses such as retail opt for midweek) and the moment.

Another step in supporting new upgrades is the Version validation program, which introduces projects into an environment in. The evaluation results are confirmed by Microsoft and any defect is reported to the customer. This program demands data and code to be shared with a Microsoft team.

Customer Accountability and reply

In the past, users were reluctant to perform One Version forces them to do precisely that, although updates when they knew a system worked nicely. In theory, this risk should be mitigated by more frequent updates by two variables. These teams should identify and report, and first, these upgrades will be received by first users before the majority of customers problems in least a month before more conservative customers. Secondly, spouses will see the upgrade that is same for all customers, which means that they ought to be able to forecast the most frequent problems for all of their customers that are D365FO in a particular quarter or month.

Users did not raise concerns or Questions in response to his advice, which has helped Microsoft move faster in this direction. Company leaders have adopted this SaaS model and determine long-term value.

Microsoft is also exploring customer Has hired an independent consultant to inform and needs Microsoft of what Customers need in various scenarios and industries (for instance, FDA-regulated manufacturers, public sector regulations, ITAR compliance). Microsoft has received comments from the community that originally Raised concerns and is currently adjusting these fundamentals.