New Microsoft 365 apps update channel names, new IT Pro guidance and a new channel!

ChristianBergstrom - yeah, we should potentially word some of that differently in the article. We have in the past, although it is extremely rare, made a bug fix across all channels in a given month (out of band). We are very cautious about making changes to Semi-Annual Enterprise after it is published as we want to make as few changes to that release as possible. We will make security changes monthly, as that is a necessary code change risk for the greater good. Otherwise, we try to leave that build alone and recommend that channel for the mission critical devices in an organization that are running complex macros and home grown add-ins that need full pass testing. For the rest of the organization, we recommend the Monthly Enterprise Channel so they can get both fixes, and as you correctly called out, features sooner.  

Firoz1723 Unfortunately, that can happen. If we are made aware of a bug after a certain cut off period, we don't have time to fix it and release it before we publish the next version of the Semi-Annual channel. So entire builds of Semi-Annual channel can have a bug in it. However, one thing to consider is that some of the issues aren't from Office itself. We have seen both Windows and Configuration Manager updates create issues for the Office client. It really comes down to when we are made aware of an issue and sometimes a bug is not discovered by us or our customers before the cut off for the next release of Semi-Annual and therefor we can't fix it in time. This is one of the biggest reasons I tell customers for the majority of your devices that are not running macros or doing key line of work processes, that they should use the Monthly Enterprise Channel. That way, when things are discovered, they get fixed and published to this channel much sooner then the Semi-Annual channel.