Workday OfficeConnect Version Compatibility Matrix

Which Workday OfficeConnect client versions work with which Workday Adaptive Planning releases — including the forced-upgrade grace periods.

Workday ships OfficeConnect alongside Adaptive Planning releases on a roughly six-month cadence (R1 in spring, R2 in fall). Each release ships a new OfficeConnect client, and the older client is blocked at sign-in after a grace period.

This matrix tracks what’s compatible right now and what’s coming.

New in 2026R1 Currently shipping: OfficeConnect 2026R1, released March 14, 2026. See What’s New in 2026R1.

Current support matrix

Workday ReleaseOfficeConnect clientStatusNotes
2026R12026R1Current — fully supportedReleased March 14, 2026. Adds View By and personal what-if scenarios.
2025R22025R2 or 2026R1Supported with grace periodSeptember 2025 release. End-of-life when 2026R2 ships (fall 2026).
2025R12025R1 or newerOutside grace window — clients blocked at sign-inIntroduced write-back. Upgrade is mandatory.
2024R2 and earlierUnsupportedClient blocked at sign-in. Upgrade immediately.

Forced-upgrade grace periods

Each release has a grace period during which the prior client can still sign in. After the grace ends, the older client is blocked.

Install modelGrace period from release date
Per-user (current-user only install)30 days
Per-machine (all-users install)60 days

The grace clock starts on the release date (not the day your tenant adopts it). Plan upgrade waves accordingly.

Feature-by-release table

FeatureFirst shippedNotes
Personal what-if scenarios2026R1Requires tenant administrator to enable
View By (open cell data in new sheet)2026R1Ribbon command, no admin gate
Write-back from Excel to Adaptive2025R1Tenant version must be in Input state; requires Input permission
OfficeConnect for WordLong-standingCompatible with all current releases
OfficeConnect for PowerPointLong-standingCompatible with all current releases
Cell ExplorerLong-standingBehavior tweaks each release; check release notes
Repeating reportsLong-standingPerformance characteristics improve incrementally each release

Excel compatibility

Excel versionWindowsMac
Microsoft 365 (current build)Full supportFull support (JavaScript add-in)
Office 2021 standaloneFull supportFull support
Office 2019 standaloneFull support (until Microsoft’s mainstream EOL)Not supported
Office 2016No longer tested by WorkdayNot supported
Excel for the WebNot supportedNot supported
Excel mobile (iOS/Android)Not supportedNot supported

For the Mac-specific story including the VDI fallback, see OfficeConnect on Mac and Mac VDI Workflow.

How this matrix is maintained

Articles on this site carry minVersion and releaseAdded fields in their front matter. The maintenance cadence:

  1. When Workday announces a release date, this page gets a “next release” row marked Preview.
  2. On release day, the row flips to Current and a new “What’s new” article ships within 14 days — see What’s New hub.
  3. When the next release ships, the prior version moves to “Supported with grace period.”
  4. Once the grace period expires, the version moves to “Outside grace window.”

What to check before an upgrade

For organizations on a managed deployment cadence:

  • Pilot the new version on 5-10 users for 2 weeks before broad rollout. See Upgrade Governance (coming soon).
  • Re-check tenant compatibility. Workday occasionally introduces a tenant-side change that requires the new client (e.g., write-back required 2025R1+).
  • Re-validate add-in conflicts. Each release can subtly change Excel hook behavior — see think-cell Conflict if your finance team uses both.
  • Update Intune/SCCM packages. Bump app version so deployment systems recognize the upgrade — see Intune Win32 Packaging and SCCM/MECM Deployment.

End-user upgrade flow

End users hit the forced-upgrade prompt at sign-in once their grace period expires. They can either:

  • Run the installer themselves (per Install for End Users)
  • Wait for the IT-managed deployment to push the new version automatically

See Check & Update Your Version for the end-user-facing flow.

Result

You can answer the “is this version still supported?” question in seconds, plan upgrade waves around the grace periods, and verify your deployment infrastructure is keyed to current releases.

Next steps