SharePoint Brand Center organizational fonts not appearing in Word/PowerPoint - expected behavior or limitation?

Question

SharePoint Brand Center organizational fonts not appearing in Word/PowerPoint - expected behavior or limitation?

Christian Berg Smith 20

We have deployed organizational fonts via the SharePoint Brand Center, and the fonts are available in the asset library (publicly accessible as required).

However, we are observing the following:

The fonts do not appear in Word or PowerPoint desktop client apps
The fonts do not appear in Word/PowerPoint web apps

We have reviewed the documentation here: https://learn.microsoft.com/en-us/sharepoint/support-for-organization-fonts-in-powerpoint-for-the-web

This documentation suggests support in PowerPoint for the web when the asset library is publicly accessible, which aligns with our configuration.

Our environment:

Microsoft 365 Apps for Enterprise (Monthly Enterprise Channel)
Version 2603

Could you clarify the intended scope of support for organizational fonts from SharePoint Brand Center?

Specifically:

Are organizational fonts expected to be supported in:
- PowerPoint desktop?
  - Word (desktop/web)?
  1. Is there a roadmap to extend Brand Center font support across M365 apps (similar to templates and brand images)?

At the moment, it is unclear whether our experience is due to a configuration issue, a limitation in current support, or a feature that is not yet rolled out.

0 comments

2 answers

Your answer

Answer 1

Tamara-Hu 14,115 Microsoft External Staff Moderator

Hello @Christian Berg Smith,

Good day! I hope you are doing well.

Based on your description, I understand that you’ve uploaded organizational fonts via the SharePoint Brand Center, the fonts are present in the asset library and publicly accessible, but they are not appearing in Word or PowerPoint (both desktop and web). You’re trying to determine whether this behavior is expected, a configuration issue, or a current limitation of the feature.

Please let me know if I misunderstood any part of your issue or if there are additional details you’d like to share.

To help provide the most accurate and effective conclusion, could you please help clarify a few points about your setup:

How were the fonts deployed?
- Were they uploaded only through the SharePoint Brand Center (Brand fonts UI), or
- Were they also configured as an Organization Asset Library for fonts (OfficeFontLibrary) using PowerShell?
If PowerShell was used, was the library designated with a Public CDN?
Approximately how long has it been since the fonts were uploaded and configured?
In which applications are you expecting the fonts to appear?
- PowerPoint for the web
- Word for the web
- PowerPoint desktop
- Word desktop
Is your tenant a standard commercial tenant, or a restricted environment (such as GCC, GCC High, or 21Vianet)?

This additional context will help us better understand your environment and the steps already taken, so we can clearly determine whether this is expected behavior or something that still needs adjustment.

I apologize if I’m not jumping straight to a definitive conclusion here. I want to make sure we avoid assumptions and provide guidance that accurately applies to your configuration and supported scenarios. Once I have the details above, I'll be in a much better position to move forward.

Looking forward to your response so we can get this sorted out together.

If you have extra questions about this answer, please click "Comment".

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.

Christian Berg Smith 20 Reputation points

2026-04-20T09:11:13.0666667+00:00
Hello Tamara-Hu,

How were the fonts deployed?

Were they uploaded only through the SharePoint Brand Center (Brand fonts UI), or

Were they also configured as an Organization Asset Library for fonts (OfficeFontLibrary) using PowerShell?

Answer: The fonts was both deployed via the SharePoint Brand Center UI and also to a different Font Assets library within the SharePoint Brand Center. The custom font org. asset library was to test if the custom library would act differently than the one provided default by the Brand Center.

If PowerShell was used, was the library designated with a Public CDN?

Answer: Correct. Both the default SharePoint Brand Center UI font upload is on the public CDN and likewise with the custom created font org. asset library.

Approximately how long has it been since the fonts were uploaded and configured?

Answer: Around start March.

In which applications are you expecting the fonts to appear?

PowerPoint for the web

Word for the web

PowerPoint desktop

Word desktop

Answer: All four options.

Is your tenant a standard commercial tenant, or a restricted environment (such as GCC, GCC High, or 21Vianet)?

Answer: A standard commercial tenant.
Christian Berg Smith 20 Reputation points

2026-04-20T09:16:40.5466667+00:00

The main difference I can see between the default org. asset provided by the Brand Center is that it is not showing up as an org. asset library, but only as a publicly exposed origin.

As you can see in the picture the custom org. asset library 'Font Assets' is showing correctly as an org. asset library, but both the custom one and default one is on the public CDN.
Tamara-Hu 14,115 Reputation points Microsoft External Staff Moderator

2026-04-20T14:22:00.54+00:00

Hi @Christian Berg Smith,

Thank you for sharing the documentation and for your patience while we work through this together.

Based on the current Microsoft documentation and the information you provided, Organization Font Support in PowerPoint for the web is explicitly stated for customers with Office 365 E3 or E5 licenses. At this time, support under a Microsoft 365 Apps for Enterprise - only environment may not be fully covered or guaranteed, as this scenario is not clearly documented in the official guidance.

Because of this ambiguity, and to avoid making assumptions, I’m in the process of deploying and validating this feature in my own Microsoft E3 environment to better confirm the expected behavior and licensing requirements in practice. This testing can take some time due to backend propagation and service-side dependencies.

I’ll come back with a further update within 48 hours once I have more concrete findings to share.

Thank you very much for your understanding and patience while this is being investigated.
Christian Berg Smith 20 Reputation points

2026-04-21T10:29:58.7566667+00:00

Hi @Tamara-Hu

You're welcome. Thank you for testing this. For informational purposes I can inform you that our organization is currently using E5 licenses.
Tamara-Hu 14,115 Reputation points Microsoft External Staff Moderator

2026-04-21T14:32:12.71+00:00

Thank you for your confirmation @Christian Berg Smith, this is very helpful and will assist me in continuing my testing. I hope everything is going well on your end. I will continue testing your case and keep you updated.
Tamara-Hu 14,115 Reputation points Microsoft External Staff Moderator

2026-04-22T14:28:53.2533333+00:00
Hi @Christian Berg Smith,

Thank you for your patience so far.

I’d like to clarify an important architectural point, as this is likely where the confusion is coming from.

The SharePoint Brand Center font upload is designed specifically for SharePoint branding scenarios, such as site theming and visual consistency within SharePoint. Uploading fonts through the Brand Center UI alone does not make them available as Office organizational fonts for Word or PowerPoint.

For Office (Word/PowerPoint) organizational fonts to work, the fonts must be deployed via a SharePoint site and explicitly registered as an Organization Asset Library of type OfficeFontLibrary by running PowerShell commands. This step is mandatory and cannot be completed through the Brand Center UI.

Specifically, Office font support requires:

A dedicated SharePoint document library

The library to be registered as an OfficeFontLibrary using PowerShell

The library to be exposed via a Public CDN

Because of this design:

Fonts uploaded only through the Brand Center default font location are not consumed by Office apps

Even though the fonts may appear correctly in SharePoint, they are not applied to Word or PowerPoint

The document and configuration you referenced are therefore unlikely to be affecting Office font availability

While you tested by uploading fonts both via the Brand Center UI and a separate Font Assets library, only the library that is explicitly registered via PowerShell as an OfficeFontLibrary is relevant for Office. The Brand Center-managed library itself does not function as an Office font source.

Based on my testing, when fonts are deployed correctly via a SharePoint library registered as an OfficeFontLibrary using PowerShell, the fonts can be used and rendered in both Word and PowerPoint on the web and desktop. However, for desktop applications, this relies on how Office handles font availability (for example, whether the font is already available to the OS), and is not the same as native Brand Center integration.

This behavior is expected due to the fact that SharePoint Brand Center fonts and Office organizational fonts are separate features, and at this time there is no publicly available roadmap indicating expanded support.

Please let me know if you have any further questions. Thank you again for sharing your inquiry!
Christian Berg Smith 20 Reputation points

2026-04-23T10:50:39.93+00:00

Hi @Tamara-Hu

Thank you for your explanation.

Based on your test it sounds like you got it working with a dedicated SharePoint library, which is also what I've done after testing the Brand Center built-in feature.

I have created a dedicated/custom library within the SharePoint site and named it 'Font Assets' and deployed this as an OrgAssetLibrary with the OrgAssetType set to OfficeFontLibrary, but the fonts are not showing up either in desktop or web versions of Word/PowerPoint.

The deployed fonts within the asset library are not existing fonts with the Word/PowerPoint apps.

Please see below picture where I've highlighted the custom 'Font Assets' library I've deployed.

And here you can see that is it deployed on the public CDN:
Christian Berg Smith 20 Reputation points

2026-04-23T11:02:51.9466667+00:00

Hi @Tamara-Hu

For testing purposes in our own environment, I'll remove our 'Font Assets' from the public CDN and also remove the OrgAssetLibrary. I'll wait a couple of days and re-deploy it to the CDN to see if anything changes in our end.
Tamara-Hu 14,115 Reputation points Microsoft External Staff Moderator

2026-04-23T11:14:18.08+00:00

Hi @Christian Berg Smith,

Thank you for the update. I really appreciate you taking the time to test this on your side. That sounds like a good approach, and it will be helpful to see if redeploying the assets makes any difference.

Please feel free to proceed with your testing, and I’ll be here waiting for your findings. If you need any assistance or would like me to review anything during the process, don’t hesitate to let me know.

Also, if these are public fonts, could you kindly share the font name and the link where you download the font? That would help us better understand your setup and provide more targeted guidance if needed.

I'm looking forward to your next update.
Christian Berg Smith 20 Reputation points

2026-04-27T06:38:38.8266667+00:00

Hello @Tamara-Hu

I have now re-added our OfficeFontLibrary on the public CDN and will give it +24 hours before checking font availability in Word/PowerPoint apps both on client and web.

The fonts are the following ones which have been uploaded from my device to the asset library:
Tamara-Hu 14,115 Reputation points Microsoft External Staff Moderator

2026-04-28T07:36:36.0933333+00:00

Thank you for the update and the screenshot, @Christian Berg Smith. I appreciate it and look forward to your next updates.
Christian Berg Smith 20 Reputation points

2026-04-28T10:46:30.16+00:00

Hi @Tamara-Hu

Unfortunately the organization fonts are still not showing up. Tested with both client apps and webapps.

Here's what I get presented via webapps:

No organization font option.

Manually searching for Metric fonts, doesn't return any results either.
Tamara-Hu 14,115 Reputation points Microsoft External Staff Moderator

2026-04-28T11:56:51.1333333+00:00
Hi @Christian Berg Smith,

Based on the information you’ve shared so far, your configuration appears to align with the documented requirements, the fonts have been uploaded via SharePoint Brand Center, are exposed through a public CDN, and sufficient time has been allowed for propagation. However, since the fonts are still not appearing as expected, this may indicate a scenario that is not fully covered by current documentation or could involve a service-side issue.

Given this situation, I would recommend reaching out to the Microsoft Support team for further investigation. They have access to backend diagnostic tools and service-side visibility that are not available through the Q&A forum, and they will be in a better position to validate your tenant configuration, check font catalog registration, and confirm whether this behavior is expected or related to an ongoing issue.

For Business support:

Find your Microsoft 365 admin: If you don't know who the global admin is in your organization, you can find guidance here: How can I find my Microsoft 365 admin? - Microsoft Support

Submit a service request: The Global Administrator should create a support request with Microsoft to receive advanced technical assistance. For detailed instructions, see: Get support - Microsoft 365 admin | Microsoft Learn

If your organization's Office 365 Business/Education subscription is from a partner or reseller, and the global administrator is unable to open a service request on your end, contact the reseller's support provider to help open a service request on behalf of you instead.

If you have additional findings, please feel free to share them here to help others in the community.

