Jamf is removing Mac font inventory: prepare for continuity

Article created October 7, 2026 · Source reviewed October 7, 2026 · Official source: Jamf Pro 11.32.0 release notes and documentation · Topic: Mac inventory and fleet management

Jamf lists an estimated October 2026 removal date for font collection in computer inventory. For Mac fleets used by studios, communications departments, engineering firms, or editorial teams, the goal is not to reproduce every historical data point: first identify which decisions genuinely rely on this inventory.

1. What Jamf has actually announced

In the Jamf Pro 11.32.0 deprecations, Jamf lists “Computer inventory collection for fonts” with an estimated removal date of October 2026. This wording announces the end of native collection; by itself, it neither fixes a final release number nor describes an automatic replacement.

Jamf’s inventory documentation still lists fonts among the categories displayed when collection is enabled. Organizations should therefore check their own version, the target release notes, and observed post-upgrade behavior instead of assuming that a calendar date alone determines the state of every instance.

2. Where to find dependencies before upgrading

Start with a consumption audit: advanced searches, smart groups, exports, reports, scripts, API calls, dashboards, and support procedures. Data shown in an inventory record does not necessarily deliver operational value; conversely, an unobtrusive criterion may trigger a policy or support a licensing control.

Then distinguish fonts shipped with macOS, fonts installed by an application, packages distributed through Jamf, fonts activated by a third-party service, and files added locally. These paths do not provide the same evidence of installation, entitlement, or compliance.

3. What does this change for a Belgian or French organization?

For an SME without font-based rules, removal may mainly eliminate unnecessary collection. For a creative agency, mid-market company, large enterprise, or public body, it can affect support for official templates, document consistency, font licensing, or prepress workflows. Being in Belgium or France does not change the Jamf feature, but it can change the contracts, catalogues, and internal responsibilities that need documenting.

IT teams need to identify which applications or business units require detailed visibility. Security and compliance owners should avoid treating the technical presence of a file as proof of a licence. Business teams should validate a short list of critical families and a clear remediation process.

4. Underside analysis: replace exhaustive inventory with a targeted control

Our assessment is that an extension attribute can fit some targeted checks because Jamf documents scripts as a source of custom inventory data. It is not, however, an announced official successor to native font collection. Jamf warns that extension attributes can add inventory time and network traffic, so an exhaustive list of thousands of fonts would rarely be a sound default.

A stronger architecture links the deployment source, font package or service, a minimal Jamf signal, and contractual evidence held outside the MDM. The attribute can answer a bounded question — such as whether an approved business-critical family is present — without turning every recon into a complete catalogue.

5. Recommended action plan

• Export searches, groups, and integrations that currently use font data.
• Classify each dependency: user support, deployment, licensing, compliance, or informational only.
• Remove collection with no owner or associated decision.
• Test the target Jamf release with a pilot group and compare records, exports, and automated rules.
• For critical requirements, design a targeted check and measure its impact on recon duration and returned data.
• Document the licensing source of truth and support procedure separately from Jamf’s technical state.

To place this work in the wider fleet governance programme, also read our guide to Jamf Pro 11.32 and OS 27 inventory and our Apple enterprise Belgium and Apple enterprise France pages.

Official sources: Jamf Pro 11.32.0 — Deprecations and Removals, Computer Extension Attributes, and Computer Inventory and Criteria Reference, accessed October 7, 2026.