D365 Finance & Operations and Dynamics AX Forum

 View Only
  • 1.  Forced Quality Updates

    SILVER CONTRIBUTOR
    Posted 19 days ago
    I am putting this out to the group to see what people think. I am very concerned about the fact the Microsoft is going to force us to take quality updates monthly once we migrate to version 10.0.30 and beyond. We do not take every upgrade because of the burden this would put on the users. Taking quality updates will still require testing so Microsoft is effectively forcing this burden of testing (and associated cost) on their customers.

    I am not convinced that Microsoft fully understands the impact this has on their customers. Am I alone? I think if enough customers push back, we may be able to get this put on hold.

    ------------------------------
    Karl Arensdorf
    Corporate Controller
    Mansfield Oil Company
    Gainesville GA
    ------------------------------


  • 2.  RE: Forced Quality Updates

    Posted 19 days ago
    Hi Karl - can you post link to your source?

    AFAIK there is the possibility to opt out automatic, but that you are only allowed to be n versions behind.

    https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/one-version
    Yes, customers can pause, delay, or opt out of an update via the update settings in Microsoft Dynamics Lifecycle Services (LCS) projects, provided that all their sandbox and production environments are no more than three versions behind the latest available update. Customers can choose to pause up to three consecutive updates.

    ------------------------------
    Andrew Russell
    Direct Wines
    Reading, UK
    ------------------------------



  • 3.  RE: Forced Quality Updates

    Posted 19 days ago
    Apologies - I posted too quickly. I guess you are referring to Proactive quality updates - Finance & Operations | Dynamics 365

    My understanding of this is that they are deemed so low risk/impact that they could not break customer customisation, and no specific customer testing is required.

    Agree that doesn't give a warm fuzzy feeling, we are in the fortunate position of getting to see how this plays out first before we will be live.

    ------------------------------
    Andrew Russell
    Direct Wines
    Reading, UK
    ------------------------------



  • 4.  RE: Forced Quality Updates

    SILVER CONTRIBUTOR
    Posted 18 days ago

    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

     

     

     

     

     




    CONFIDENTIAL
    The information contained in this electronic message is confidential and intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this electronic message is strictly prohibited. If you have received this electronic message in error, please notify me immediately at the above listed telephone number(s) and delete the original message.





  • 5.  RE: Forced Quality Updates

    Posted 19 days ago
    Edited by Tim Harpur 11 days ago

    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 3rd 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



  • 6.  RE: Forced Quality Updates

    Posted 18 days ago
    No, you are definitely not alone in being very concerned.  Like you, our company does not update every month.  We usually are upgrading every other month.  That is because our users go through a pretty rigorous testing cycle.  Unfortunately, we have found many issues in the past with new delivered code and were able to get these resolved or develop a work around before it was loaded into our production environment.  I fear with the forced updates, we will not get to test everything thoroughly before it is forced into production environment and we will find ourselves in a case where we can not process our GL close or run our necessary reports.  We do not have the manpower to test every month and we certainly can't do it in a week's time at the drop of a hat.  We've complained to Microsoft but that hasn't helped.  I hope others complain as well.

    ------------------------------
    Paula Buffa
    Controller
    XTRA Lease
    St. Louis MO
    ------------------------------



  • 7.  RE: Forced Quality Updates

    Posted 15 days ago
    Edited by Sabu Sentry 15 days ago
    Microsoft is really overdoing it with updates. Logically speaking, quality updates can't come out too often, as it takes time to work on quality. But more than that, I heard from https://www.d365experts.co.uk/software/microsoft-business-central/ that Microsoft has started to force Windows 10 version 1903 to be updated to more recent ones. And even if you turn off all auto-updates with the help of some kind of program, Microsoft still has all the possibilities online to influence your installed windows, up to collecting your mail and Wi-Fi passwords and analyzing your documents.


If you've found this thread useful, dive deeper into User Group community content by role