SharePoint gets a PowerShell command to delete brand fonts worldwide
Reviewed by Helen Jones
Microsoft is adding Remove-SPOFontFile to SharePoint Online PowerShell. The cmdlet deletes brand font files from the Brand Fonts library used by SharePoint Brand Center, including copies in primary and satellite geographies. If a site or page still points at a removed font, SharePoint falls back to Microsoft-defined fonts. Font packages that still reference the deleted file are not removed automatically. They surface warnings instead. Rollout runs from late September 2026 through mid-October 2026. Public CDN must be enabled, and admins need an updated SharePoint Online PowerShell module after the feature lands.
Until now, Brand Center made it easy to push custom fonts into the tenant and much harder to retire them cleanly. Unapproved, unlicensed, or leftover brand kits could sit in the Brand Fonts library, with multi-geo tenants especially exposed to leftover copies that no longer matched what brand or legal wanted. The change closes that lifecycle gap. Deletion is now a supported admin action rather than a half-clean manual mess, while live pages stay readable through fallbacks. Packages that still depend on the old file warn instead of vanishing, which means cleanup is safer but still needs a check before you pull the trigger on anything the intranet still uses.
Analysis
Treat this as a compliance and brand-hygiene fix, not a general SharePoint cleanup win. If you use Brand Center fonts or run multi-geo, list what sits in Brand Fonts, confirm Public CDN and the PowerShell module, then remove only fonts brand or legal have retired after a quick scan of packages that still reference them.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "SharePoint gets a PowerShell command to delete brand fonts worldwide", Collab365 Spaces. 1 source referenced.