‎Legacy SharePoint Online Content Delivery Network (CDN) domain to be retired‎

Question

‎Legacy SharePoint Online Content Delivery Network (CDN) domain to be retired‎

Shaun 86

I have a custom SharePoint application that configures the Global Navigation across our SharePoint environment, and I would like assistance in understanding whether the upcoming retirement of the public CDN has any impact on this solution. Details of the retirement can be found here: https://mc.merill.net/message/MC1184996 The SPFx package references assets hosted in a SharePoint library. I have the library and the packaged solution, but not the original source project. Is it possible to update the CDN path without recreating the project from scratch or will the CDN update automatically?

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Anonymous

Hello Shaun, thank you for reaching out to the Q&A Forum.

I completely understand your concern regarding the upcoming retirement of the legacy public CDN domain and how it might impact your custom Global Navigation application.

Do you happen to have the .sppkg file for that app? If not, you can download it directly from your Tenant App Catalog here: https://[your-tenant-name].sharepoint.com/sites/appcatalog/_layouts/15/tenantAppCatalog.aspx/manageApps

Once you have the file:

Rename the extension from .sppkg to .zip and extract everything into a new, empty folder.
Open a code editor like Notepad++ or Visual Studio Code and use “Find in Files” to search the entire extracted folder for the legacy domain: publiccdn.sharepointonline.com

According to provided link, the only change is the addition of a hyphen. Update every instance of publiccdn.sharepointonline.comto public-cdn.sharepointonline.com

You will find these references in the SPFx manifest JSON files (the files ending in .manifest.json; this is where the cdnBasePath value is baked in after packaging).

The full URLs usually look like this: https://publiccdn.sharepointonline.com/tenantname.sharepoint.com/sites/appcatalog/ClientSideAssets/...

(Only insert the hyphen, leave the rest of the path, tenant name, library, and file hashes exactly as they are.)

After making all the changes:

Save the files.
Go back to the extracted folder, select all files and folders inside it (do not select the parent folder itself), right-click, and compress them into a new .zip file.
Rename the new .zip back to .sppkg.

Upload the modified .sppkg back to your SharePoint App Catalog. It will prompt you to replace the existing solution. Check the box to deploy/enable it tenant-wide.

Once deployed, your Global Navigation solution will point to the new CDN path and continue working after the legacy domain is retired on March 31, 2026.

If your search returns zero results for the old domain, the package does not have the legacy CDN hardcoded (it’s likely using a direct SharePoint library URL or automatic Microsoft hosting). In that case, no changes are needed, it will stay compatible automatically.

Hope this info is helpful. If you have any other questions, please don't hesitate to ask.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Shaun 86 Reputation points

2026-02-27T14:38:48.84+00:00

Thanks very much. Have you tried this yourself, and is it safe to make the change while keeping the original file as a backup in case it doesn’t work?

Also, one of the files in the SharePoint library still references the old CDN. Do those need to be updated as well, or will repackaging the existing app resolve this?
Anonymous

2026-02-27T15:06:05.3966667+00:00

Hello Shaun, thank you for your response.

To be honest, I did test this process on my own test tenant. However, the applications in my environment do not currently have that specific legacy CDN hardcoded, which is why my previous guidance was primarily based on official documentation and standard research.

If you are concerned about potentially impacting your live application, I highly recommend applying these changes in a separate test tenant first if you have one available. This way, if the updated package does not work as expected for any reason, it will not affect your main production environment. In any case, please make sure to keep a safe copy of your original .sppkg file as a backup. You can always simply upload your original backup file back to the App Catalog to instantly restore everything to its previous state if needed.

Regarding the files currently hosted in the SharePoint library, please allow me a little more time to do some further research. I want to see if I can replicate a source environment similar to your case so I can thoroughly test that specific scenario before giving you a definitive answer.
I appreciate your patience, and I will get back to you as soon as I have more concrete information.
Anonymous

2026-03-02T12:06:06.5+00:00

Hello Shaun, have you had a chance to review my reply? I attempted to test this in my own environment, but unfortunately, I wasn’t able to reproduce the scenario. However, based on my research, if any files in your SharePoint library contain references to the old CDN domain within their content, those references will need to be updated as well. Repackaging the SPFx solution does not automatically modify the content inside existing library files.

I also recommend deploying the updated package to a test site or tenant first. This will allow you to verify that the solution loads correctly and confirm that no network requests are still targeting the old domain. Doing so will help ensure that all references have been updated successfully and that the package is properly accepted by SharePoint.
Shaun 86 Reputation points

2026-03-02T19:24:20.0566667+00:00

Thanks I have tested repackaging the SPFx app using your method and it has worked in our test environment so thank you for that.
Anonymous

2026-03-03T07:21:48.6866667+00:00

Dear Shaun

I'm really happy to hear that the information I shared was useful to you! If you ever need more help, feel free to post your questions in the forum. It's not just me, the whole community is here and always happy to support you.