Forum Discussion
Prevent issues caused by updates
- I agree that this is challenging - and just did a blog post about the various places that you need to pay attention to and approach to consider in order to solve this challenge. Here is a link to the post: http://www.networkworld.com/article/3112340/software/it-takes-a-village-change-management-with-office-365.html.
Thank you for you reply.
Perhaps it makes no sense but I was asking if it would be possible to somehow configure the tenant to only receive updates, for example, once a month. Kind of the same way it is possible to https://mcpmag.com/articles/2014/09/11/office-365-update-tips-for-it.aspx.
That would allow me to know when the tenant is updated and antecipate any issues (ex, by having a first release tenant, as you suggest, or by having a first release user on that tenant and fix any issues before the tenant gets updated).
Given the worldwide rollout of features and the usual "rolling" schedule, I don't think it's feasible to have updates applied to your tenant on any kind of schedule, like "first of the month, give me everything that's available." If that were available, I would sign up my tenant!
One other frustration for me is that the tenant-level controls (on/off for your tenant) aren't available until the same time that the feature is rolled out to your tenant. Someone pleae correct me if I'm wrong.
- There is no way to schedule your updates today. But as you have seen, some new features (e.g. modern document libraries) can be turned off for your tenant or individual library. This is one of the pros/cons of software as a service (depending on you you look at it). You don't have to install updates but you have less control over the timing and frequency of when they happen. I would love to see more specificity about when an update will hit a specific tenant - because with more clarity about timing, you have a better opportunity to prepare and prioritize you testing and communications (and I'm hoping this will happen).
