---
title: "Connect Microsoft Copilot to Workday: 3 routes — Kiweely"
description: "Three ways to connect Microsoft 365 Copilot or Copilot Studio to Workday, what each can read and change, how it signs in, and what it needs. Checked 17…"
url: https://kiweely.com/blog/microsoft-copilot-workday-connector-options
---

# How do I connect Microsoft 365 Copilot or Copilot Studio to Workday?

Copilot has three Workday routes: Workday’s Sana Self-Service Agent, Microsoft’s Employee Self-Service agent with the Workday pack, and the Copilot Studio Workday connector. Microsoft’s simplified set-up signs in as the employee, not an integration system user.

-   By Kiweely
-   November 17
-   9 min read

The short answer: there are three Microsoft-side routes, and they do different jobs. Workday’s Sana Self-Service Agent runs inside Microsoft 365 Copilot for employees and managers. Microsoft’s Employee Self-Service agent adds a Workday extension pack for employee details, contact changes and time off. The Power Platform Workday connector lets a maker build their own Copilot Studio actions. As of 17 November 2026, Microsoft’s simplified set-up for its own agent signs in as the employee through Microsoft Entra, with no integration system user.

None of the three connects Claude, ChatGPT or Gemini. That part is at the end.

## Which Copilot route should you use?

|  | Workday’s Sana Self-Service Agent in Copilot | Microsoft’s Employee Self-Service agent, Workday pack | Workday connector in Copilot Studio |
| --- | --- | --- | --- |
| Built by | Workday | Microsoft | Microsoft (connector), you (the agent) |
| Suits | Employees and managers asking about pay, time off, expenses, reviews | Employees asking about their own employee details | Makers who want specific Workday actions in their own agent |
| Reads | Yes | Employee details | Whatever you wire up: SOAP, reports, REST, preview actions |
| Changes | Yes, through Workday’s approvals | Phone, email, time off | Whatever you wire up |
| Signs in as | Workday’s own security applies | The signed-in employee, through Entra OAuth | Depends on the connection type you choose |
| Status | Generally available, 13 May 2026 (Workday) | Documented set-up, page updated 3 November 2026 | Connector available; several Workday actions are preview |

The first two are finished experiences. The third is a toolkit, and what it does depends on what you build.

## What does Workday’s Self-Service Agent do inside Microsoft 365 Copilot?

Workday’s release of 13 May 2026 says the Sana Self-Service Agent is generally available in Microsoft 365 Copilot “for eligible Workday and Microsoft customers”. It is one app in the Microsoft Marketplace. Copilot hands Workday questions to the agent, which does the work in Workday and returns the result.

Workday’s examples: employees check time-off balances, update personal information, view payslips, review tax withholding and request leave. Managers review team goals, approve timesheets in bulk, start a performance review and submit payroll input. Responses follow each organisation’s role-based permissions, and actions respect existing approvals and business rules. Workday says there is “no separate login, no new deployment, and no additional licensing requirement”.

Workday’s own pages add two limits. Its admin guide says Workday does not support notifications in Microsoft 365 Copilot, and that only an implementation or production instance of Copilot can connect to your tenant. [Workday’s guide](https://doc.workday.com/admin-guide/en-us/human-capital-management/hcm-innovation-services/workday-everywhere/concept--workday-everywhere-for-slack-and-teams-us.html) also tells admins to enable Self-Service Agent and its conversational skills in the tenant, so it is a configuration step in Workday, not nothing.

On cost, Workday’s pages do not agree on a single sentence. The May release says no additional licensing requirement. Workday’s Flex Credits rate card, last updated 5 November 2026, lists Self-Service Agent requests at 1 credit for a read (“pull Workday-hosted data”) and 5 credits for a write, per request. Neither page says how the two fit together. Ask Workday which applies to your agreement before you plan a budget.

This route suits a company that has Microsoft 365 Copilot and wants employees to handle everyday HR and finance requests there with the least set-up. It stops at the skills Workday has built for the agent; Workday’s release does not mention your own reports or custom queries.

## What does Microsoft’s Employee Self-Service agent do with the Workday pack?

Microsoft’s Employee Self-Service agent is built on Copilot and Copilot Studio. Workday is added as an extension pack under Settings, then Customize. Microsoft’s setup page documents these scenarios: reading employee data (base compensation, company code, cost centre, service anniversary, employment information, emergency contacts, national IDs, passports, visas, languages and certifications), updating a phone number or email address, and requesting time off. The page says the integration is “currently configured to retrieve only Employee details” and does not work for external staff or non-employees.

### Does it need an integration system user?

No, in the simplified set-up. Microsoft’s page says the agent “connects to Workday using the signed-in user’s identity through a single OAuth connection”. It adds: “SOAP calls don’t require integration system users (ISUs) in the simplified Employee Self-Service Workday integration. Both SOAP and REST calls run as the signed-in user through the same OAuth connection.” The REST call `/workers/me` finds who the user is once per session, which replaces the Reports as a Service (RaaS) report the older set-up used.

Microsoft is careful about scope. It says the sentence applies to this integration, “not to every Workday integration”, and that the older set-up, with an integration system user and a RaaS report, still works. So an answer that says Copilot’s Workday access depends on an integration system user is describing the legacy set-up, or a different Microsoft Workday feature.

### What does the Workday admin do?

Microsoft’s page lists the work:

-   Workday must sign in through Microsoft Entra, either directly or through a third-party identity provider federated with Entra. Basic authentication is not supported, including for pilots.
-   A Workday admin registers an API client with at least four functional areas: Core Payroll, Organizations and Roles, Staffing, and Time Off and Leave, with “Include Workday Owned Scope” set to Yes.
-   The admin grants domain security to the employees’ security group. Microsoft starts with Worker Data: Public Worker Reports and says the API scopes do not replace domain security. If someone gets “Task not authorized”, the fix is a Workday security change for that domain, not a Copilot setting.
-   IT allowlists the Power Platform IP ranges for Workday’s REST and SOAP endpoints.
-   The REST base URL on the connection is mandatory. Without it, Microsoft says, the simplified flow “fails silently and the agent falls back to the legacy ISU-based” RaaS path.

On licensing, Microsoft’s [prerequisites page](https://learn.microsoft.com/en-us/microsoft-365/copilot/employee-self-service/prerequisites) says users need Microsoft Copilot licensing and makers and admins need Copilot Studio and Copilot licensing. The agent “includes the Workday, SAP SuccessFactors, and ServiceNow premium connectors at no additional cost”, and you still need the right licences for the third-party systems. Users without a Copilot licence can be billed pay-as-you-go.

This route suits a company that already runs the Employee Self-Service agent for HR and IT and wants Workday in it. It stops at employee details and the scenarios above; extra topics are yours to build.

## What can the Workday connector in Copilot Studio do?

Microsoft’s Workday connector (publisher Microsoft) is a building block for makers. It is Premium in Copilot Studio, Power Apps and Power Automate and Standard in Logic Apps, and is not available in US Government (GCC and GCC High), Department of Defense or China cloud regions. Microsoft lists a throttle of 200 API calls per connection per 60 seconds.

Connection types are Microsoft Entra ID Integrated, OAuth 2.0, Basic and Entra ID through API Management. The actions on Microsoft’s page:

-   Execute SOAP operation, Execute RaaS operation, Execute REST request (preview), Execute REST request in JSON (preview), and Execute SOAP operation with JSON extraction (preview).
-   Preview actions for common tasks: get my worker profile, search workers, get worker direct reports, get inbox tasks, get pay slips, get supervisory organizations managed by a worker, get feedback templates, request feedback on a worker, and transfer employee, which starts a job change.

Microsoft says the REST action runs “using the signed-in user’s OAuth credentials” and that Workday enforces that user’s permissions. For writes through the JSON REST action, it says not to retry automatically and that callers are responsible for retry handling and idempotency. That is a real design task if you let an agent change data.

Microsoft also lists a separate “Workday HCM (Preview)” connector. It takes a Workday endpoint, user name and password, with a throttle of 1,800 calls per connection per 60 seconds. Its actions add or update address, email, instant messenger, phone and web address, read employment, identity, personal and qualification information, run a generic SOAP operation, and trigger when an employee is added or updated.

This route suits a team with Power Platform skills that needs one specific action the other two routes do not cover. It stops at what you build and test. There is no packaged agent, approval step or audit view; those are yours.

## Can Copilot Studio use Workday’s Agent-Ready Tools?

Workday’s admin guide for connecting an external agent over MCP says any platform that supports MCP, “Google Agentspace, Amazon Bedrock AgentCore, Microsoft Copilot Studio, and others”, connects to the same endpoint with the same OAuth credentials. The guide’s walk-through uses an authorize call with a sign-in, then a token exchange. It states that access tokens expire after 4 hours and refresh tokens after 30 days.

The same page says “This functionality is for Extend Professionals only”, and lists the set-up: Agent System of Record, discovering the tools, registering and configuring the external agent, and security policies for agent skills. Workday’s release of 13 October 2026 says Agent-Ready Tools are “generally available in Workday Extend AI”. Those two statements sit on different Workday pages, and neither page reconciles them. Workday’s rate card prices Agent-Ready tool calls for non-custom agents at 10 Flex Credits per 100 base calls and 50 per 100 advanced calls.

Separately, Workday documents Microsoft Agent Sync. It synchronises agents built in Copilot Studio and Azure AI Foundry into Workday’s Agent System of Record, which is a governance record of which agents exist. It needs a Microsoft Global Administrator to grant consent and a set of Workday Agent System of Record permissions. It registers the agents; it does not by itself give an agent access to Workday data.

## Is there a Microsoft Graph (Copilot) connector for Workday?

Partly, and it is not the one people usually want. Microsoft’s Microsoft-built connectors gallery, updated 16 November 2026, lists a Workday entry described as synchronising organization data “via Microsoft 365 Organizational Data Service”. Microsoft’s guide for it imports organizational data from the Workday SOAP API, for up to 100,000 users, into Microsoft 365. That guide has the Workday admin create an integration system user and an API client, with a weekly or monthly refresh. The data feeds apps such as Viva Insights, the Copilot Dashboard and Viva Glint.

So it brings your org chart into Microsoft 365. It does not let Copilot ask Workday a person’s own live question under that person’s security. Microsoft’s partner-built connectors page lists no Workday entry as of 17 November 2026.

## What if your company also uses Claude, ChatGPT or Gemini?

All three Microsoft routes serve Copilot. Workday’s own pages say Sana Self-Service Agent also reaches Gemini Enterprise, Teams and Slack, and Workday’s “Sana from Workday” connector is in Claude’s directory, where Claude’s page calls it a Beta service and says Workday admins apply for access. We found no Workday app for ChatGPT as of 17 November 2026. See [every option compared](https://kiweely.com/blog/claude-chatgpt-gemini-workday-options-compared) for those, with dates.

Most companies with Copilot rolled out to the Microsoft 365 population and Claude, ChatGPT or Gemini elsewhere will end up with two layers: one of the Copilot routes above for the Copilot users, and one connector that works for the other assistants. The question for the second layer is the same as for Copilot: who is signed in to Workday, and what can the connector change. Microsoft’s simplified route answers that by using the employee’s own identity, and a connector for the other assistants should answer it the same way. [Four gates](https://kiweely.com/blog/secure-workday-mcp-server-four-gates) walks through where each check happens.

Kiweely Bridge is coming next for that second layer. As described on [its page](https://kiweely.com/bridge), it puts Workday inside Claude, ChatGPT and Gemini, each person signs in as themselves on Workday’s own sign-in screen, and every change waits for a browser card showing the value now and after. It is not available yet; you can [register interest](https://kiweely.com/bridge#interest). Planned pricing is $499 a month per company up to 1,000 employees, $1,499 up to 5,000 and $3,999 up to 20,000, with Enterprise by quote. Its page names Claude, ChatGPT and Gemini, not Copilot, so for Copilot users the routes above are the ones to use.

## Frequently asked questions

### Does Microsoft Copilot need an integration system user to read Workday?

Not in Microsoft's simplified set-up for the Employee Self-Service agent. Microsoft's set-up page, last updated 3 November 2026, says the agent uses one OAuth connection as the signed-in user, and that SOAP calls do not need integration system users in that set-up. The older set-up, which uses an integration system user and a Reports as a Service report, still works, and Microsoft says existing configurations continue to run.

### Is there a Microsoft 365 Copilot (Graph) connector for Workday?

There is a Workday entry in Microsoft's Microsoft-built connectors gallery, but it imports organizational data into the Microsoft 365 Organizational Data Service (for Viva and Copilot Dashboard, for example). Microsoft's guide for it sets up an integration system user. It is not a way for Copilot to answer a person's own Workday questions live.

### Can Copilot Studio call Workday's own Agent-Ready Tools?

Workday's admin guide says any platform that supports MCP, Microsoft Copilot Studio among them, can connect to Workday's MCP endpoint with the same OAuth credentials. The same page says the feature is for Extend Professionals only, so check your Workday agreement first.

### How much does the Workday connector in Copilot Studio cost?

Microsoft lists the Workday connector as Premium in Copilot Studio, Power Apps and Power Automate. For the Employee Self-Service agent, Microsoft says the Workday premium connector is included at no additional cost, and you still need the right Workday licences.

## Read next

[All posts](https://kiweely.com/blog)

-   [November 17 ### Will AI Replace Workday Consultants? No. The Agent Works for You](https://kiweely.com/blog/will-ai-replace-workday-consultants)
-   [November 17 ### ServiceNow AI agents vs Workday AI agents: operations vs HCM/finance build](https://kiweely.com/blog/servicenow-ai-agents-vs-workday-ai-agents)
-   [November 17 ### How Workday prospects should run an AI-agent-driven implementation methodology](https://kiweely.com/blog/workday-prospect-ai-agent-implementation-methodology)

### More guides on Custom agents and Workday AI

[All 91 guides](https://kiweely.com/guides#custom-agents)

-   [Why Custom Agent Actions Fail With S22 Permission Denied or Task Not Authorized in Agent Chat](https://kiweely.com/guides/workday-custom-agent-actions-permission-denied-tool-wids)
-   [Fixing invalid\_request OAuth Token Exchange Errors When Connecting Microsoft Copilot Studio to Workday A2A](https://kiweely.com/guides/workday-a2a-copilot-studio-oauth-invalid-request)
-   [Why Custom Agent Skills Deployed From the Developer Site Don’t Appear in Agent Management Hub, and ASOR Tenant Prerequisites](https://kiweely.com/guides/workday-agent-management-hub-skills-not-showing)
-   [Fixing Workday Developer Agent VS Code Sign-In With a Personal Developer Account and Subagent Interrupt Errors](https://kiweely.com/guides/workday-developer-agent-vscode-personal-account-login)
-   [Finding Workday tool IDs with the Agent Resource Search (finder) API](https://kiweely.com/guides/workday-finder-api-tool-discovery)
-   [Connecting an Extend app to the Workday Self-Service Agent and Microsoft Teams](https://kiweely.com/guides/workday-extend-self-service-agent-teams)
-   [How to build a chatbot in Workday Extend](https://kiweely.com/guides/workday-extend-chatbot)
-   [How to call AI Gateway Document Intelligence from a Workday Extend app](https://kiweely.com/guides/workday-extend-ai-gateway-document-intelligence)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
