Deployment on OfficeConnectPro

Fix COM Registration Errors

Mon, 01 Jan 0001 00:00:00 +0000

COM registration errors usually surface during a Workday OfficeConnect install or upgrade and point to a broken Microsoft Office add-in registration. Confirm your machine meets the system requirements before working through the fixes — multiple Office versions installed side by side is the most common root cause.

Symptom: You receive an error like the following when trying to install or update OfficeConnect:

System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject'
to interface type 'Microsoft.Office.Core.IRibbonUI'.

Why this happens

OfficeConnect is an Excel COM add-in that relies on Excel objects registered correctly by your Microsoft Office installation. This error occurs when:

Resolve OfficeConnect Update Errors

Mon, 01 Jan 0001 00:00:00 +0000

Symptom: When updating OfficeConnect, you see:

An error occurred while downloading the update. Details: The underlying connection
was closed: An unexpected error occurred on a send.

Common causes and fixes

Cause 1: Network or proxy blocking the update

Your corporate network or proxy may be blocking the update download.

Fix: Work with your IT team to allowlist the Workday update servers. Alternatively, download the latest installer manually from Product Downloads in Workday and install it directly — bypassing the auto-update.

System Requirements

Mon, 01 Jan 0001 00:00:00 +0000

Verify your machine meets these requirements before installing OfficeConnect.

Required software

All of the following must be installed before running the OfficeConnect installer:

Software	Notes
WebView2 Runtime	Required for the OfficeConnect sign-in UI
Microsoft .NET Framework 4.8	Download from Microsoft
VSTO 2010	Visual Studio Tools for Office runtime
Workday Event Log Components	Installed by the OfficeConnect setup wizard if you have admin rights

Tip: If you have administrator rights on your machine, the per-user installer handles prerequisites automatically. If you don’t, ask your IT team to install these before you run OfficeConnect setup.

Task Pane Not Displaying Correctly

Mon, 01 Jan 0001 00:00:00 +0000

Symptom: Reporting pane is invisible or blank

If the OfficeConnect Reporting pane disappears or shows as blank, it’s usually a display rendering issue in Excel.

Fix:

Open Excel Options Go to File → Options → General.

Change the rendering setting Find the option “Optimize for best appearance” and change it to “Optimize for compatibility”.

Close and reopen Excel The Reporting pane should now display correctly.

Symptom: Floating pane has disappeared

If you undocked the Reporting pane and lost it:

Install as an End User

Mon, 01 Jan 0001 00:00:00 +0000

Follow these steps to install OfficeConnect on your own Windows machine. You’ll need administrator rights, or IT must pre-install the prerequisites.

Prerequisites

All system requirements are met
You have your Workday Adaptive Planning login credentials

Steps

Download the installer Go to Product Downloads in your Workday Adaptive Planning instance (ask your admin for the link if you don’t have it). Download OfficeConnectSetup.exe — always use the latest version.

Run the installer

Double-click OfficeConnectSetup.exe. If you have administrator rights on your machine, Windows will prompt you to allow the installation to run elevated — click Yes.

Install as an IT Admin

Mon, 01 Jan 0001 00:00:00 +0000

For admins & power users This page is for IT administrators deploying OfficeConnect to multiple users or machines. End users installing on their own machine should see Install as an End User.

Two installation modes

Mode	When to use
Per-user	Each user installs on their own workstation. Users can install future updates without admin permissions.
Per-machine	Installed once on a shared machine for all users on that computer. Requires admin permissions for all updates.

Per-user installation is generally preferred — it lets users self-update and reduces IT overhead.

Deploy

Mon, 01 Jan 0001 00:00:00 +0000

Deployment guides for getting Workday OfficeConnect into the hands of your finance team, from a handful of users to an enterprise rollout.

Articles in this section

Deploy via Registry — Push Workday OfficeConnect tenant configuration to user machines using the Windows registry
Intune Win32 Packaging — Package Workday OfficeConnect as a Win32 app for Microsoft Intune, push to all users silently, and verify deployment
SCCM / MECM Deployment — Deploy Workday OfficeConnect through Microsoft Configuration Manager (SCCM/MECM) with silent install switches, detection methods, and required user-rights handling

Sign In & Create Your First Tenant

Mon, 01 Jan 0001 00:00:00 +0000

A tenant in Workday OfficeConnect is a saved connection to a Workday instance. You create it once, and OfficeConnect remembers it for future sessions.

What you’ll need

Before you start, gather these details from your Workday administrator:

Detail	Where to find it
Client ID	Workday OfficeConnect API client
API Endpoint URL	Workday OfficeConnect API client
Authorization Endpoint URL	Workday OfficeConnect API client

If your admin hasn’t yet generated these, see Set Up Workday SSO.

Run the Troubleshooting Tool

Mon, 01 Jan 0001 00:00:00 +0000

When standard troubleshooting steps don’t resolve your issue, the OCSystemChecker tool gathers detailed diagnostic information from your machine to help Workday Support investigate.

When to use it

You’re getting an error during installation or startup that other fixes haven’t resolved
Workday Support asks you to run the tool as part of a support case
You want a diagnostic log before reaching out to Support

Steps

Download OCSystemChecker.zip Download the OCSystemChecker.zip file from the Workday Community or ask your Workday Support contact for the link. Save it to your Desktop.

Extract the zip file Right-click OCSystemChecker.zip → Extract All. Open the extracted folder.

Launch OCSystemChecker.exe Double-click OCSystemChecker.exe. Windows may prompt you to allow it to run — click Yes.

Select the application with the error Choose OfficeConnect for Excel (or the appropriate application) and click Next.

