On May 13, Workday moved a routine HR request into a place many employees already had open.

An employee using Microsoft 365 Copilot could ask how much vacation was left, request time off, check a payslip, update personal information, review tax withholding, look up a family-leave policy, or ask about an expense. The answer did not require opening Workday in another tab. Copilot became the surface. Workday stayed the system that knew the policy, checked the permission, ran the approval and wrote the transaction.

That was the point of Workday’s announcement that the Sana Self-Service Agent is now available in Microsoft 365 Copilot. Workday said employees and managers could complete everyday HR and finance tasks inside Microsoft 365 while organizations kept existing Workday security, compliance, policies and business rules. It also said eligible customers could turn on the app through Microsoft Marketplace without a separate login, a new deployment or an additional licensing requirement.

For an employee, that sounds like convenience.

For HR technology vendors, it is a fight over distribution.

Employee service has always suffered from a simple defect: the person with the question rarely wants to visit the place where the answer lives. A manager wants to approve a timesheet while reading email. A frontline supervisor wants to start onboarding from the same chat surface used to coordinate shifts. An employee wants a payroll answer without learning whether the case belongs to HR, finance, payroll, IT or a shared-service queue. The portal may be the system of record for the company. It is not the natural starting point for the worker.

AI agents turn that old inconvenience into a market shift. If the employee can begin in Copilot, Gemini Enterprise, Slack, Teams, ServiceNow, a mobile frontline app, or a payroll chat, the value of the HR portal changes. It still matters. It may matter more for policy, permissions, approvals and evidence. But the front door moves closer to the tools where work already happens.

Workday is not alone. ServiceNow is pushing EmployeeWorks through Moveworks as a conversational front door available in Teams, Slack and browser surfaces. UKG is putting People Assist into Google Cloud’s Gemini Enterprise Agent Gallery. SAP is describing Joule Assistants for payroll, recruiting, onboarding, HR service and workforce upskilling. Oracle is placing agentic HR applications inside Fusion Cloud HCM. ADP is building Assist agents for payroll variance, policy questions, talent actions and workforce analytics.

The vendors are doing more than making HR chatbots better. They are trying to decide where an employee request starts, which platform gets credit for resolving it, which license absorbs the cost, which system retains the audit trail and which vendor can claim the renewal story.

May 13 Made the Distribution Fight Visible

The Workday-Microsoft integration is useful because it separates the user surface from the transaction system.

Workday described a flow in which a Microsoft 365 user asks a question in natural language. If the request involves Workday data or processes, Copilot connects to Sana Self-Service Agent. Sana completes the task in Workday using existing approvals, policies and business rules, then returns the result in Copilot. Workday said the underlying Workday data and transactions remain in the Workday trusted system, even though the activity appears to the user in Copilot.

That architecture is commercially important.

Microsoft gets to make Copilot feel like the place where work happens. It does not need to own every HR or finance workflow to increase the daily habit of asking Copilot for help. Workday gets to avoid losing the transaction layer. It can say that employees never have to leave their flow of work, while customers keep Workday as the policy and execution system.

The dividing line sounds clean. In practice, it creates new buyer questions.

If an employee resolves a leave request in Copilot through Workday, who gets credit for the deflected HR case? If the answer is wrong because the policy article was stale, who owns the correction? If a manager bulk-approves timesheets from a chat surface, which system records the review? If a finance leader asks about an expense policy and gets guided into a case, does the value accrue to Microsoft because the work started in Copilot, to Workday because the transaction ran there, or to the shared-service team because the case never reached a human?

These questions matter because HR service automation is sold through numbers.

Vendors talk about reduced support tickets, faster answers, fewer manual tasks, better employee experience, more productive managers and lower service-center volume. Those claims are hard enough when the request begins and ends inside one product. They become harder when the employee asks in Copilot, the action runs through Workday, the identity is governed by Microsoft Entra, the evidence is retained in Workday, and a follow-up ticket lands in ServiceNow or Jira.

The user sees one answer. Procurement sees several claims on the same unit of work.

Employees Do Not Want Another Portal

