Short answer: The built-in Microsoft 365 CDN caches selected static files used by SharePoint Online—such as scripts, images, icons, and resource-library files—at distributed edge locations. Browsers can retrieve those files from a nearby endpoint instead of repeatedly downloading them from the SharePoint origin. It is a SharePoint asset-delivery feature, not a promise that all Office 365 or Microsoft 365 data is delivered through a CDN.
What the Microsoft 365 CDN actually does
Microsoft defines a content delivery network as geographically distributed proxy and file servers connected by high-speed backbone networks. When a browser requests an eligible file, Microsoft 365 can return it directly or redirect the request to a CDN URL. If an edge node does not already have the file, it retrieves and caches it before serving the response.
As an Amazon Associate I earn from qualifying purchases.
For SharePoint Online, Microsoft positions the built-in CDN as a way to host static assets and improve SharePoint page performance. The service uses HTTP/2 and is included with the SharePoint Online subscription. It does not mean that documents, lists, mail, Teams data, or every other Microsoft 365 workload is automatically being served from a CDN. SharePoint performance also depends on page design, browser and device conditions, network paths, and other factors, as Microsoft explains in its modern SharePoint performance guidance.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →What files should you put on the Microsoft 365 CDN?
Choose files that are static or change infrequently and that many pages or users request. Typical candidates include:
#1 Best Overall
- JavaScript and other client-side scripts
- Images, icons, and other generic page graphics
- Static files embedded in SharePoint pages
- Client-side resource libraries
- Large downloadable installation or package files, when reducing repeated load on the SharePoint site is useful
Frequently requested small scripts and images can benefit from edge caching because the same objects are requested repeatedly. Large files can also be reasonable candidates, although the CDN does not make a file automatically public-safe or guarantee a particular download speed.
Assets to keep out
- Frequently changing content that would make cache freshness difficult to manage
- Confidential documents, internal-only resources, or anything whose URL must not be usable anonymously
- Personal or regulated data
Assess the sensitivity and update pattern of each asset before placing it in an origin. The CDN is not a substitute for SharePoint permissions, publishing controls, or data-classification policy.
Rank #2
Public and private origins: the security decision
An origin is the SharePoint site, library, or folder from which the CDN obtains files. Microsoft documents both public and private origin models. The choice determines who can retrieve the cached asset.
| Origin choice | Access behavior | Appropriate use |
|---|---|---|
| Public | Assets are anonymously accessible to anyone who has the URL. | Generic, non-sensitive images, scripts, icons, and other material intended for broad distribution. |
| Private | Access remains subject to the authenticated SharePoint context and its controls. | Assets that require organizational access restrictions and are suitable for the private-origin model. |
Never place sensitive organizational resources in a public origin. A long or obscure URL is not an access-control mechanism: anyone who obtains it can request the asset anonymously.
How do I enable the Office 365 CDN for SharePoint Online?
Microsoft’s setup process is administrative rather than a hardware installation. Use the SharePoint Online CDN configuration documentation for the current command syntax and policy details.
- Confirm eligibility and scope. Check the tenant’s cloud environment and decide whether the built-in public or private CDN model fits the assets and access requirements.
- Check the current tenant CDN status. Review whether a CDN is already enabled and which policies and origins are in effect.
- Enable the intended CDN type. Microsoft documents workflows through SharePoint Online Management Shell and CLI for Microsoft 365.
- Define one or more origins. Point each origin at the SharePoint site, library, or folder that contains the selected static files.
- Organize and publish the assets. Keep only appropriate files in each origin and update page references to the CDN-served locations according to Microsoft’s documented pattern.
- Manage policies and lifecycle. Review origins, files, cache behavior, and access decisions as sites and applications change.
Microsoft’s enablement tutorial says an origin’s final configuration takes approximately 15 minutes. That is an approximate procedural estimate, not a guaranteed propagation time or service-level commitment. Follow the current tutorial, Enable the Microsoft 365 CDN, when carrying out the operation.
Network planning can determine whether the CDN helps
Moving an asset to an edge cache does not remove the rest of the network path. The browser still needs an efficient route to the CDN endpoint. Microsoft identifies client-to-CDN latency as a key consideration and recommends allowing browsers to reach CDN endpoints directly rather than forcing CDN traffic through centralized proxies that add distance or inspection hops.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteNetwork checks for administrators
- Map where remote and office users connect from and which CDN endpoints they are likely to use.
- Determine whether proxy, secure web gateway, or hairpinning policies detour CDN traffic through a central location.
- Review Microsoft 365 network insights and trusted-endpoint handling.
- Keep endpoint lists and bypass rules maintained automatically where possible; stale lists can send users back through inefficient paths.
- Measure your own page and asset behavior before promising a benefit. The cited Microsoft guidance provides no tenant-specific benchmark or universal percentage improvement.
Broader planning guidance is available in Microsoft’s optimal networking for Microsoft 365 tenants.
Best Value
Cloud availability and service boundaries
Verify the current eligibility of the tenant before writing an operational runbook. Microsoft’s pages do not list identical exclusions: the setup page names US Government and China as unsupported, while the general CDN overview also lists Germany. Treat the applicable cloud documentation for your tenant as authoritative rather than assuming worldwide availability.
The built-in Microsoft 365 CDN is part of SharePoint Online. It is different from provisioning an Azure CDN endpoint for custom hosting. Microsoft’s overview explains that a separately deployed Azure CDN instance requires an Azure subscription and is not the same service as the built-in Microsoft 365 CDN. Azure may be relevant when assets live outside SharePoint or need a different hosting and control model, but it introduces a separate service, configuration, and cost boundary.
Deployment choices at a glance
| Question | Built-in Microsoft 365 CDN | Separate Azure CDN |
|---|---|---|
| Primary scope | Static assets hosted for SharePoint Online. | Custom-hosted assets and applications, including content outside SharePoint. |
| Subscription boundary | Included with the SharePoint Online subscription, subject to tenant eligibility. | Requires an Azure subscription. |
| Origin planning | SharePoint sites, libraries, or folders. | Azure-supported origins and a separately managed endpoint. |
| Best fit | SharePoint page scripts, images, icons, and resource files. | Organizations that need custom hosting scope or Azure-specific controls. |
Neither option supplies a universal speed guarantee. The useful choice depends on asset location, sensitivity, cloud availability, and the actual network route used by clients.
Free tools Windows power users keep installed
One-click scans. No signup required.
Administrator checklist
- List the exact static assets and owners.
- Classify each asset as public-safe or restricted.
- Select the SharePoint site, library, or folder that will be the origin.
- Confirm the tenant’s cloud eligibility against current Microsoft documentation.
- Check proxy and secure-web-gateway paths to CDN endpoints.
- Enable and configure the CDN with SharePoint Online Management Shell or CLI for Microsoft 365.
- Document origin, policy, ownership, update, and removal procedures.
- Validate behavior with representative users and networks instead of relying on a generic performance claim.
The Bottom Line
The Microsoft 365 CDN is a focused SharePoint Online asset cache: use it for suitable static files, choose origins and public/private access deliberately, and design the network so browsers can reach edge endpoints efficiently. It improves the delivery path for those assets; it does not turn all Microsoft 365 content into CDN content.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
