Configure on OfficeConnectPro

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.

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.

Set Up Workday SSO

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

For admins & power users This page requires Workday Security Administrator access. End users don’t need to do anything — SSO is configured at the tenant level by admins and power users.

What Workday SSO does for OfficeConnect

With SSO enabled, users sign in to Workday OfficeConnect using their existing Workday credentials through your identity provider. They don’t need a separate Adaptive Planning username and password.

For identity-provider-specific guides, see SSO with Okta, SSO with Microsoft Entra ID, or SSO with Ping Identity (coming soon under Admin → Configure).

Single Sign-On for Workday OfficeConnect with Okta

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

For admins & power users Requires Okta administrator access and Workday Security Administrator access. End users don’t change anything on their side; this is a tenant-level configuration.

Workday OfficeConnect doesn’t authenticate to Okta directly. Instead, OfficeConnect authenticates to Workday, and Workday uses Okta as its identity provider. This indirection is important — the configuration lives on the Workday side, not directly in OfficeConnect — and explains why many SSO problems surface as Workday auth failures rather than Okta errors.

Single Sign-On for Workday OfficeConnect with Microsoft Entra ID

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

For admins & power users Requires Entra ID Application Administrator (or higher) and Workday Security Administrator access. End users don’t change anything; this is a tenant-level configuration.

Workday OfficeConnect doesn’t authenticate to Microsoft Entra ID directly. OfficeConnect authenticates to Workday, and Workday uses Entra ID as its identity provider. The configuration sits on the Workday side, with Entra ID providing the SAML or OIDC backbone.

This guide assumes Entra ID-to-Workday SSO is already working for the Workday web app. If not, do that integration first (Entra’s enterprise app gallery has a “Workday” SAML template).

Refresh Reports Automatically with Power Automate

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

Workday OfficeConnect doesn’t have a built-in scheduler, but you can automate report refresh using Power Automate Desktop — Microsoft’s desktop automation tool included with Windows 10/11 and Microsoft 365. This how-to sets up a scheduled desktop flow that opens your report workbook, refreshes OfficeConnect data, saves, and closes — on any schedule you set.

What you’ll need:

Windows 10 or 11 with Power Automate Desktop installed (download from Microsoft)
Microsoft 365 subscription (Power Automate Desktop is included)
Your Workday OfficeConnect report workbook saved to a local path or a network/SharePoint location accessible from the machine

For admins & power users The machine running the flow must be on and signed in for the scheduled flow to run. This approach works best on a server or shared workstation that stays online. For cloud-only approaches, consider saving the refreshed file to SharePoint so downstream users always see the latest version.

1. Create the desktop flow

Open Power Automate Desktop from the Start menu.
Click + New flow, give it a name like Refresh OfficeConnect Monthly Report, and click Create.
The flow designer opens. You will build the flow by adding actions from the left panel.

2. Add actions to open, refresh, save, and close the workbook

In the Actions panel, search for Launch Excel and drag it into the flow. Set: