Download location change for Microsoft 365 Apps readiness file

Published Feb 02 2021 05:54 PM 4,817 Views
Microsoft

We’re changing the location of the readiness file that is downloaded by the Microsoft 365 Apps Upgrade Readiness dashboard in Microsoft Endpoint Configuration Manager (version 1906 or later). This dashboard helps you determine which devices are ready to update to Microsoft 365 Apps. 

 

Note: If you don’t use the Microsoft 365 Apps Upgrade Readiness dashboard, you can ignore this information. 

 

Old location: https://contentstorage.osi.office.net/sccmreadinessppe/sot_sccm_addinreadiness.cab

New location: https://omex.cdn.office.net/mirrored/sccmreadiness/SOT_SCCM_AddinReadiness.CAB

 

When will this happen?

The new location for the readiness file will take effect on March 2nd 2021 After that date, the old location will no longer be used. 

 

How this will affect your organization

Your top-level site server for Configuration Manager needs to be able to access the new location of the readiness file to be able to download the file. 

 

If your top-level site server can’t access the new location, the Microsoft 365 Apps Upgrade Readiness dashboard won’t have access to the most up-to-date readiness data. If a version of the readiness file was downloaded previously from the old location, the dashboard will keep working but will be using readiness data that is out-of-date.

 

What you need to do to prepare 

You need to make sure that your top-level site server can access the new location of the readiness file. If your organization restricts network communication with the internet using a firewall or proxy device, make sure to allow this endpoint:

  • omex.cdn.office.net to support the evaluation of Office add-in readiness.

For more information about the endpoints used by Configuration Manager when managing Microsoft 365 Apps, see Manage Microsoft 365 Apps.

 

For more information about the Microsoft 365 Apps Upgrade Readiness Dashboard, see Office 365 Client Management dashboard

