If you are scoping an agent rollout, start with the surface, not the model. Workday’s public pages describe a small set of places employees actually meet agents: the in-Workday Self-Service Agent experience, Sana as an AI-native workspace, and Workday Everywhere conversational entry points in Microsoft 365 Copilot, Microsoft Teams, Slack, and Gemini Enterprise. Custom Agents, once activated in Agent System of Record, show up on that same fabric—including Sana—and can be reached over Agent-to-Agent (A2A).
This post is a surface map for forward-deployed and implementer teams. It is deliberately complementary to the admin setup guide for Sana Self-Service Agent: that guide covers tenant security before you turn the agent on; this one covers where the conversation appears once it is on.
Surface map (what Workday publishes)
| Surface | What employees do there | What Workday cites |
|---|---|---|
| SurfaceSelf-Service Agent chat panel (in Workday) | What employees do thereConversational HR/finance self-service; Custom Agents after ASOR activation | What Workday citesCustom Agents overview; SSA concept |
| SurfaceSana from Workday | What employees do thereAI-native workspace for multi-step decisions; agents underneath | What Workday cites“Building Agents on Workday’s Guardrails”; Custom Agents “available in Sana” |
| SurfaceMicrosoft 365 Copilot | What employees do thereAsk HR/finance questions and complete tasks without leaving Microsoft 365 | What Workday citesNewsroom (13 May 2026); Workday Everywhere concept; Sana-in-Copilot blog |
| SurfaceMicrosoft Teams | What employees do thereSame Everywhere conversational skills; notifications supported | What Workday citesWorkday Everywhere concept |
| SurfaceSlack | What employees do thereSame Everywhere conversational skills; notifications supported | What Workday citesWorkday Everywhere concept |
| SurfaceGemini Enterprise | What employees do thereEverywhere / Path-2 style access to Self-Service Agent | What Workday citesWorkday Everywhere concept; paths-to-build blog |
| SurfaceExternal A2A clients | What employees do thereDiscover/call Workday or Custom Agents on behalf of a user | What Workday citesDeveloper A2A guides |
Workday Everywhere using Self-Service Agent
Workday’s administrator concept Workday Everywhere Using Sana Self-Service Agent (updated 21 August 2026) states that Everywhere lets workers perform self-service tasks from Gemini Enterprise, Microsoft 365 Copilot, Microsoft Teams, or Slack, delivered with Self-Service Agent. Workday recommends enabling Self-Service Agent and its conversational skills in the tenant.
Documented Self-Service Agent capability themes include:
- Workforce lifecycle, benefits, and worker profiles
- Support requests
- Specific reports and tasks
- Compensation, payments, and tax forms
- Policy answers from knowledge base articles
- Performance reviews, goals, and internal job searches
- Time, absence, and team schedules
Security is the same as Workday: managers see team performance reviews; workers see their own. You connect an implementation or production instance of those collaboration tools. Contingent workers can use Everywhere when granted access, but they cannot set it up for the organization. Notifications can land in Teams and Slack; Workday does not support Everywhere notifications in Microsoft 365 Copilot.
Copilot and Sana timing (read the fine print)
Workday’s May 2026 newsroom piece: Sana Self-Service Agent is available in Microsoft 365 Copilot so employees can, for example, check vacation and request time off, check expense status, prepare for a review, or look up policies—while approvals and role-based permissions stay in Workday.
Workday’s Rising EMEA blog on Sana in Copilot adds availability nuance:
- Sana Self-Service Agent in Microsoft Teams and Microsoft Copilot: available today
- Sana plugin for Copilot: early access, with general availability expected in early 2027
- Sana Lead Agent in Teams and Copilot: early next year
Do not collapse “Self-Service Agent in Copilot” with “every Sana agent in Copilot.” They are different availability lines on Workday’s own page.
Sana as a workspace, not only a chat plugin
In Building Agents on Workday’s Guardrails, Workday describes three paths. Path 2 keeps the employee in Copilot or Gemini while reasoning stays on Workday. Path 3 is Sana itself when the problem is too multi-dimensional for a single prompt—budgets, PTO, calendar, expenses in one workspace—with agents such as the Sana Travel Agent example running underneath. Sana from Workday and the Sana Self-Service Agent are described there as available to Workday customers today.
Where Custom Agents land
Workday’s Custom Agents overview is explicit: after ASOR configuration and activation, users can access a Custom Agent from the Self-Service Agent chat panel, in Sana, through the business process framework, over A2A, or through Workday’s agent tool protocol. Custom Agents are Delegate mode only. The build guide’s result section adds that a deployed Custom Agent is automatically A2A-ready and available in Sana.
That is the pairing rule for FDEs: first-party Self-Service Agent skills and your Custom Agent share ASOR and can share surfaces—but only after Activate, and only for users in the Available To groups you set.
What this post does not claim
- It does not replace the admin prerequisites on Set Up Self-Service Agent or ASOR domain setup.
- It does not invent mobile-only or inbox-only surfaces Workday did not name on the pages above.
- It does not treat newsroom roadmap wording as a tenant toggle you can click today without checking the matching admin guide for your release.
Practical cutover question for the steering group
Ask one question before you fund training: Which surface is the system of engagement for week one—Workday chat, Teams, Copilot, Slack, Gemini, or Sana workspace? Then align ASOR Available To, Everywhere admin ownership (Manage: Innovation Services), and Flex Credits monitoring to that surface. The agent logic can be shared; the adoption plan cannot pretend every surface is already live for every skill.
Sources checked for this session include Workday’s Workday Everywhere concept, Custom Agents developer overview, the Sana-in-Copilot blog, the May 2026 Copilot newsroom release, and Workday’s three-paths developer blog.