I’m sorry if this redirection causes any inconvenience, and I truly appreciate your understanding. As a forum moderator, I unfortunately do not have the capability to perform deeper tenant-level diagnostics or access internal systems.

Thank you very much for your patience and for providing detailed information throughout the discussion. I truly appreciate your efforts in validating the setup. I hope the Microsoft Support team will be able to assist you further and help get this resolved as soon as possible.
Christian Berg Smith 20 Reputation points

2026-05-04T06:13:49.0233333+00:00

Hello @Tamara-Hu

Thank you for your assistance with this issue, I'll raise a support ticket with Microsoft support.

Just out of curiosity, which M365 apps version did you conduct your successful test with? Version 2603 via the monthly enterprise channel or a newer version via the current enterprise channel?
Christian Berg Smith 20 Reputation points

2026-05-04T06:47:20.2033333+00:00

I might have found the problem. Previously when I've uploaded fonts, I've uploaded them manually via the SharePoint web page and not utilizing the Set-SPOCustomFontCatalog command provided by Microsoft.

I've now uploaded the fonts via this command and awaiting results are 24 hours of updating.

I'll provide feedback.
Christian Berg Smith 20 Reputation points

2026-05-04T06:54:58.5133333+00:00

After adding fonts via Set-SPOCustomFontCatalog our font library now looks like this:

Not sure why folder 1 and 2 has appeared, these does not exist within the font folder I uploaded.
Christian Berg Smith 20 Reputation points

2026-05-04T06:57:46.1333333+00:00

Fonts are now appearing in M365 web apps
Christian Berg Smith 20 Reputation points

2026-05-04T07:17:37.32+00:00

Custom fonts are now also appearing the M365 desktop apps. The resolution was to use the Set-SPOCustomFontCatalog command to upload custom fonts to the SharePoint library. Fonts will not be published correctly if uploading these manually, even though the OrgAssetLibrary is correctly mapped and published on the CDN.
Tamara-Hu 14,115 Reputation points Microsoft External Staff Moderator

2026-05-05T08:07:04.51+00:00
Hi @Christian Berg Smith,

Thank you so much for getting back with such a detailed update! I’m really glad to hear that you were able to identify the root cause and get everything working as expected.

Based on your findings, it does appear that the key requirement is using the Set-SPOCustomFontCatalog command when uploading fonts, rather than uploading them manually through the SharePoint interface. As you’ve observed, manually uploading the font files - even when the Organization Asset Library is correctly configured and exposed via the CDN - does not properly register or publish the fonts for use in M365 applications.

Using the PowerShell command ensures that the fonts are:

Correctly registered in the font catalog

Properly structured in the library (which likely explains the automatically created folders such as “1” and “2”)

Fully recognized by both M365 web apps and desktop apps

It’s great to hear that after using this method, the fonts are now appearing as expected across Word and PowerPoint (both web and desktop). This confirms that the behavior you were experiencing earlier was due to how the fonts were uploaded and registered in the service.

Also, thank you for sharing the screenshots and explaining the behavior (such as the additional folders appearing). This level of detail is incredibly helpful and will definitely benefit others who may run into the same situation.

I truly appreciate the time and effort you put into troubleshooting this and coming back to share the resolution with the community.

Thanks again for your patience throughout the process, and I’m really happy to hear that everything is now working correctly. If you have any further questions or run into anything else, please don’t hesitate to reach out, I’ll be here to help!

Answer 2

Based on the documented behavior, the current support and limitations are:

Scope of support for organization fonts from SharePoint Brand Center / Organization Asset Libraries

Organization fonts uploaded via an Organization Asset Library (OAL) and exposed through the public Microsoft 365 CDN are supported in:
- PowerPoint for the web
- Word for the web
When configured correctly, users should see the organization fonts in the Font dropdown in PowerPoint and Word for the web after propagation (up to 24 hours).
The same organization font infrastructure is also used for brand fonts in SharePoint and Viva Connections experiences via the SharePoint brand center.

Relevant points from the documentation:

“Organization font support for PowerPoint for the web is also available utilizing the organization assets infrastructure. Customers with E3 or E5 licenses can take advantage of Organization Font Support in PowerPoint for the web to edit and display their fonts.”
“Allow 24-hours for the SharePoint servers to update and for the users in your organization to see their organization fonts when using the Font dropdown menu in PowerPoint and Word for the web.”
“This feature is only available on PowerPoint and Word on Web, Windows, Mac, and Mobile.”

Note that the feature requires:

An Organization Asset Library configured with -OrgAssetType OfficeFontLibrary -CdnType Public.
Fonts uploaded via Set-SPOCustomFontCatalog -FontFolder <Local Font Folder Location> -LibraryUrl <Document Library SharePoint URL>.
Up to 24 hours for propagation.

Expected behavior in desktop apps (PowerPoint / Word)

The documentation explicitly states that the feature is “available on PowerPoint and Word on Web, Windows, Mac, and Mobile,” which means organization fonts delivered via this mechanism are in scope for desktop clients as well.
There is no additional configuration documented for desktop apps beyond correctly configuring the Organization Asset Library and font catalog.
If fonts are not appearing in desktop apps but the OAL and CDN are correctly configured, that is not described as expected behavior in the provided documentation and may indicate either:
- Propagation delay (up to 24 hours after catalog upload or change), or
- A deployment/rollout or client issue not detailed in the current docs.

Expected behavior in Word/PowerPoint for the web

With a correctly configured OfficeFontLibrary OAL and public CDN, organization fonts are expected to:
- Render and be selectable in PowerPoint for the web.
- Render and be selectable in Word for the web.
The docs emphasize:
- Fonts are only usable/viewable within the organization.
- Updates to font asset libraries can take up to 24 hours to propagate.
- Changes made directly in the SharePoint document library (outside the PowerShell catalog process) can affect availability and functionality.

If fonts are not appearing in the web apps after:

Confirming the library is registered with Add-SPOOrgAssetsLibrary -OrgAssetType OfficeFontLibrary -CdnType Public (no /AllItems.aspx in URL),
Uploading fonts with Set-SPOCustomFontCatalog,
Waiting at least 24 hours,

then that behavior is not aligned with the documented expectations and would point to a configuration or service issue rather than a documented limitation.

Licensing and tenant limitations

Organization font support in PowerPoint and Word is not available for:
- Office 365 Germany
- Office 365 operated by 21Vianet (China)
- Microsoft 365 US Government plans
Fonts must be licensed appropriately for cloud hosting and use in Microsoft 365; the documentation warns not to use this feature if font licenses restrict cloud hosting or public availability.

Roadmap / parity with other Brand Center assets

The SharePoint brand center provides centralized management for brand assets (logos, images, fonts, etc.) and notes:
- Organization asset libraries already support brand images and templates.
- Organization font support for PowerPoint for the web is available using the same organization assets infrastructure.
The provided documentation does not include a published roadmap or explicit commitment to broader or different behavior beyond:
- Support for PowerPoint and Word on Web, Windows, Mac, and Mobile via the organization assets infrastructure.
- Multi-geo requirements (each geo needing its own OAL using Public CDN for custom fonts to appear in that geo’s “Change the Look” panel and work there).

No additional roadmap details or future expansion plans beyond what is described above are present in the supplied context.

Summary relative to the questions:

Are organizational fonts expected to be supported in PowerPoint desktop and Word (desktop/web)?
- Yes. The feature is documented as available on PowerPoint and Word on Web, Windows, Mac, and Mobile, with fonts delivered via an OfficeFontLibrary Organization Asset Library and public CDN.
Is there a roadmap to extend Brand Center font support across M365 apps similar to templates and brand images?
- The documentation confirms integration with SharePoint/Viva and organization fonts for PowerPoint/Word via the organization assets infrastructure but does not provide further roadmap details or additional app coverage beyond those explicitly listed.

References:

Share via

SharePoint Brand Center organizational fonts not appearing in Word/PowerPoint - expected behavior or limitation?

2 answers

Your answer