For Microsoft 365 administrators, the change separates the governance side of Brand Center from its font-delivery feature. Tenants that want a controlled location for brand managers and organizational branding settings will no longer have to approve Public CDN merely to turn Brand Center on. Public CDN will still be needed when an organization decides to use capabilities that depend on it, with Microsoft explicitly naming organizational fonts.
The practical value is less about faster setup than removing a security, compliance, and change-control objection that has kept some SharePoint teams from deploying Brand Center at all. Until now, enabling a feature intended to centralize brand governance also changed a SharePoint tenant-wide delivery setting.
The existing setup still requires Public CDN
Microsoft’s current SharePoint Brand Center documentation still states plainly that the app “requires the use of Public CDN.” The setup instructions require a global administrator to consent to Public CDN during Brand Center creation for tenants with no organizational asset libraries, and also for tenants already using organization assets with a Private CDN.
That documentation reflects the old behavior described in Roadmap 571391. In effect, organizations that wanted Brand Center for themes, images, templates, or administrative governance had to accept a Public CDN configuration even when they had no plan to distribute custom fonts.
Microsoft’s own Community Hub discussion from February 2025 described the mismatch especially clearly. A Microsoft responder said that themes managed through Brand Center do not use the Public CDN, but the administrator still had to accept the CDN’s potential use for custom fonts in order to create the Brand Center. The October update appears designed to eliminate exactly that bundled consent.
The documentation has not yet been revised to reflect the forthcoming setup path. That is expected for a roadmap item still marked In development, but it leaves administrators with an important operational point: the Public CDN requirement remains in force until Microsoft actually ships the revised experience. A roadmap entry is a deployment notice, not a tenant configuration change that can be acted on today.
What changes for organizations using themes and assets
Brand Center is SharePoint’s central administrative experience for managing branded assets and design choices. It can work with the SharePoint site that already hosts an organization’s asset libraries, or it can create a new Brand Center site. The site’s owners are then the people who administer the Brand Center application and its assets.
Under the revised setup, an organization can establish that control point while deferring Public CDN. That matters in tenants where SharePoint administrators and security teams treat CDN enablement as a separate architectural decision, requiring review of asset types, publishing behavior, data classification, and approved origins.
Microsoft’s Public CDN is intended to cache static content closer to requesting browsers. Microsoft documents that the service supports common web and font formats including CSS, JavaScript, images, SVG, EOT, TTF, and WOFF files. This improves delivery performance, but it also means the tenant setting has consequences beyond a single Brand Center site: it is a SharePoint Online capability managed at the tenant level.
The new setup flow should therefore help three groups in particular:
- Organizations that want to centralize SharePoint branding governance but prohibit public asset delivery by policy can deploy Brand Center without making an immediate exception.
- Tenants already using Private CDN-backed organizational asset libraries will no longer need to activate Public CDN merely because the same site becomes the Brand Center location.
- Administrators can stage adoption by setting up Brand Center and delegating ownership first, then enabling Public CDN later only after deciding to publish organizational fonts.
Microsoft’s roadmap wording is careful: it says tenants can defer Public CDN until they need a feature that depends on it. It does not say Brand Center will cease to support or use Public CDN. The distinction matters. Public CDN is becoming optional for initial setup, not obsolete for all Brand Center workloads.
Organizational fonts remain the dividing line
The reason Public CDN has been coupled to Brand Center is custom-font delivery. Microsoft’s SharePoint documentation says turning on Brand Center enables access to the custom fonts feature, while its CDN guidance lists font file types among the content that Public CDN can serve.
Microsoft has also been explicit elsewhere that Brand Center font assets require Public CDN. Its earlier custom-font announcements described organization fonts as available in additional SharePoint geographies only where organizational asset libraries are configured with Public CDN. The current Brand Center documentation similarly says that custom fonts across multiple geographies require an organization asset library in each relevant geo that uses Public CDN.
That means the new setup choice should not be read as a workaround for a tenant that needs custom font packages but does not want Public CDN. It is not. If the objective is to make organization-managed fonts available in SharePoint’s branding controls, the Public CDN dependency remains.
There is a meaningful security and governance reason for treating that dependency separately. Microsoft’s Public CDN documentation describes static-asset caching and tenant-level origins; the configuration is not equivalent to granting a small group of Brand Center owners access to a private SharePoint library. Font packages are meant to be fetched by browsers across the organization, so their delivery mechanism is fundamentally different from a restricted planning document or a draft marketing asset.
Administrators should therefore keep proprietary, embargoed, customer-specific, or otherwise sensitive material out of libraries configured as Public CDN origins. Microsoft’s change makes that governance conversation easier: a tenant no longer has to resolve it on day one merely to create Brand Center.
The rollout leaves several implementation details unanswered
Roadmap 571391 gives a general-availability target of October 2026, but Microsoft has not published an exact rollout date, tenant-release sequence, or transition instructions for existing Brand Center deployments. It also does not say whether tenants that previously enabled Public CDN solely because Brand Center required it will receive any detection, cleanup prompt, or recommended path for disabling the service.
That omission is significant for existing installations. Enabling Public CDN and creating CDN origins are separate administrative operations, and disabling a service that has subsequently become optional could affect other SharePoint workloads, custom SharePoint Framework solutions, organizational asset libraries, or already-published fonts. An admin should not assume that a future optional setup switch makes it safe to disable Public CDN in an established tenant.
Microsoft’s documented management commands make the necessary pre-change inventory straightforward. SharePoint administrators can check whether Public CDN is enabled and inspect configured public origins with Get-SPOTenantCdnEnabled -CdnType Public and Get-SPOTenantCdnOrigins -CdnType Public. The same status can be retrieved through the CLI for Microsoft 365.
Before changing anything in October, IT teams should identify why Public CDN is enabled in their tenant, not merely whether it is enabled. A configuration might predate Brand Center and support an application catalog, custom web parts, existing asset libraries, or another SharePoint publishing design. Removing an origin or disabling the service without that inventory risks turning a Brand Center cleanup into a broader SharePoint outage.
A smaller consent screen with a real administrative payoff
Microsoft has framed the update as flexibility, but the larger change is that Brand Center will no longer force a tenant-wide technical choice before an organization can use its governance features. The present arrangement has been hard to justify for teams interested only in theme management or a central place to organize brand assets, because the particular CDN requirement was tied chiefly to a capability they might never deploy.
The revised setup should also reduce friction between Microsoft 365 global administrators and brand owners. Global administrators will still control creation and tenant-level settings, while Brand Center site owners can manage the day-to-day application. Separating the CDN decision means a branding project can begin without requiring the same approval process as a public content-delivery configuration.
Microsoft’s documentation needs to catch up before the rollout reaches general availability. Until it does, the clearest planning assumption is simple: create or retain Brand Center without Public CDN only after the October 2026 change appears in the Microsoft 365 admin center; enable Public CDN later if the organization decides to use organizational fonts.