D365 Finance & Operations and Dynamics AX Forum

I appreciate that several of you are of the same opinion that I am on this subject. I do not believe that Microsoft understands the burden that the automatic quality updates have on their customers. We simply cannot trust that nothing will break. One week to test is not enough time, especially if we have no control over the timing of it and that is only if we accept the fact that this burden of testing and associated cost burden is acceptable for Microsoft to push our way. We accepted the Run One program and I do think it has been beneficial but this next step is too much and is inching closer to forcing the full version updates. I am certain that is where Microsoft is ultimately planning to go. We all need to push hard on our points of contact at Microsoft to make sure they understand our strong feelings on this matter. The worst thing that can happen is they proceed as planned. If we do not voice our concerns, we will be stuck with this.

Based on some posts, I think there is some confusion about exactly what I am referring to with this thread. Below is a link to a good summary of the changes coming from proactive quality updates (thank you Andrew Russell for adding this to the thread. I am not fully understanding of the timing of these quality update trains based upon this article but I am working with my partner to digest this information.

Proactive quality updates - Finance & Operations | Dynamics 365

Thanks and have a great weekend!

Karl Arensdorf

Corporate Controller

Mansfield Energy

Office: 678-207-2575

1025 Airport Pkwy, Gainesville, GA 30501

Karl

We just had a lengthy Teams meeting with our Microsoft rep. on this very issue. When we apply D365 updates we first apply to one of our sandbox env. and perform a month of regression testing. We have our own in-house customizations to test and, we have to reach out five ISVs to retrieve the latest/appropriate updated modules from them to include in our env. to test. To reduce the impact this has on us, we only apply every 3^rd D365 version update, skipping two completely, resulting in two (or occasionally 3) updates a year. With this new PQU process Microsoft is forcing on its customers, we now have to do further rounds of testing immediately after we do a version update (since we will be on the current version again and subject to these PQUs for about a month until the version drops out of scope for PQUs). We showed the Microsoft reps just how much of an impact this is going to have on us, how Microsoft clearly didn't bother to consult any of its customers over this decision that is being forced on us, and how completely unreasonable it is. It didn't appear to us they were the slightest bit aware of the impact this was going to have, and they are taking this back to their team. I don't have much faith they will actually do anything about it though and we may be stuck dealing with this going forward. I can say we are not impressed with this new process.

 
Tim