%3CLINGO-SUB%20id%3D%22lingo-sub-1515688%22%20slang%3D%22en-US%22%3EImpact%20of%20Changes%20to%20Update%20Channels%20for%20Microsoft%20365%20Apps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1515688%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20previously%20announced%2C%20Microsoft%20recently%20made%20changes%20to%20the%20update%20channels%20for%20Microsoft%20365%20Apps.%20For%20the%20official%20announcement%20of%20these%20changes%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Foffice-365-blog%2Fa-new-wave-of-innovation-to-help-it-modernize-servicing-of%2Fba-p%2F1380733%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eread%20this%20blog%20post%3C%2FA%3E.%20For%20Microsoft%20Endpoint%20Configuration%20Manager%20admins%20that%20manage%20Microsoft%20365%20Apps%20updates%2C%20actions%20may%20be%20required%20depending%20on%20your%20environment.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUpdate%20packages%20in%20the%20Microsoft%20Update%20Catalog%20began%20using%20the%20new%20product%20name%20starting%20with%20releases%20on%20June%2018%2C%202020.%20If%20you%20use%20an%20automatic%20deployment%20rule%20(ADR)%20to%20deploy%20updates%20using%20Configuration%20Manager%2C%20and%20you%20rely%20on%20the%20%22Title%22%20property%2C%20you%20will%20need%20to%20make%20changes%20to%20your%20ADR.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20example%2C%20the%20title%20of%20an%20update%20package%20released%20prior%20to%20June%209%3CSUP%3Eth%3C%2FSUP%3E%2C%202020%20looks%20something%20like%20the%20following%20example%3A%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3EOffice%20365%20Client%20Update%20-%20Semi-annual%20Channel%20Version%201908%20for%20x64%20based%20Edition%20(Build%2011929.20708)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20update%20packages%20released%20on%20and%20after%20June%2018%2C%202020%2C%20the%20title%20of%20the%20update%20package%20will%20look%20something%20like%20the%20following%20example%3A%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3EMicrosoft%20365%20Apps%20Update%20-%20Semi-Annual%20Enterprise%20Channel%20Version%201908%20for%20x64%20based%20Edition%20(Build%2011929.50000)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENOTE%3A%20Microsoft%20365%20Apps%20updates%20released%20on%20the%20regular%20June%20%E2%80%9Cpatch%20Tuesday%E2%80%9D%20on%20the%209%3CSUP%3Eth%3C%2FSUP%3E%20were%20replaced%20(and%20expired)%20by%20rebranded%20updates%20released%20on%20June%2018%3CSUP%3Eth%3C%2FSUP%3E.%20If%20you%20have%20synced%20Microsoft%20365%20Apps%20updates%20since%20June%2018%3CSUP%3Eth%20%3C%2FSUP%3Eand%20have%20not%20fully%20deployed%20the%20updates%20released%20on%20the%209%3CSUP%3Eth%3C%2FSUP%3E%2C%20actions%20may%20be%20required.%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20use%20an%20ADR%20that%20relies%20on%20the%20%E2%80%9CTitle%E2%80%9D%20property%2C%20you%E2%80%99ll%20need%20to%20make%20changes%20as%20noted%20above%20to%20pick%20up%20the%20latest%20updates%20released.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20manually%20deployed%20the%20updates%20released%20on%20the%209%3CSUP%3Eth%3C%2FSUP%3E%2C%20which%20are%20now%20expired%2C%20you%20will%20need%20to%20select%20the%20latest%20updates%20to%20continue%20your%20deployments.%3C%2FLI%3E%0A%3CLI%3ENo%20action%20is%20required%20if%20your%20ADR%20does%20not%20rely%20on%20the%20%E2%80%9CTitle%E2%80%9D%20property.%3C%2FLI%3E%0A%3CLI%3EMicrosoft%20365%20Apps%20updates%20released%20on%20July%20%E2%80%9Cpatch%20Tuesday%E2%80%9D%20on%20the%2014%3CSUP%3Eth%3C%2FSUP%3E%20will%20of%20course%20be%20published%20using%20the%20new%20channel%20and%20product%20names.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EAdditional%20Resources%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E-ERR%3AREF-NOT-FOUND-A%20new%20wave%20of%20innovation%20to%20help%20IT%20modernize%20servicing%20of%20Microsoft%20365%20Apps%20for%20enterprise%3C%2FP%3E%0A%3CP%3E-ERR%3AREF-NOT-FOUND-Overview%20of%20update%20channels%20for%20Microsoft%20365%20Apps%3C%2FP%3E%0A%3CP%3E-ERR%3AREF-NOT-FOUND-Changes%20to%20update%20channels%20for%20Microsoft%20365%20Apps%3C%2FP%3E%0A%3CP%3E-ERR%3AREF-NOT-FOUND-Manage%20updates%20to%20Microsoft%20365%20Apps%20with%20Microsoft%20Endpoint%20Configuration%20Manager%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1515688%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20previously%20announced%2C%20Microsoft%20recently%20made%20changes%20to%20the%20update%20channels%20for%20Microsoft%20365%20Apps.%20For%20Microsoft%20Endpoint%20Configuration%20Manager%20admins%20that%20manage%20Microsoft%20365%20Apps%20updates%2C%20actions%20may%20be%20required%20depending%20on%20your%20environment.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1515688%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EO365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESoftware%20Update%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUnified%20Endpoint%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1516082%22%20slang%3D%22en-US%22%3ERe%3A%20Impact%20of%20Changes%20to%20Update%20Channels%20for%20Microsoft%20365%20Apps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1516082%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8458%22%20target%3D%22_blank%22%3E%40Yvette%20O'Meally%3C%2FA%3E%26nbsp%3Bfirst%20it%20looked%20like%20there%20are%20no%20major%20impacts.%20I%20declined%20that%20from%20the%20beginning%20as%20Office%20365%20MCSA.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESee%20also%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Foffice-365-blog%2Fa-new-wave-of-innovation-to-help-it-modernize-servicing-of%2Fbc-p%2F1476022%2Fhighlight%2Ftrue%23M2338%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Foffice-365-blog%2Fa-new-wave-of-innovation-to-help-it-modernize-servicing-of%2Fbc-p%2F1476022%2Fhighlight%2Ftrue%23M2338%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1516088%22%20slang%3D%22en-US%22%3ERe%3A%20Impact%20of%20Changes%20to%20Update%20Channels%20for%20Microsoft%20365%20Apps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1516088%22%20slang%3D%22en-US%22%3E%3CP%3EActions%20are%20also%20required%20for%20people%20not%20using%20MECM.%20There%20is%20more%20than%20channel%20renaming.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERenaming%20also%20affect%20scripts%20and%20other%20processes.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpdating%20Office%20ADMX%20at%20least%202%20times%20a%20years%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpdating%20ODT%20at%20least%20two%20times%20a%20year%20including%20checking%20their%20XML.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChecking%20their%20GPOs.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEverything%20without%20notice%2C%20outside%20blogs%20and%20social%20media.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20has%20to%20check%20for%20updates%20frequently%20and%20manually.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1525226%22%20slang%3D%22en-US%22%3ERe%3A%20Impact%20of%20Changes%20to%20Update%20Channels%20for%20Microsoft%20365%20Apps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1525226%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F289393%22%20target%3D%22_blank%22%3E%40K_Wester-Ebbinghaus%3C%2FA%3E%2C%20thanks%20for%20the%20feedback.%26nbsp%3B%26nbsp%3BI'd%20like%20to%20know%20if%20your%20points%20are%20specifically%20for%20this%20rename%20or%20more%20generally%20for%20notice%26nbsp%3Babout%20updates%20to%20the%20Group%20Policy%20files%20and%2For%20the%20Office%20Deployment%20Tool%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20M365%20Apps%20team%20has%20also%20provided%20these%20reference%20docs.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fdeployoffice%2Fname-change%23registry-key-values%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fdeployoffice%2Fname-change%23registry-key-values%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fdeployoffice%2Fname-change%23powershell-scripts%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fdeployoffice%2Fname-change%23powershell-scripts%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3EBest%20Regards%3C%2FP%3E%0A%3CP%3E-Yvette%20O'Meally%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

As previously announced, Microsoft recently made changes to the update channels for Microsoft 365 Apps. For the official announcement of these changes, read this blog post. For Microsoft Endpoint Configuration Manager admins that manage Microsoft 365 Apps updates, actions may be required depending on your environment.

 

Update packages in the Microsoft Update Catalog began using the new product name starting with releases on June 18, 2020. If you use an automatic deployment rule (ADR) to deploy updates using Configuration Manager, and you rely on the "Title" property, you will need to make changes to your ADR.

 

For example, the title of an update package released prior to June 9th, 2020 looks something like the following example:

Office 365 Client Update - Semi-annual Channel Version 1908 for x64 based Edition (Build 11929.20708)

 

For update packages released on and after June 18, 2020, the title of the update package will look something like the following example:

Microsoft 365 Apps Update - Semi-Annual Enterprise Channel Version 1908 for x64 based Edition (Build 11929.50000)

 

NOTE: Microsoft 365 Apps updates released on the regular June “patch Tuesday” on the 9th were replaced (and expired) by rebranded updates released on June 18th. If you have synced Microsoft 365 Apps updates since June 18th and have not fully deployed the updates released on the 9th, actions may be required.

 

  • If you use an ADR that relies on the “Title” property, you’ll need to make changes as noted above to pick up the latest updates released.
  • If you manually deployed the updates released on the 9th, which are now expired, you will need to select the latest updates to continue your deployments.
  • No action is required if your ADR does not rely on the “Title” property.
  • Microsoft 365 Apps updates released on July “patch Tuesday” on the 14th will of course be published using the new channel and product names.

 

Additional Resources:

A new wave of innovation to help IT modernize servicing of Microsoft 365 Apps for enterprise

Overview of update channels for Microsoft 365 Apps

Changes to update channels for Microsoft 365 Apps

Manage updates to Microsoft 365 Apps with Microsoft Endpoint Configuration Manager

 

3 Comments

@Yvette O'Meally first it looked like there are no major impacts. I declined that from the beginning as Office 365 MCSA. 

 

See also 

https://techcommunity.microsoft.com/t5/office-365-blog/a-new-wave-of-innovation-to-help-it-modernize...

Actions are also required for people not using MECM. There is more than channel renaming. 

 

Renaming also affect scripts and other processes. 

 

Updating Office ADMX at least 2 times a years,

 

Updating ODT at least two times a year including checking their XML.

 

Checking their GPOs. 

 

Everything without notice, outside blogs and social media. 

 

One has to check for updates frequently and manually. 

Microsoft

Hello @K_Wester-Ebbinghaus, thanks for the feedback.  I'd like to know if your points are specifically for this rename or more generally for notice about updates to the Group Policy files and/or the Office Deployment Tool?

 

The M365 Apps team has also provided these reference docs.
https://docs.microsoft.com/deployoffice/name-change#registry-key-values 
https://docs.microsoft.com/deployoffice/name-change#powershell-scripts 

Best Regards

-Yvette O'Meally