MC1505610: Brand Center Setup Lets Admins Complete Configuration Without Enabling Public CDN

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
38
0 25 50 75 100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsSharePoint AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The announcement introduces a change to Brand Center setup, allowing administrators to complete configuration without enabling Public CDN. This affects admin setup workflow and governance options but does not require immediate action. User experience impact is minimal and limited to branding features. Admins should be aware that font capabilities remain dependent on enabling Public CDN, but the rollout is straightforward and low risk.
45
🛡️ Admin Impact
20
👥 User Impact
40
⚡ Urgency
35
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Brand Center setup no longer requires enabling Public CDN. Admins can now complete setup first and turn on Public CDN later if needed for fonts.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Worth noting that Public CDN is now optional during Brand Center setup and must be enabled manually for font features.
📅

ROLLOUT TIMELINE

Rolling out:
October 2026

📢 Official Microsoft Message Center Announcement


Public CDN is becoming optional during Brand Center setup
Message ID: MC1505610

[What and Why:]

We are updating the Brand Center setup experience so that administrators can set up Brand Center without enabling Public CDN.

Today, Public CDN is enabled as part of Brand Center setup, even when an organization only wants to use branding governance capabilities that do not require it. With this update, organizations can begin using Brand Center while deferring Public CDN until they need capabilities that depend on it, such as organizational fonts.

[Rollout Schedule:]

General Availability (Worldwide): We will begin rolling out in mid-October 2026 and expect to complete by late October 2026.

[Impact on Your Organization:]

When an administrator sets up Brand Center in the Microsoft 365 admin center:

  • Public CDN will be unselected by default.
  • Brand Center setup can be completed without Public CDN.
  • Public CDN will only be enabled after an administrator explicitly selects the option and confirms the change.
  • Font-related capabilities will remain unavailable until Public CDN is enabled.
  • If Public CDN is already enabled for the tenant, this update will not disable or change it.

This change separates Brand Center setup from Public CDN activation. It does not remove the Public CDN requirement for organizational fonts.

Why we are making this change

Some organizations want to begin using Brand Center for branding governance without introducing an external or public content-delivery dependency.

Making Public CDN optional provides a more incremental adoption path: organizations can establish Brand Center first and enable font capabilities only when they are ready.

[Action Required/Recommendations:]

No action is required. If your organization plans to use organizational fonts, an administrator must explicitly enable Public CDN during setup or later from the applicable settings experience.

[Compliance considerations:]

QuestionAnswer
Does the change include an admin control and can it be controlled through Entra ID group membership?Yes. The feature includes or affects admin controls, policies, permissions, roles, authentication, or management settings as described in this message. Review the linked documentation or admin center controls for group-based configuration support.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update