Ensure relieble Releases on Dynamics 365 FinOps

As Microsoft Dynamics 365 Finance & Operation Release 10.0.29 is General available all Dynamics 365 Finance & Operations customer can apply self-update for their environments from last week on and auto-updates will be scheduled to start from end of September.

I often see that customer don’t care about all the enhancements that are included in each release, and then I will be asked what I would recommend to enable in feature management workspace, and I tell them: “It’s up to you” and we start to discuss about the release process. Before we go to a generic task list it would make sense to have an alignment with process owner and key users what is a realistic period for the Team to apply Release updates. Typically it needs to be less than three month because of end of service is three month after GA date, customer often decide to use a two- or three-month cycle to keep the effort reasonable.

For every update we should do some validation steps to impove existing process, establish a Facilitation for the user and avoid unexpected process behavior and user experience.

As many features are added, defaulted and often set to mandatory we should be aware of opportunities and risks of every feature enhancement. And because of features often become mandatory it is more important to know how the business process and even the user experience will be affected.

So my recommendation for Product- and Process-Owner, key Users, SysAdmins and Project Manager is to follow this guideline (as a sample for Release 10.0.29):

Keep your eyes open is not enough, take all release documentation under observation which can be seen much earlier for all releases to prepare your Team and processes for upcoming changes. For better and sustainable business processes without undisered surprises.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.