1
We normally opt out of all production service updates via the LCS screen. This is because we have strict internal testing that occurs for all packages that run against our Production environment. The testing window for these are 2 weeks long. The reason we are so careful with updating Production is during the early days of D365, there was a major bug that came with an update that stopped our ability to use OData until MSFT fixed it. As a result, we put in careful business controls to protect ourselves. One of these is we will also remain at least 1 version behind the most recent version. We do NOT want to be the users to discover the bugs in production and have it interfere with our business.
The issue occurred over the weekend where we had errors in OData sales orders slowly start occurring. It started getting worse this morning so we started looking into the issue. It looks like our production environment was auto updated to 10.0.12 without our acknowledgement. I looked further and it looks like the opting out of updates screen in LCS only allows opting out of 3 updates at a time. I’m not sure when that change occurred as we’ve been opting out of updates since the initial release of ONE version and I don’t recall having to go in every 3 months to opt out of additional updates.
The biggest issue for us though is the production upgrade went through even though I never had to click “Yes” to anything. Especially for these auto-updates, it should still enforce an Environment Manager or higher user to require clicking a final “Yes” before proceeding with the upgrade. Otherwise, it’s far too easy for a production upgrade to slip through the cracks and result in negative consequences for our business. If we compare the auto-update process to a manual update and you can see what I mean. If I wanted to manually update my production environment, there are multiple forms/screens I have to visit and each time I have to confirm that yes, I am purposefully aware I am updating a production environment. On the other hand, these auto-updates send a single LCS email notification about some planned maintenance and that’s it. There’s no confirmation I have to give and there’s no multiple step verification to ensure I want to take this action.
On top of that, I believe someone on our team actually clicked cancel on that LCS email notification email and it still proceeded with the update anyway. I hope you can understand our frustrations with how laissez faire the auto updates are treated and help introduce some better controls around the process so we don’t get surprised like this in the future. In the meantime, I’ve added internal calendar reminders so I can go into LCS every 3 months and opt out of additional updates.
The issue occurred over the weekend where we had errors in OData sales orders slowly start occurring. It started getting worse this morning so we started looking into the issue. It looks like our production environment was auto updated to 10.0.12 without our acknowledgement. I looked further and it looks like the opting out of updates screen in LCS only allows opting out of 3 updates at a time. I’m not sure when that change occurred as we’ve been opting out of updates since the initial release of ONE version and I don’t recall having to go in every 3 months to opt out of additional updates.
The biggest issue for us though is the production upgrade went through even though I never had to click “Yes” to anything. Especially for these auto-updates, it should still enforce an Environment Manager or higher user to require clicking a final “Yes” before proceeding with the upgrade. Otherwise, it’s far too easy for a production upgrade to slip through the cracks and result in negative consequences for our business. If we compare the auto-update process to a manual update and you can see what I mean. If I wanted to manually update my production environment, there are multiple forms/screens I have to visit and each time I have to confirm that yes, I am purposefully aware I am updating a production environment. On the other hand, these auto-updates send a single LCS email notification about some planned maintenance and that’s it. There’s no confirmation I have to give and there’s no multiple step verification to ensure I want to take this action.
On top of that, I believe someone on our team actually clicked cancel on that LCS email notification email and it still proceeded with the update anyway. I hope you can understand our frustrations with how laissez faire the auto updates are treated and help introduce some better controls around the process so we don’t get surprised like this in the future. In the meantime, I’ve added internal calendar reminders so I can go into LCS every 3 months and opt out of additional updates.
STATUS DETAILS
Needs Votes