Name changes for Microsoft 365 Apps update channels

%3CLINGO-SUB%20id%3D%22lingo-sub-1455086%22%20slang%3D%22en-US%22%3EName%20changes%20for%20Microsoft%20365%20Apps%20update%20channels%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1455086%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Office%20Insiders%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELast%20month%20we%20announced%20that%20we%20were%20changing%20the%20names%20for%20the%20Windows%20update%20channels.%20Starting%20on%20June%209th%2C%20these%20name%20changes%20will%20be%20available%20broadly%20across%20documentation%2C%20product%20UI%2C%20deployment%20tools%2C%20etc.%20To%20learn%20more%20about%20these%20name%20changes%20and%20what%20to%20do%20if%20you're%20an%20admin%2C%20check%20out%20our%20%3CA%20href%3D%22https%3A%2F%2Fblog-insider.office.com%2F2020%2F06%2F09%2Fmicrosoft-365-apps-update-channels%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Elatest%20blog%20post%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECheers%2C%3C%2FP%3E%0A%3CP%3EEvan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1477208%22%20slang%3D%22en-US%22%3ERe%3A%20Name%20changes%20for%20Microsoft%20365%20Apps%20update%20channels%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1477208%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F478150%22%20target%3D%22_blank%22%3E%40Evan_Bolin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMS%20renamed%20the%20patches%20on%20the%209th%20June%20example.%26nbsp%3B%3CSPAN%3E%26nbsp%3BOffice%20365%20Client%20Update%20-%20Semi-annual%20Channel%20Version%201908%20for%20x64%20based%20Edition%20(11929.20838)%20to%26nbsp%3B%26nbsp%3BOffice%20365%20Client%20Update%20-%26nbsp%3B%26nbsp%3B-%20Semi-Annual%3CSTRONG%3E%20Enterprise%3C%2FSTRONG%3E%20Channel%20Version%201908%20for%20x64%20based%20Edition%20(11929.20838)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Ethen%20on%20the%2018th%20June%20you%20completed%20the%20named%20change%20from%26nbsp%3B%26nbsp%3B%3CEM%3EOffice%20365%20Client%20Update%3C%2FEM%3E%20-%26nbsp%3B%26nbsp%3B-%20Semi-Annual%20Enterprise%20Channel%20Version%201908%20for%20x64%20based%20Edition%20(11929.20838)%20to%26nbsp%3B%26nbsp%3B%3CSTRONG%3E%20Microsoft%20365%20Apps%20Update%3C%2FSTRONG%3E%20-%20Semi-Annual%20Enterprise%20Channel%20Version%201908%20for%20x64%20based%20Edition%20(11929.20838)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Ethis%20was%20part%20way%20through%20the%20month%2C%20but%20the%20same%20version%20number%20was%20used%2C%20This%20caused%20the%20current%20one%20with%20the%20same%20version%2C%20to%20expire%20and%20in%20turn%20deleted%20the%20patch%20from%20WSUS%2C%20and%20then%20SCCM.%26nbsp%3B%20This%20had%20the%20knock%20on%20effect%20of%20deleting%20our%20deployments%20for%20that%20patch%20version.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ENormally%20any%20incremental%20changes%20you%20would%20have%20added%20a%20new%20version%20number%20so%20it%20does%20not%20affect%20anything%2C%20Can%20you%20confirm%20this%20was%20just%20a%20name%20change%20and%20did%20not%20have%20any%20additional%20updates.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1484928%22%20slang%3D%22en-US%22%3ERe%3A%20Name%20changes%20for%20Microsoft%20365%20Apps%20update%20channels%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1484928%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20in%20the%20same%20situation%20here%20currently%20rolling%20out%20Windows%2010%20with%20version%201908%20O365%2C%20deployments%20for%20this%20have%20been%20removed.%20The%20name%20change%20to%26nbsp%3B%3CSPAN%3ESemi-Annual%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EEnterprise%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3BChannel%20Version%26nbsp%3B%20around%20patch%20Tuesday%20was%20difficult%20enough%20to%20pick%20up%2C%20we%20changed%20all%20our%20filters%20in%20SCCM%20to%20reflect%20the%20above%20change%20and%20now%20another%20one..%20Do%20you%20think%20you%20will%20settle%20on%20a%20name%20soon%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1493070%22%20slang%3D%22en-US%22%3ERe%3A%20Name%20changes%20for%20Microsoft%20365%20Apps%20update%20channels%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1493070%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F708424%22%20target%3D%22_blank%22%3E%40John_Osti%3C%2FA%3E%26nbsp%3BWe%20apologize%20for%20any%20inconvenience%20this%20change%20has%20created.%20At%20this%20time%2C%20we%20have%20no%20plans%20on%20changing%20the%20names%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Hello Office Insiders,

 

Last month we announced that we were changing the names for the Windows update channels. Starting on June 9th, these name changes will be available broadly across documentation, product UI, deployment tools, etc. To learn more about these name changes and what to do if you're an admin, check out our latest blog post.

 

Cheers,

Evan

3 Replies

@Evan_Bolin 

MS renamed the patches on the 9th June example.  Office 365 Client Update - Semi-annual Channel Version 1908 for x64 based Edition (11929.20838) to  Office 365 Client Update -  - Semi-Annual Enterprise Channel Version 1908 for x64 based Edition (11929.20838)

 

 

then on the 18th June you completed the named change from  Office 365 Client Update -  - Semi-Annual Enterprise Channel Version 1908 for x64 based Edition (11929.20838) to   Microsoft 365 Apps Update - Semi-Annual Enterprise Channel Version 1908 for x64 based Edition (11929.20838)

 

this was part way through the month, but the same version number was used, This caused the current one with the same version, to expire and in turn deleted the patch from WSUS, and then SCCM.  This had the knock on effect of deleting our deployments for that patch version. 

Normally any incremental changes you would have added a new version number so it does not affect anything, Can you confirm this was just a name change and did not have any additional updates. 

We are in the same situation here currently rolling out Windows 10 with version 1908 O365, deployments for this have been removed. The name change to Semi-Annual Enterprise Channel Version  around patch Tuesday was difficult enough to pick up, we changed all our filters in SCCM to reflect the above change and now another one.. Do you think you will settle on a name soon?

@John_Osti We apologize for any inconvenience this change has created. At this time, we have no plans on changing the names again.