Workday integrates Sana Self-Service Agent into Microsoft 365 Copilot

Workday announced on May 13, 2026 that the Sana Self-Service Agent is now available in Microsoft 365 Copilot, enabling employees and managers to query HR and finance information and invoke actions directly inside Microsoft 365, per Workday's newsroom release and a PR Newswire distribution. The company describes examples including checking vacation balances and requesting time off, checking expense status, seeing steps for a performance review, and looking up policies such as family leave. Per Workday, when a request requires Workday data or processes, Microsoft 365 Copilot securely connects to the Self-Service Agent, which completes the task in Workday under the organization's existing approvals, policies, and business rules and then returns the result in Copilot. The press materials include a direct quote from Joel Hellermark, Sana general manager: "People shouldn't have to jump between systems just to get a simple HR or finance answer."

Companies integrating enterprise systems into Copilot-class assistants commonly use authenticated connectors, tokenized API calls, and policy-enforcement layers to ensure data residency and authorization controls. Industry-pattern observations: surface integrations typically map natural-language intents to canonical API endpoints, apply business-rule checks server-side, and return formatted responses to the assistant layer. For practitioners, that pattern implies priorities around access controls, auditability, latency, and error-handling when mapping conversational intents to transactional systems.

Industry context: Embedding HR and finance automation into productivity tools reduces context switching for end users and can shift routine transactional volume away from HR service desks. For platform engineers and SRE teams, enabling conversational self-service amplifies the need for robust observability, rollback paths for automated actions, and fine-grained authorization auditing. For security and compliance teams, the relevant tradeoffs center on how identity, consent, and approval workflows are preserved when an assistant initiates workday transactions from a third-party UI.

• •Adoption metrics and supported enterprise controls: whether organizations can enforce custom approval flows and policy exceptions via the integration.
• •Audit and logging capabilities: availability of end-to-end logs tying Copilot prompts to Workday transactions.
• •Scope of supported actions: initial demo items (time off, expenses, policy lookup) versus later support for compensation, org changes, or payroll-affecting tasks.
• •Third-party certifications or Microsoft validation for the connector and any compliance attestations.

This release is primarily a product integration announcement from Workday; no additional roadmap details or customer case studies appeared in the cited press materials.