Select the type of issue Choose the closest match (installation error, refresh error, startup error, etc.). If it’s file-specific, attach the problematic file when prompted. Click Next.

Reproduce the error on the 'Re-create Issue' page

Important: While the Re-create Issue page is open, perform the action that causes the error. For example:

Configure

Mon, 01 Jan 0001 00:00:00 +0000

Tenant configuration, single sign-on, and the network plumbing OfficeConnect needs to reach Workday Adaptive Planning.

Articles in this section

Sign In & Create Tenant — Sign in to Workday OfficeConnect for the first time and configure your Workday tenant connection
Multiple Instances — How to switch between production, sandbox, and multi-instances in Workday OfficeConnect
Workday SSO — Configure Workday OfficeConnect to use Workday Single Sign-On for your organization
SSO with Okta — Configure Okta to authenticate Workday OfficeConnect users via Workday SSO — application setup, claim mapping, MFA pairing, and the common failure modes
SSO with Microsoft Entra ID — Configure Microsoft Entra ID (formerly Azure AD) to authenticate Workday OfficeConnect users via Workday SSO — enterprise application setup, claim mapping, and Conditional Access tuning
Refresh with Power Automate — Use Power Automate Desktop to schedule Workday OfficeConnect report refreshes automatically — keep distributed Excel reports up to date without manual intervention

Work with Multiple Instances

Mon, 01 Jan 0001 00:00:00 +0000

If your user ID has access to more than one Workday instance — a sandbox, a linked multi-instance hierarchy, or simply multiple tenants — Workday OfficeConnect handles them through an Instance drop-down in the Reporting pane.

Types of multiple instances

Type	Description
Sandbox	A clone of your production instance. Use it for testing reports and what-if scenarios without affecting live data.
Multi-instances	Linked instances in a hierarchical relationship that share data through account and dimension mapping.

Switching instances

When your user ID has access to multiple instances, an Instance drop-down appears in the Reporting pane.

Workday OfficeConnect on Mac: The VDI Workflow

Mon, 01 Jan 0001 00:00:00 +0000

The native Mac version of Workday OfficeConnect (Excel for Mac JavaScript add-in) supports most reporting workflows, but a few power-user features remain Windows-only — most notably Power Automate Desktop integration, configurable refresh shortcuts, and the broadest set of add-in interop. For Mac users who need parity with their Windows colleagues, a VDI (virtual desktop infrastructure) is the established workaround.

This article compares the three realistic options and walks through the simplest setup.

Deploy Tenants via Registry

Mon, 01 Jan 0001 00:00:00 +0000

For admins & power users This is an IT admin / power-user task. It requires access to Windows group policy, deployment scripts, or software distribution tools (e.g., SCCM, Intune).

Instead of having each user manually enter tenant details, you can deploy tenant configuration directly to the Windows registry. This is the recommended approach for organizations with many users.

Registry locations

Choose one:

Location	Scope
`HKEY_LOCAL_MACHINE\Software\Adaptive Insights`	All users on the machine (preferred)
`HKEY_CURRENT_USER\Software\Adaptive Insights`	The current user only

Configuration file format

Create an XML configuration file with your tenant details:

System Admins

Mon, 01 Jan 0001 00:00:00 +0000

Workday OfficeConnect lives at the intersection of finance and IT. This section is for the people who deploy it, secure it, and keep it running well — whether your title says IT administrator or you’re the FP&A power user everyone turns to when something breaks.

Pick a sub-section:

Deploy — install across the organization, package for Intune/SCCM, and choose between per-user and per-machine.
Configure — tenant XML, single sign-on with Okta, Microsoft Entra ID, and Ping, plus proxy and firewall allowlists.
Govern — licenses, audit logging, secret rotation, tenant migration runbooks.
Upgrade — manage the forced-upgrade cadence, prepare users, and roll back when needed.

Articles in this section

Sub-sections

Configure — Configure Workday OfficeConnect tenants, single sign-on, multi-instance setups, and network access
Deploy — Install Workday OfficeConnect across the organization — silent install switches, Intune Win32 packaging, SCCM, GPO templates, and the per-user vs per-machine decision
Govern — Govern Workday OfficeConnect responsibly — secure workbooks, manage licenses, rotate secrets, capture audit trails, and run tenant migrations safely
Upgrade — Manage Workday OfficeConnect’s forced-upgrade cadence — version compatibility, user preparation, rollback paths, and multi-region migrations

Silent Install Workday OfficeConnect with Microsoft Intune (Win32 App)

Mon, 01 Jan 0001 00:00:00 +0000

For admins & power users This is an IT admin / power-user task. Requires Microsoft Intune admin access and the Microsoft Win32 Content Prep Tool.

Microsoft Intune deploys Workday OfficeConnect cleanly through its Win32 app model — silent install, mandatory assignment, automatic upgrade on new releases. This guide walks through packaging, uploading, and assigning the app.

For the SCCM/MECM equivalent, see Silent Install with SCCM/MECM. For tenant configuration after install, see Deploy Tenants via Registry.

Silent Install Workday OfficeConnect with SCCM / MECM

Mon, 01 Jan 0001 00:00:00 +0000

For admins & power users This is an IT admin / power-user task. Requires Microsoft Configuration Manager (the product formerly known as SCCM, now MECM) admin access and a working software distribution channel.

Microsoft Configuration Manager (MECM, formerly SCCM) is still the dominant on-prem software-deployment tool in many organizations. This guide packages Workday OfficeConnect as an Application in MECM, with silent install, supersedence-aware upgrade behavior, and reliable detection.