The demand side is not mysterious.

Employees do not wake up wanting to navigate an HR information system. They want a specific answer: how much leave they have, whether a policy covers them, why a payslip changed, how to update a dependent, where a form sits, whether an onboarding task is complete, or who must approve a request. Managers want the same thing at higher stakes. They need to approve time, initiate changes, complete reviews, open requisitions, move onboarding forward, resolve payroll exceptions and answer team questions without losing the workday to navigation.

This is why HR service delivery has always been pulled toward the communication layer.

Email became a support queue because it was where workers already were. Slack and Teams became help-desk surfaces because employees could ask inside the channel they used all day. Mobile apps became necessary for frontline teams because desk-bound portal design missed workers who do not spend the shift in front of a laptop. AI agents now push the same logic further. The request can start as a sentence. The sentence can trigger a workflow. The workflow can cross HR, finance, IT, payroll, identity and facilities.

ServiceNow has been explicit about this direction. In March, when it announced Autonomous Workforce and the addition of Moveworks to the ServiceNow AI Platform, the company described EmployeeWorks as a conversational front door available where employees work and collaborate, including Teams, Slack and browsers. It said the product connects conversational AI chat and enterprise search with the ServiceNow portal and autonomous workflows, turning intent into coordinated action across systems.

That phrase - coordinated action across systems - is the new center of the category.

An HR portal can answer a policy question. A service agent must know whether answering is enough, whether a case should open, whether payroll must be touched, whether a manager should approve, whether IT should provision access, whether a record must be retained, whether a legal hold applies, and whether the employee has permission to see the answer.

This is why the chat surface alone is not sufficient. A generic assistant can make a policy sound clear. It cannot safely update pay, start a promotion, change an employee record, approve time or initiate onboarding without transaction rights and workflow controls. That gives the system-of-record vendors a strong defense.

It also gives communication platforms a strong offense. If the employee habit lives in Copilot, Gemini, Slack or Teams, the HCM vendor must meet the user there or risk becoming a back-end utility.

Workday Keeps the Transaction Layer

Workday’s Copilot move is easier to understand against its broader Sana strategy.

In March, Workday introduced Sana from Workday as an agentic AI platform that connects people and money data, context, policies and processes. The company said Sana Self-Service Agent had more than 300 skills across areas such as pay, time and absence and was already handling everyday HR and finance tasks for customers.

Joel Hellermark, who founded Sana before Workday acquired the company in 2025, framed the product as a way to bring superintelligence into work rather than another point tool. Srini Raghavan, Microsoft’s corporate vice president for Teams, said the Copilot integration gives users access to Workday’s people and financial data from the Microsoft 365 surface. Those comments matter less as marketing copy than as a map of the commercial split: Microsoft brings the workspace, Workday brings the trusted transaction.

The Copilot integration turns that product strategy into a distribution strategy.

Workday does not have to persuade every employee to live inside Workday all day. It can let the employee start elsewhere while keeping the action on Workday rails. In its May 13 release, Workday made the contrast directly: Workday business processes are deterministic by design, with clear starts and finishes, approvals and controls; modern AI is probabilistic, reasoning and recommending from patterns. The pitch is that Sana can couple AI interaction with deterministic workflows.

That is the version of agentic HR large employers will be more willing to buy.

An HR service agent cannot be only fluent. It has to respect role-based permissions. It has to know the difference between reading a policy and changing a record. It has to avoid exposing payroll or health-related data to the wrong person. It has to preserve a record when the request becomes part of an employment decision, an employee dispute, a tax correction, a works council inquiry or a future audit.

For Workday, those requirements defend the core platform. The company can say that Copilot is an access point, not the owner of the HR transaction. The same logic would apply to other surfaces: a request can begin in Teams, Slack, email or browser search, but the final action should still respect Workday approvals, data permissions and process rules.

That creates a new kind of platform dependency.

In the old HR self-service model, the portal owned the experience because it was where the employee had to go. In the new model, the HCM system owns the transaction because it is where the policy and record live. The most valuable vendor may not be the one with the prettiest chat interface. It may be the one that can let any front door safely reach the underlying people and money workflows.

Microsoft Gets the Surface, Workday Gets the Proof

Microsoft’s incentive is different.

Copilot becomes more valuable when it can do real work inside the applications employees already depend on. HR and finance requests are attractive because they are frequent, personal and often frustrating. A tool that can answer a payroll question, request time off or start an approval earns a different kind of habit than a tool that only drafts text.

Microsoft Agent 365 adds another layer to that strategy. On May 1, Microsoft said Agent 365 was generally available and described it as a control plane to observe, govern and secure agents and their interactions. The company framed the problem as agent sprawl across apps, endpoints and cloud, with agents acting on behalf of users or operating with their own credentials.

For HR, that matters because employee-service agents will not stay inside one system.

A payroll request can touch ADP or Workday, an expense question can touch finance, an onboarding request can touch HRIS, background check, identity, equipment and access, and a manager question can touch performance, goals, learning and scheduling. If Microsoft can provide identity, network controls, agent registry, audit signals and endpoint discovery around those requests, it can become part of the governance layer even when the HR transaction sits elsewhere.

That gives Microsoft two positions in the stack.

First, it owns a large share of the employee’s daily workspace. Copilot, Teams, Outlook, SharePoint and Microsoft 365 admin surfaces are already present in many large companies. Second, it can tell IT and security teams that agents need to be governed with the same seriousness as users, devices and applications.

Workday, ServiceNow, SAP, Oracle, ADP and UKG all have domain-specific workflow depth. Microsoft has horizontal reach. The question for buyers is how much HR service work should be surfaced through the horizontal work layer and how much should stay native to the HR platform.

There is no clean answer.

Moving too much to Copilot risks making HR service dependent on a general productivity vendor’s interface, availability, prompt controls and user permissions. Keeping everything inside HCM risks low adoption because employees will avoid the portal until a problem forces them there. The durable architecture is likely to be split: daily requests begin where employees work, while final transactions, approvals, evidence and sensitive data remain governed by the system that owns the record.

That split will be useful only if contracts make it measurable.

ServiceNow, UKG, SAP, Oracle, and ADP Make It a Platform Race

Workday’s announcement landed in a crowded month.

ServiceNow’s Autonomous HR release said its HRBP experience, available through HR Service Delivery, would use natural language talent analytics, autonomous workflow orchestration and real-time workforce intelligence. Its next-generation manager experience promises policy questions, approvals and sensitive escalations handled conversationally with guardrails. Availability is staged: HRBP experience in Q3 2026 and manager experience beginning in the second half of 2026.

ServiceNow’s Bhavin Shah described the target as work that crosses systems, not a better search box. That is why Moveworks matters. It gives ServiceNow a front door that many employees may touch before they ever open an HR service portal.

UKG took a different route. On April 29, it announced UKG People Assist inside Google Cloud’s Gemini Enterprise Agent Gallery. The first agent is expected to become generally available through Gemini Enterprise Agent Gallery and Google Cloud Marketplace in July. UKG said a hiring manager could initiate a new-hire onboarding request in Gemini Enterprise, while UKG creates the employee record and triggers HR, payroll and policy-driven processes, coordinating with systems such as ServiceNow for equipment and access.

That is a clearer frontline story than a generic HR chatbot.

UKG sells into time, pay, scheduling, workforce management and frontline operations. Its claim is not only that an employee can ask a question. It is that the agent can move work across the operational systems that determine whether a worker is onboarded, scheduled, paid and ready. If the request starts in Gemini Enterprise, UKG still wants to own the execution of workforce work.

SAP’s May 14 Sapphire update pushed the same direction from the suite side. SAP described Joule Assistants for HR that coordinate agents across payroll, recruiting, onboarding, HR service and workforce upskilling. Its HR Service Assistant is intended to help administrators resolve common HR questions and direct employees to the next step. The Payroll Assistant coordinates multiple agents to prepare payroll runs, identify issues early and guide administrators to resolution.

SAP’s Dan Beck positioned the shift as autonomous HCM, with Joule coordinating agents across HR work. UKG’s Corey Spencer made a similar point from the workforce side, arguing that agentic AI should help leaders handle complex, people-centric processes without forcing them through fragmented tools.

Oracle and ADP are making similar claims from their own installed bases.

Oracle introduced Fusion Agentic Applications for HR in April, positioning the applications inside Fusion Cloud HCM rather than as a loose assistant outside the transaction system. ADP launched ADP Assist agents in January, citing a data foundation spanning 1.1 million clients, 140 countries and territories, and 42 million wage earners. Its agents cover payroll variance detection, tax registration gaps, policy guidance, analytics and talent actions such as initiating a promotion through natural language.

Maria Black, ADP’s chief executive, has been selling that advantage as data depth. The company wants customers to believe payroll, tax and workforce agents are safer when they run on the same platform that already processes wages. Oracle makes a related argument from suite integration: the agent is not bolted onto HR from outside; it is embedded in the application that owns the workflow.

The pattern is consistent.

Every large HR platform wants to say two things at once. Employees should not have to navigate systems. Customers should not lose control of the systems that matter.

That tension defines the HR service market now forming around agents.

Budget Owners Will Count Deflected Cases Differently

The first buyer fight will be over value attribution.

An HR shared-services leader may see a reduction in tickets. A CIO may see higher Copilot adoption. A Workday or ServiceNow owner may see more transactions completed through existing workflows. A CFO may see new agent licenses, premium AI modules, marketplace add-ons, security controls, implementation services and integration costs. Each team can be right while disagreeing about whether the program saved money.

Case deflection used to be simpler.

If an employee read a knowledge article and did not open a ticket, HR could count the deflection. If a virtual agent answered the question in the HR portal, the service delivery platform could claim the interaction. If a payroll practitioner resolved a variance faster, payroll operations could count the time saved.

Agent distribution breaks that neat accounting.

A single transaction can begin in Copilot, retrieve policy context from Workday, verify identity through Microsoft, write the action in Workday, open an exception in ServiceNow, trigger equipment provisioning, produce a payroll change in ADP, and store evidence across several systems. If all vendors claim contribution, the business case inflates. If none of them provides a reconciled event trail, Finance cannot see which cost replaced which human activity.

This is where HR service agents connect to the broader AI pricing problem.

The invoice may include a Copilot license, an HCM AI feature, a Workday or Salesforce-style credit pool, ServiceNow AI usage, integration platform charges, identity-governance controls, security logs, implementation consulting and premium support. The same solved case may be counted as an employee-experience win, a support deflection, a manager-productivity gain and a workflow automation event.

Buyers need a unit-of-work file, not a slide.

For HR service, that file should answer basic questions: who initiated the request; where it started; which systems were touched; what data was read; what transaction was written; which human approved; what policy version applied; how long it took; whether a case was avoided; whether a follow-up case opened; which vendor meters were consumed; and whether the answer was later corrected.

Without that file, agent ROI will depend on the vendor that tells the cleanest story.

Picture the quarterly review. The HR shared-services leader says employee tickets fell 18%. The Microsoft owner says Copilot adoption rose. The Workday owner says more self-service transactions completed without HR intervention. The ServiceNow owner says escalations were cleaner. Finance sees the combined bill. Without a common event record, the meeting becomes a negotiation over anecdotes.

That is why distribution is also a finance problem. The front door can make employees happier and still make the cost file harder to read.

HR Help Desks Become Risk Surfaces

Employee-service agents handle lower-drama tasks than hiring decisions, but they do not handle low-risk data.

Pay, leave, benefits, tax withholding, accommodations, performance, employee relations, manager actions, location, scheduling and onboarding can all sit behind a friendly question. A wrong answer may not reject a candidate, but it can still create payroll errors, missed leave rights, inconsistent policy treatment, privacy exposure or a retaliation claim. A fast workflow can also make a bad transaction faster.

That is why Workday emphasized role-based permissions, approvals, business rules and visibility in its Copilot announcement. It is also why ServiceNow talks about governance and audit trails, why SAP frames Autonomous HCM around human control, why ADP stresses human oversight for payroll variance remediation, and why Microsoft is building controls around agent identity, network access, shadow agents and audit evidence.

The control burden will grow as service agents move from answering to acting.

An agent that says “your vacation balance is 48 hours” is one thing. An agent that submits leave, changes tax withholding, starts a promotion, opens a sensitive employee relations case or approves timesheets is different. The second agent needs stronger permissions, more logging, clearer exception handling and a way to prove that a human had meaningful control when the action crossed into employment consequence.

The hardest cases will be mixed requests.

A manager may ask why an employee is absent more often than peers. That sounds like analytics until it becomes performance, accommodation, scheduling or discipline. An employee may ask about family leave, which sounds like policy until it becomes health or caregiver information. A payroll variance may look like an operations error until it reveals a classification problem. A new-hire onboarding request may touch recruiting, payroll, identity, equipment, training and safety compliance.

These are not exotic edge cases. They are the work HR service teams already handle.

Agents make the work faster and more distributed. That means the audit trail must become more specific, not less. A buyer should know when the agent answered, when it acted, when it escalated, when it refused, when it asked for human approval and when it handed work to another system.

What Buyers Should Demand Before Switching It On

The procurement template for HR service agents should not start with the quality of the chat interface.

It should start with the workflow boundary.

Buyers need to know which requests the agent can answer, which requests it can complete, which requests it must escalate, which data sources it can read, which systems it can write to, which approval paths apply and which actions require a human. That boundary should be visible in the admin console and written into the contract.

The second requirement is attribution. If a request starts in Copilot and completes in Workday, the event record should show both. If Gemini launches a UKG onboarding workflow that triggers ServiceNow equipment provisioning, the buyer should be able to reconstruct the chain. If ADP Assist suggests a payroll remediation under human oversight, the record should separate the agent recommendation from the human action.

The third requirement is cost mapping. Each resolved request should connect to the meters it consumed. That does not mean every employee sees the cost. It means Finance can reconcile usage against the business case. A deflected case that triggers five paid agent actions, a premium workflow credit and an integration charge may still be worth it. The buyer needs to know.

The fourth requirement is correction handling. HR service agents will make mistakes. They will use stale policy, misunderstand a request, surface a partial answer, route a case poorly or write a transaction that needs reversal. A production agent should therefore have a correction workflow: who can challenge the result, who reviews it, how the corrected answer propagates, how affected employees are notified and how the vendor supports investigation.

The fifth requirement is user trust. Employees should know when they are dealing with an AI agent, which system is handling their data and when a human will review the request. This does not require a warning label on every harmless question. It does require a clear distinction between policy lookup, transaction execution and sensitive employment action.

These requirements sound heavy only if the product is sold as a chatbot.

They are normal if the product is sold as an HR service layer.

A Portal Still Has to Exist Somewhere

The HR portal is not dead. It will stay alive with less visibility.

Large employers still need a place where policies are authored, cases are managed, approvals are configured, records are retained, analytics are reviewed and exceptions are handled. A worker may never want to open that place for a simple question. HR, legal, payroll, finance and IT still need it when the simple question becomes a transaction, a dispute or an audit file.

That is why front doors alone will not decide this market.

Microsoft, Google, Slack and Teams can pull employee requests into daily work. Workday, ServiceNow, SAP, Oracle, ADP and UKG can defend the transaction layer because they know the record, the policy and the workflow. The winning customer architecture will join those two realities without letting either side erase the other.

An employee should be able to ask from the tool already open.

The company should be able to prove what happened after the question was asked.

On May 13, Workday made that split visible. Copilot became the place the employee could start. Workday stayed the place where the HR and finance action had to finish.

The next renewal meeting will ask whether that split saved money, reduced cases, protected data and made employees trust the system more. If the answer is scattered across three dashboards and four invoices, the help desk did not disappear. It only moved.

This article provides a deep analysis of HR service agent distribution across Workday, Microsoft, ServiceNow, UKG, SAP, Oracle, and ADP. Published May 31, 2026.