A professional uses a laptop as glowing AI-powered collaboration and workflow dashboards appear around her.
Workday wants its HR and finance agents to work wherever your employees already chat, and that now includes Microsoft Copilot and Teams. Workday said at Rising 2026 that Sana, its agentic experience and orchestration engine, will work inside Claude, Google Cloud's Gemini Enterprise, Microsoft Copilot and Teams, and Slack. The announcement builds on self-service features that are already live.

For Microsoft 365 administrators, the key point is the change in what Copilot and Teams are used for. They have been places to ask questions. Workday wants them to become places where HR and finance tasks get done.

A professional uses a laptop as glowing AI-powered collaboration and workflow dashboards appear around her. What Workday announced​

Workday's pitch is that employees ask for an outcome in plain language. Sana then checks the company's policies, permissions and approvals, and brings in the right Workday agents to do the work. The employee doesn't need to know which agent handles what.

The release gives two examples:

  • Planning in Copilot. A business leader asks Sana inside Microsoft Copilot to model a planning decision. Sana checks permissions, compares options using company data, and saves the chosen plan to Workday with an audit trail. If approval is needed, Sana gathers the context first and gives the manager a recommendation.
  • Expenses in Claude. After a business trip, Sana can flag an unfiled expense in Claude, apply company policy and prepare the expense report for review. The employee then confirms it from the conversation. The wording says "prepare for review". It does not say Sana submits or approves the report on its own.

Both are vendor scenarios, not tested results. The planning example is a good illustration of the target, but it isn't evidence that the workflow works in Copilot today (see the availability section below).

What is available now and what isn't​

Workday's release separates what exists today from what is planned. The two tiers are easy to blur together.

ItemStatus per Workday
Sana self-service in Gemini Enterprise, Microsoft Copilot, Microsoft Teams, SlackGenerally available
Broader Sana experience on those platformsLate 2026
Sana in Claude CoworkEarly access today
Sana in Copilot CoworkEarly access expected late 2026

The release is explicit about the risk. It says unreleased features may change or may not ship as planned, and it tells customers to base purchase decisions on what is available now.

Don't treat Copilot Cowork early access as the same thing as the existing Microsoft 365 Copilot self-service agent. They are listed separately, and only the second is described as available.

The Microsoft 365 Copilot groundwork​

This isn't Workday's first move into Copilot. In May, Workday announced that its Sana Self-Service Agent was available in Microsoft 365 Copilot. That release described several everyday tasks:

  • Employees can check time-off balances, update personal information, view payslips, review tax withholding information, or request leave.
  • Managers can review team goals, approve timesheets in bulk, start a performance review, or submit payroll input.

On deployment, Workday said that for organizations already using Microsoft 365 Copilot, turning on the agent is a configuration step. It is a single app in the Microsoft Marketplace, with no separate login, no new deployment and no additional licensing requirement. Those details come from the May announcement. The October release doesn't repeat them or say whether they apply to the new agentic features. Check licensing for the later tier with Workday and Microsoft.

How Workday says the governance works​

For IT and security teams, this is the part to examine most closely. Third-party platforms do not receive direct access to Workday data. Sana mediates access and applies company-specific permissions and policies before completing tasks. Workday's phrasing is that actions are "lawful by design". That is a marketing characterization. It is not a legal conclusion that anyone has verified.

The release also describes a single-connection model. One connection brings Workday agents into the supported platforms, and new capabilities appear across connected tools without extra integration work. It says agents built by Workday, customers or partners can be included. If that holds up, it would save admins from wiring every chat tool to every agent individually.

Long-running work​

Some processes are too big for one chat exchange. Workday names open enrollment, performance reviews, quarter-end close and workforce planning. For those, Sana offers a home experience where people can see progress and pick up where they left off. Work can start in another tool, move into Sana when a richer view is needed, and return to the employee's usual workflow with context intact.

The release gives no screenshots, workflow limits or explanation of how context carries over.

What admins should ask before piloting​

The release leaves several gaps. Raise them with Workday and Microsoft before any rollout:

  1. Tenant eligibility and licensing. The release names no supported Copilot or Teams editions and no prerequisites.
  2. Data handling. It doesn't say which data fields reach each external AI service, or how long they are retained.
  3. Audit behavior. It promises a "full audit trail" but doesn't explain how the log works or where it lives.
  4. Approval boundaries. Test which actions are prepared for review and which can execute. The expense example stops at review.
  5. Rollout timing. "Late 2026" is the only date given for the broader experience. It states no schedule by customer or region.
  6. Claude Cowork early access. The release doesn't say whether the offer has customer, geography or tenant limits.

A May WindowsForum analysis made a related recommendation for the earlier agent. It advised teams to pilot against real policy edge cases before broad deployment. That advice still applies, and it matters more once agents can act and not just answer.

Analysis​

This is a sensible direction, and a risky one. Putting HR and finance actions inside Copilot and Teams removes friction, and employees will use the tools they already have open. The same convenience adds more places where permissions, prompt behavior and data exposure have to be right. A wrong tax withholding answer in a chat window is still a compliance problem.

Workday also supports Claude, Gemini and Slack alongside Microsoft's tools. That cuts both ways. It avoids tying customers to one ecosystem, but it means IT teams must govern a multi-vendor AI surface instead of one Microsoft tenant.

Treat the claims as claims for now. Workday says it serves Claude, Gemini Enterprise, Microsoft Copilot, Teams and Slack through one connection, and no independent implementation or security test results have been published. Until those exist, pilot narrowly, log everything and keep HR and finance owners in the loop.

 

References

  1. Workday to Bring Sana Everywhere Employees Work, Including Claude, Gemini Enterprise, Microsoft Copilot, Slack, and Teams - HRTech Series HRTech Series 2026-10-13T15:02:26+00:00
  2. Workday to Bring Sana Everywhere Employees Work, Including Claude, Gemini Enterprise, Microsoft Copilot, Slack, and Teams - Oct 13, 2026 en-sg.newsroom.workday.com
  3. Workday to Bring Sana Everywhere Employees Work, Including Claude, Gemini Enterprise, Microsoft Copilot, Slack, and Teams - Oct 13, 2026 newsroom.workday.com