JR-0111465 (Developer Platform FDE, fetched 2026-11-18) says agents “can show up in Workday, in Sana, or inside the AI tools people already use every day.” Workday’s public admin and blog pages name those AI tools for Self-Service Agent and related paths: Microsoft 365 Copilot, Microsoft Teams, Slack, and Gemini Enterprise.
This is a surface map for scoping rollouts—not the admin setup sequence for Sana Self-Service Agent.
Surface map
| Surface | What Workday publishes |
|---|---|
| SurfaceWorkday (Self-Service Agent chat / in-product) | What Workday publishesCustom Agents overview: after ASOR activation, Custom Agents appear in the Self-Service Agent chat panel; first-party SSA is the in-Workday conversational path |
| SurfaceSana | What Workday publishesJR-0111465 + Custom Agents blog / build guide: available in Sana; paths-to-build Path 3 is the AI-native Sana workspace |
| SurfaceMicrosoft 365 Copilot | What Workday publishesWorkday Everywhere concept; Sana in Copilot blog; paths-to-build Path 2 |
| SurfaceMicrosoft Teams | What Workday publishesEverywhere concept; Sana-in-Copilot blog (SSA in Teams available today) |
| SurfaceSlack | What Workday publishesEverywhere concept (self-service via Slack) |
| SurfaceGemini Enterprise | What Workday publishesEverywhere concept; paths-to-build |
| SurfaceExternal A2A clients | What Workday publishesDeveloper A2A docs + Custom Agents blog (open standards including A2A) |
Workday Everywhere using Self-Service Agent
Workday’s concept Workday Everywhere Using Sana Self-Service Agent states workers can 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. Security matches Workday access. Notifications can land in Teams and Slack; Workday does not support Everywhere notifications in Microsoft 365 Copilot.
Blog nuance: Copilot vs every Sana agent
Workday’s Rising EMEA Sana / Copilot blog separates lines:
- Sana Self-Service Agent in Teams and Copilot: available today
- Sana plugin for Copilot: early access; GA expected early 2027
- Sana Lead Agent in Teams/Copilot: early next year
Do not treat “Self-Service Agent in Copilot” as “every Sana agent in Copilot.”
Path 2 vs Path 3
Building Agents on Workday’s Guardrails keeps Path 2 as Copilot/Gemini (or similar) front doors with agents running on Workday, and Path 3 as the full Sana workspace when a single prompt is not enough.
Custom Agents on the same fabric
The Custom Agents announcement says Custom Agents built on open standards including A2A can show up in Workday, Sana, Gemini Enterprise, or Claude—still running inside Workday guardrails.
Steering question
Pick the week-one system of engagement—Workday chat, Teams, Copilot, Slack, Gemini, or Sana workspace—then align ASOR Available To and Everywhere ownership to that surface. Agent logic can be shared; adoption cannot pretend every surface is live for every skill.