Forced update faliures

(0) Share

Report

Posted on by MRasheed

If a client can't take major/minor upgrade for a few months (possibly due to resource constraints during peak trading periods) and MS automatically apply a major or minor upgrade to a production environment... if any bugs/issues are introduced (due to the upgrade), who is responsible for potential loss of revenue/trading and who is responsible for fixing the bug.. is it MS, the client or the partner?

Categories:

Continuous Updates

Implementation Lifecycle

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Martin Walker on at

Like (0)

Report

RE: Forced update faliures

We are working hard to avoid breaking changes or regressions. But given the large number of permutations of Microsoft code, ISV code, client customizations, configuration choices and data patterns, some risk remains. This is why we strongly recommend a reasonable degree of regression testing, and provide tooling to make it easier to perform. If the client has been notified of a forthcoming update per the policy, and they choose not to test at all, then they are assuming the risk that an issue will affect them. If on the other hand they test, and find an issue, they can report the issue and request that the update not be applied to the production environment. Once the issue has been fixed, the update cycle resumes as normal.

Was this reply helpful? Yes No