A certificate used by Microsoft 365 apps on macOS and iOS is set to expire on July 13, 2026 — and for organisations still running Office 2019 for Mac, Microsoft has confirmed it will not be pushing a certificate update. The practical result: after that date, affected installations on those platforms will likely encounter authentication or connectivity failures with Microsoft 365 services, with no vendor-supplied remediation path. Windows and Android users are unaffected.

The advisory comes from Microsoft's support documentation, updated in May 2026, and it lands in the context of a product that has been out of support for more than two and a half years. Office 2019 for Mac reached end of support on October 10, 2023, at which point Microsoft ceased delivering security patches, feature updates, and — critically — certificate renewals.

The Certificate Problem, Plainly Stated

The expiring certificate in question sits within the trust chain that Microsoft 365 client applications on macOS and iOS rely on for secure communications with Microsoft's backend services. When that certificate expires without renewal, the client-side validation against Microsoft's services breaks. Depending on how the application handles the failure, users may see authentication errors, lose access to cloud-connected features, or find the application non-functional for anything requiring a live Microsoft 365 connection.

For Office 2019 for Mac specifically, the chain of causation is straightforward: the product is past end of support, Microsoft is not issuing updates for it, and the certificate renewal that would normally arrive via a software update will not arrive. The product will simply age past the expiry date unremediated.

The certificate issue does not affect the Windows or Android versions of Microsoft 365 apps. Whether this reflects differences in how certificate trust is implemented across platforms — macOS and iOS certificate pinning behaviours versus the Windows certificate store model — is not addressed in Microsoft's advisory, but the scoped impact to Apple-ecosystem clients is explicit.

Who Is Actually Exposed

The population at risk breaks into two groups.

The first is organisations or individual users still running Office 2019 for Mac as their primary productivity suite. Despite the October 2023 end-of-support date, anecdotal evidence from enterprise IT forums suggests a non-trivial tail of deployments persists — particularly in environments where software refresh cycles are long, Mac deployments are managed separately from Windows fleets, or procurement constraints have slowed migration. Any of these installations connecting to Microsoft 365 services face a hard deadline.

The second group is subtler: iOS users running Microsoft 365 apps that may not have been kept fully current. The advisory specifies that the certificate impact extends to iOS as well as macOS. Mobile device management teams operating in MDM-governed Apple environments should verify that their Microsoft 365 app versions are current and that automatic updates are enabled — or that they have a mechanism to force a version push before July 13.

There is no workaround for Office 2019 for Mac. The product receives no updates. The only resolutions are migration to a supported Microsoft 365 subscription plan, or acceptance that cloud-connected functionality will break after the deadline.

The Mechanics of an End-of-Support Cliff

It is worth being precise about what end of support actually means in this context, because the implications are often underestimated until they materialise as operational incidents.

When Microsoft ends support for a product, it ceases delivering security patches, bug fixes, and — as this situation illustrates — routine maintenance artefacts like certificate renewals. A certificate, unlike a CVE-linked patch, does not register in most vulnerability scanners. It will not appear on a Qualys or Tenable dashboard as a critical finding until the expiry triggers a failure. That invisibility is exactly what makes certificate expiry in end-of-life software a latent operational risk rather than an immediately visible one.

We have seen this pattern before, when organisations running legacy versions of Internet Explorer discovered — often through outright failures rather than advance warnings — that backend trust anchors had quietly lapsed. The playbook is always the same: a product drifts past its support boundary, certificate maintenance lapses, and the failure mode surfaces not as a graceful deprecation but as a connection error with no patch available. The July 13 date is, at least, a known deadline. That is an advantage not always available in these situations.

iOS: The Less-Discussed Surface

Enterprise Mac management has been a reasonably mature discipline for over a decade, and most IT teams with significant Mac estates have tooling — Jamf, Microsoft Intune, Kandji — to push compliance posture and enforce minimum app versions. The iOS exposure deserves equal attention and may, in some organisations, be less systematically governed.

iOS devices frequently sit in a more loosely managed space in enterprise environments: BYOD policies, personally enrolled devices under MAM-only policies, or executive and field devices that are exceptions to standard MDM. Microsoft 365 apps on iOS that are running outdated versions, or that have not received certificate updates through normal App Store refresh cycles, are in scope for this issue. MDM administrators should query their device inventories for Microsoft 365 app versions and confirm compliance well ahead of the deadline.

Recommended Actions Before July 13, 2026

For IT and operations teams, the immediate tasks are:

Audit for Office 2019 for Mac installations. Query your software inventory tooling — whether that is Jamf Pro, Microsoft Endpoint Configuration Manager, or any asset management layer — for active Office 2019 for Mac deployments. Any found should be treated as a migration priority, not a monitoring item.

Verify iOS Microsoft 365 app currency. Pull MDM reports on Microsoft 365 app versions across enrolled iOS devices. Ensure auto-update policies are in place, and consider a forced update push for any devices showing versions below the current release channel.

Plan migration for Office 2019 for Mac users. The supported path is Microsoft 365 — either through existing enterprise agreements or new licensing. There is no supported in-place upgrade path that preserves Office 2019 for Mac as a product; users must move to a subscription-based plan. For organisations still on perpetual licensing models, this is a licensing conversation as much as a technical one.

Document and communicate the deadline. July 13, 2026 is a fixed date. Internal stakeholders — finance, procurement, end-user computing teams — should be aware that any delay past this point will result in service disruption for affected users, not a degraded-but-functional state.

Looking at what this means for the broader landscape of perpetual-licence Mac deployments: the July 2026 deadline is a forcing function that accelerates what was already an inevitable conversation. The Office 2019 for Mac end-of-support date passed in October 2023; organisations that have run past it for two and a half years have, in effect, been operating on borrowed time. The certificate expiry is the mechanism by which that borrowed time runs out.

For current Microsoft 365 subscribers on macOS and iOS, the action required is simply to confirm that software is current — a standard hygiene task. The urgency and the migration cost fall entirely on the holdout Office 2019 for Mac population.