(Updated) Legacy SharePoint Online Content Delivery Network (CDN) domain to be retired—review configurations

Updated January 8, 2026: We have updated this post as a reminder. Thank you for your patience. 

[Introduction]

As part of ongoing service modernization, Microsoft has migrated the hosting of SharePoint Online static assets to the Microsoft Azure Front Door (AFD) content delivery network (CDN), using the new domain public-cdn.sharepointonline.com. This migration was previously announced in MC1066155 and completed in July 2025.

This message is a follow-up notice to retire the legacy CDN domain publiccdn.sharepointonline.com. After this rollout completes, content referenced via the legacy domain will no longer be accessible, and users will receive 404 errors when trying to access resources hosted on the legacy domain.

[When this will happen:]

General Availability (Worldwide): Rollout begins March 31, 2026, and completes by late April 2026.

[How this affects your organization:]

Who is affected:

• Organizations using SharePoint Online with applications, scripts, or configurations that hardcode the legacy CDN domain.
• Developers using SharePoint Framework (SPFx) with hardcoded cdnBasePath values.
• Admins who have configured domain-based allow lists in their network settings.

What will happen:

• The legacy domain publiccdn.sharepointonline.com will be retired.
• Any content referenced via the legacy domain will return 404 errors.
• The same resources remain available through the new CDN domain public-cdn.sharepointonline.com.
• The legacy domain previously served as an automatic hosting endpoint for SharePoint resources.
• The 404 error does not indicate data loss—only the access path is affected.
• Hardcoded references to the legacy domain will fail once the domain is retired.

[What you can do to prepare:]

• Review your applications, scripts, and configurations for any hardcoded references to publiccdn.sharepointonline.com.
• Update affected components to use supported and dynamic endpoints to ensure continued functionality.
• For SPFx applications:
  • If using an external CDN, it’s fine to update the cdnBasePath.
  • If relying on automatic hosting through the Microsoft 365 Public CDN, do not hardcode cdnBasePath—leave it unchanged, shown in the code snippet box below. For more details, refer to Update your solution project for the CDN URLs.

{
  "cdnBasePath": "<!-- PATH TO CDN -->"
}

• Ensure public-cdn.sharepointonline.com is included in your domain-based allow lists.
• Validate your updates before March 31, 2026 to prevent potential service disruptions.
• Monitor network traffic and optionally block requests to the legacy domain to confirm that content hosted through the CDN continues to function properly.
• Learn more: Overview of the SharePoint Framework

[Compliance considerations]

No compliance considerations identified, review as appropriate for your organization.