The short answer: each assistant reaches Workday by a different route. Microsoft 365 Copilot and Gemini Enterprise have Workday’s own Self-Service Agent, generally available. Claude has Workday’s Sana connector in early access. ChatGPT has no Workday-built app. A company where people use more than one of these either runs a route per assistant, each with its own set-up and policy, or puts one connector in front of Workday that every assistant uses, with each person signed in as themselves.
This page was rewritten on 17 November 2026. An earlier version described Microsoft Agent Sync as Copilot’s way into Workday data; it is not, as the table below says.
What does each assistant have today?
| Assistant | Workday’s own route | Other routes | Status, 17 Nov 2026 |
|---|---|---|---|
| AssistantMicrosoft 365 Copilot | Workday’s own routeSana Self-Service Agent, one app in the Microsoft Marketplace | Other routesMicrosoft’s Employee Self-Service agent with its Workday pack; the Power Platform Workday connector in Copilot Studio | Status, 17 Nov 2026Workday’s agent GA since 13 May 2026 for eligible customers |
| AssistantGemini Enterprise | Workday’s own routeSana Self-Service Agent, through a Google Cloud Marketplace private offer | Other routesCustom MCP Server data store (public preview) | Status, 17 Nov 2026Early access on 28 May 2026; “generally available today” in Workday’s 13 October release |
| AssistantClaude | Workday’s own routeSana from Workday connector | Other routesAny MCP server as a custom connector, including Workday’s Agent-Ready Tools | Status, 17 Nov 2026Beta in Claude’s directory; early access, GA expected late 2026 (Workday) |
| AssistantChatGPT | Workday’s own routeNone found | Other routesAny MCP server as a custom plugin, including Workday’s Agent-Ready Tools | Status, 17 Nov 2026No Workday app found |
Microsoft Agent Sync, which an earlier version of this page put in the Copilot row, synchronises agents built in Copilot Studio and Azure AI Foundry into Workday’s Agent System of Record. It registers and governs those agents in Workday; it does not by itself give Copilot access to anyone’s Workday data. For the three Copilot routes that do, see Microsoft Copilot and Workday.
What does running a route per assistant cost you?
Each Workday-built route is a separate set-up with its own prerequisites. Workday’s own agents need its AI subscription terms and Flex Credits: on Workday’s rate card (updated 5 November 2026) each self-service read is 1 credit and each write 5. Sana in Claude needs an active Workday UMSA, the agents set up in Agent Management Hub and an approved access request. Microsoft’s Workday pack needs its own Entra sign-in set-up and an API client with the functional areas Microsoft lists. ChatGPT needs a custom MCP server from somewhere.
The skills also differ. Workday’s agent is employee and manager self-service; Microsoft’s pack reads employee details and changes phone, email and time off; a custom MCP server does whatever its tools do. Employees on different assistants can get different answers to the same question, and the security team reviews each route separately.
That is fine for a company whose people sit in one assistant. It gets harder with every assistant added.
What does one connector for every assistant need?
Claude, ChatGPT and Gemini Enterprise all accept remote MCP servers, so one server can serve all three. For that to be safe, it needs the same things any Workday MCP server needs, set once:
- Each person signed in as themselves, through a Workday API client with the authorization code grant, so every call runs under their own security groups and domains. No integration system user shared by everyone.
- One tool list for every assistant, each tool marked read or change, with the same fields left out everywhere.
- Every change confirmed outside the chat. The assistants confirm writes differently, and a confirmation inside a conversation can be answered by the conversation.
- One place to switch it off: the Workday API client every token comes from.
How to secure a Workday MCP server walks through each of these.
Copilot users are a separate case: Microsoft’s routes above are the way to reach them, and Microsoft’s simplified Workday set-up already signs in as each employee (Microsoft).
Where does Kiweely Bridge fit?
Kiweely Bridge is coming next. It is built for the case above: Workday inside Claude, ChatGPT and Gemini, for everyone, on any standard tenant with no Workday AI agreement. Each person signs in as themselves on Workday’s own sign-in screen. It is read-only by default; admins turn changes on one by one, and every change waits for a browser card showing now and after. Nothing is stored. It is priced per company, by size: $499 a month up to 1,000 employees, $1,499 up to 5,000 and $3,999 up to 20,000. You can register interest.
For every route side by side, with dates and sources, see Claude, ChatGPT and Gemini with Workday: every option compared.
Frequently asked questions
Does Workday's own Sana cover Copilot, Gemini, Claude and ChatGPT equally?
No. Workday's 13 October 2026 release says self-service Sana is generally available in Gemini Enterprise, Microsoft Copilot, Teams and Slack, and in early access in Claude. It names no ChatGPT app, and we found none as of 17 November 2026.
Is Microsoft Agent Sync a way for Copilot to read Workday data?
No. Workday's guide describes Agent Sync as synchronising agents built in Copilot Studio and Azure AI Foundry into Workday's Agent System of Record, so they are registered and governed there. Reading Workday data from Copilot goes through Workday's Self-Service Agent, Microsoft's Employee Self-Service Workday pack or a connector.