2 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-2121723%22%20slang%3D%22en-US%22%3ERe%3A%20Download%20location%20change%20for%20Microsoft%20365%20Apps%20readiness%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2121723%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F690118%22%20target%3D%22_blank%22%3E%40AntonKolobov1%3C%2FA%3E%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ethe%20change%20will%20only%20be%20made%20on%202nd%20of%20March%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eafter%20the%20day%2C%20you%20can%20check%20the%26nbsp%3B%3CEM%3EFileVersion%20%3C%2FEM%3Ecolumn%20in%20the%26nbsp%3B%3CEM%3EOffice_AdoptionStatus%3C%2FEM%3E%26nbsp%3Btable.%20If%20the%20file%20version%20is%20higher%20or%20equal%20to%2020.4.10930.10000%2C%20file%20was%20downloaded%20successfully.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2121457%22%20slang%3D%22en-US%22%3ERe%3A%20Download%20location%20change%20for%20Microsoft%20365%20Apps%20readiness%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2121457%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20any%20way%20to%20check%20if%20my%20top-level%20site%20server%20has%20successfully%20downloaded%20the%20newest%20readiness%20file%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2110282%22%20slang%3D%22en-US%22%3EDownload%20location%20change%20for%20Microsoft%20365%20Apps%20readiness%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2110282%22%20slang%3D%22en-US%22%3E%3CP%3EWe%E2%80%99re%26nbsp%3Bchanging%20the%20location%20of%20the%20readiness%20file%20that%20is%20downloaded%20by%20the%20Microsoft%20365%26nbsp%3BApps%26nbsp%3BUpgrade%20Readiness%20dashboard%20in%20Microsoft%20Endpoint%20Configuration%20Manager%20(version%201906%20or%20later).%26nbsp%3BThis%20dashboard%26nbsp%3Bhelps%20you%20determine%20which%20devices%20are%20ready%20to%20update%20to%20Microsoft%20365%20Apps.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENote%3A%26nbsp%3BIf%20you%26nbsp%3Bdon%E2%80%99t%26nbsp%3Buse%20the%20Microsoft%20365%26nbsp%3BApps%26nbsp%3BUpgrade%20Readiness%20dashboard%2C%20you%20can%20ignore%20this%20information.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOld%26nbsp%3Blocation%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcontentstorage.osi.office.net%2Fsccmreadinessppe%2Fsot_sccm_addinreadiness.cab%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fcontentstorage.osi.office.net%2Fsccmreadinessppe%2Fsot_sccm_addinreadiness.cab%3C%2FA%3E%3C%2FP%3E%3CP%3ENew%26nbsp%3Blocation%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fomex.cdn.office.net%2Fmirrored%2Fsccmreadiness%2FSOT_SCCM_AddinReadiness.CAB%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fomex.cdn.office.net%2Fmirrored%2Fsccmreadiness%2FSOT_SCCM_AddinReadiness.CAB%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3EWhen%20will%20this%26nbsp%3Bhappen%3F%3CP%3EThe%20new%20location%20for%20the%20readiness%20file%20will%20take%20effect%20on%26nbsp%3BMarch%202nd%202021%20After%20that%20date%2C%20the%20old%20location%20will%20no%20longer%20be%20used.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3EHow%20this%20will%20affect%20your%20organization%3CP%3EYour%26nbsp%3Btop-level%20site%20server%26nbsp%3Bfor%20Configuration%20Manager%20needs%26nbsp%3Bto%20be%20able%20to%20access%26nbsp%3Bthe%26nbsp%3Bnew%20location%20of%20the%20readiness%20file%20to%20be%20able%20to%20download%20the%20file.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20your%20top-level%20site%20server%26nbsp%3Bcan%E2%80%99t%26nbsp%3Baccess%20the%20new%20location%2C%20the%20Microsoft%20365%26nbsp%3BApps%26nbsp%3BUpgrade%20Readiness%20dashboard%20won%E2%80%99t%20have%20access%20to%20the%20most%20up-to-date%20readiness%20data.%20If%20a%20version%20of%20the%20readiness%20file%20was%20downloaded%20previously%20from%20the%20old%20location%2C%20the%20dashboard%20will%20keep%20working%20but%20will%20be%20using%20readiness%20data%20that%20is%20out-of-date.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3EWhat%20you%20need%20to%20do%20to%20prepare%26nbsp%3B%3CP%3EYou%20need%20to%20make%20sure%20that%20your%20top-level%20site%20server%20can%20access%20the%20new%20location%20of%20the%20readiness%20file.%26nbsp%3BIf%20your%20organization%20restricts%20network%20communication%20with%20the%20internet%20using%20a%20firewall%20or%20proxy%20device%2C%20make%20sure%20to%20allow%20this%20endpoint%3A%3C%2FP%3Eomex.cdn.office.net%20to%20support%20the%20evaluation%20of%20Office%20add-in%20readiness.%3CP%3EFor%20more%20information%20about%20the%20endpoints%20used%20by%20Configuration%20Manager%20when%20managing%20Microsoft%20365%20Apps%2C%20see%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fconfigmgr%2Fcore%2Fplan-design%2Fnetwork%2Finternet-endpoints%23manage-microsoft-365-apps%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3EManage%20Microsoft%20365%20Apps%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20more%20information%20about%20the%20Microsoft%20365%26nbsp%3BApps%26nbsp%3BUpgrade%20Readiness%26nbsp%3BDashboard%2C%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fconfigmgr%2Fsum%2Fdeploy-use%2Foffice-365-dashboard%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3EOffice%20365%20Client%20Management%20dashboard%3C%2FA%3E.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2110282%22%20slang%3D%22en-US%22%3E%3CP%3EWe%E2%80%99re%26nbsp%3Bchanging%20the%20location%20of%20the%20readiness%20file%20that%20is%20downloaded%20by%20the%20Microsoft%20365%26nbsp%3BApps%26nbsp%3BUpgrade%20Readiness%20dashboard%20in%20Microsoft%20Endpoint%20Configuration%20Manager%20(version%201906%20or%20later).%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2110282%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECloud-attached%20management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESoftware%20update%20management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Co-Authors
Version history
Last update:
‎Feb 11 2021 09:02 AM
Updated by: