Skip to content
KiweelyKiweelyKiweely

Microsoft Copilot Studio and Workday: Agent Gateway vs. User-Delegated Bridge

Workday’s published path for Copilot Studio is Agent Gateway: Agent System of Record registration, an agent system user, and OAuth on the regional endpoint. Kiweely Bridge (coming next) is a different design for Claude, ChatGPT, and Gemini, and does not list Copilot Studio.

  • By Kiweely
  • 7 min read
On this page
Microsoft Copilot Studio and Workday: Agent Gateway vs. User-Delegated Bridge

Microsoft Copilot Studio can call Workday, and Workday documents that path. It is not the same path as Kiweely Bridge (coming next). Copilot Studio, on Workday’s own admin guide, connects to Workday’s agent endpoint after the agent is registered in the Agent System of Record. Bridge is a user-delegated Workday API client for Claude, ChatGPT, and Gemini. The published Bridge pages do not list Copilot Studio as a client.

Facts below are from Workday’s admin guide and Microsoft Learn, fetched 16 November 2026, and from Kiweely Bridge’s published pages.

What Workday requires before Copilot Studio can call the agent endpoint

Connect an External Agent with Workday MCP says you can connect any registered external agent to Workday’s server, and then states: this functionality is for Extend Professionals only. The same page names Microsoft Copilot Studio, Google Agentspace, and Amazon Bedrock AgentCore as platforms that use that endpoint and the same OAuth credentials. It tells you to follow each platform’s own setup after Workday’s side is done.

Workday’s sequence on that page is:

  1. Set up the Agent System of Record.
  2. Discover agent-ready tools, register the external agent, configure it, and configure security policies for its skills.
  3. Sign in through the authorize endpoint, exchange the code for an agent-system-user access token, and confirm the connection with a tools/list call.
  4. Point the outside platform at the same endpoint.

The endpoint pattern Workday prints is https://{agentGatewayRegionEndpoint}/{tenantName}/mcp. The worked example host is https://us.agent.workday.com. Workday’s page says access tokens expire after 4 hours and refresh tokens after 30 days. The agent security topic adds that external-agent access tokens are valid for 4 hours and that you cannot currently customize that expiry for third-party agents.

Subscription paperwork is separate from the “no extra ASOR SKU” sentence. About Workday Agents says you do not need to purchase an additional SKU to use the Agent System of Record; it is included in the core subscription. The same page says that in order to register agents in Production, you must opt in to the Universal Main Service Agreement (UMSA). The external-agent page says UMSA customers already have the feature, and Main Service Agreement customers must enable it through Innovation Services. Those are Workday’s words. This article does not turn them into a price.

Two Copilot Studio setups, not one

Workday and Microsoft document different layers.

Workday’s agent sync is an administrative bootstrap. Configure Microsoft Agent Sync (last updated 2 October 2026 on that page) synchronizes agents from Copilot Studio and Azure AI Foundry into the Agent System of Record. It requires a Microsoft Global Administrator, because the sync uses application permissions that need Entra admin consent. You create an Entra app registration, a Power Platform application user mapped to that service principal, Dataverse role access for Copilot Studio, then the Workday task Create Microsoft Agent Sync Configuration with an OAuth 2.0 client-credential store. After sync, Workday’s page says to edit the Copilot Studio custom connector’s security settings and enter the Workday agent-system-user credentials, then try the agent in the Copilot playground.

Copilot Studio’s own connector UI is how an agent attaches to a server that already exists. Microsoft Learn says Copilot Studio supports the Streamable transport, and that it no longer supports SSE for this protocol after August 2025. In the onboarding wizard you set a server name, description, and server URL, then pick authentication: none, an API key, or OAuth 2.0. OAuth 2.0 can be dynamic discovery, dynamic, or manual. Manual mode asks for a client ID, client secret, authorization URL, token URL, refresh URL, and optional scopes, and Microsoft says the consent card is presented in the agent chat. Access to these servers relies on Power Platform connectors, so a Power Platform data policy that governs connectors also governs the tools.

Workday’s page and Microsoft’s page do not spell out a single happy-path screenshot that joins every field. What both do say is that Copilot Studio is an outside MCP client, and Workday’s client for that path is the agent system user created when the agent is configured, not a normal worker’s Register API Client grant.

How the agent acts once it is connected

Agent security defines two modes:

Delegate Ambient
Who acts DelegateThe user and the agent system user together AmbientThe agent system user alone
Sign-in DelegateOAuth on-behalf-of. Workday-built agents: access token up to 60 minutes on the authorization-code grant. External agents: 4 hours, not customizable today AmbientThe ambient agent system user, with no person in the flow
What is allowed DelegateIntersection of the person’s permissions and the agent’s enabled skills. The person must also be in a security group on the skill’s Available To list AmbientThe agent’s own domain and business-process policies. Activating an ambient skill creates an Ambient Agent Security Group
Audit DelegateThe agent is By User. The person is On Behalf Of User AmbientThe agent system user is By User

Workday also says you cannot delegate agent interactions or use a proxy, and agent system users do not support proxy accounts. A skill’s Available To list is a separate gate from domain security: failing Available To denies the conversation even when the person could run the underlying task.

What Kiweely Bridge publishes instead

Kiweely Bridge is coming next. It is not a second way to register a Copilot Studio agent in the Agent System of Record. The published product is a remote connector for Claude, ChatGPT, and Gemini, on desktop, browser, and phone, with no laptop install.

On security and setup, Bridge’s pages say:

  • The Workday client is Register API Client, authorization code with PKCE, for each employee. It is not an Integration System User, and Bridge does not ask for a Workday AI agreement.
  • Every call runs under that worker’s own security groups and domains. Bridge does not query with a shared service account.
  • The tenant starts read-only. Admins enable writes one by one. Disabled tasks are absent from the tool list.
  • An enabled write pauses for an out-of-band browser card that shows now and after. Chat text cannot click Allow.
  • Workday responses pass through memory. Bridge’s published telemetry is timestamp, tenant ID, tool name, HTTP status, and latency. Pay figures, worker names, and request arguments are not written to those logs.
  • An AI admin agent walks Workday and IT through the API client in Sandbox, field rules, and tests as roles such as Employee or Manager, then the connector is published. On a company plan, a workspace owner adds the connector once.

Pricing on the same pages, by employees licensed in Workday, with unlimited calls, Production, and every non-production tenant included:

Licensed employees Price
Licensed employeesUp to 1,000 Price$499 per company per month
Licensed employees1,001 to 5,000 Price$1,499 per company per month
Licensed employees5,001 to 20,000 Price$3,999 per company per month
Licensed employeesAbove 20,000, or a dedicated static IP, or a self-hosted container PriceEnterprise, by quote
Licensed employeesOne person on their own Workday developer tenant PriceFree

Which path you are actually choosing

Question Workday Agent Gateway for Copilot Studio Kiweely Bridge (coming next)
QuestionWhere it is documented Workday Agent Gateway for Copilot StudioWorkday admin guide and Microsoft Learn Kiweely Bridge (coming next)kiweely.com/bridge
QuestionAssistants named Workday Agent Gateway for Copilot StudioCopilot Studio is named by Workday. Microsoft’s wizard attaches whatever server URL you enter Kiweely Bridge (coming next)Claude, ChatGPT, and Gemini. Copilot Studio is not listed
QuestionWorkday identity Workday Agent Gateway for Copilot StudioAgent system user, delegate or ambient Kiweely Bridge (coming next)That employee’s user-delegated grant
QuestionExtra Workday program Workday Agent Gateway for Copilot StudioExtend Professionals for the external-agent feature; Production agent registration requires UMSA opt-in; MSA customers use Innovation Services Kiweely Bridge (coming next)No Workday AI agreement on the Bridge pages
QuestionWhere a person confirms Workday Agent Gateway for Copilot StudioWorkday evaluates Available To plus the person’s own tasks. Microsoft’s manual OAuth consent card is in the agent chat. This article does not claim a separate now/after card Kiweely Bridge (coming next)Browser card outside the chat for every enabled write
QuestionStatus Workday Agent Gateway for Copilot StudioWorkday’s and Microsoft’s features as documented Kiweely Bridge (coming next)Coming next. Register interest

If the workforce assistant is Copilot Studio, follow Workday’s external-agent guide and Microsoft’s wizard, and budget the Extend Professionals and UMSA conditions Workday prints. If the workforce assistant is Claude, ChatGPT, or Gemini and you want each call to be that employee’s own API client, that is the Bridge design, and it is not available yet.

Frequently asked questions

Does Copilot Studio skip Workday security?

No. In delegate mode Workday checks the skill’s Available To groups and then the person’s domain and business-process access. Ambient mode uses the agent system user alone. Neither mode is a bypass.

Can Kiweely Bridge be the server URL inside Copilot Studio?

The Bridge pages published today name Claude, ChatGPT, and Gemini. They do not name Copilot Studio. Treat a Copilot Studio connection as unsupported until a Bridge page says otherwise. Bridge is coming next in any case.

Does “ASOR is included” mean the agent endpoint is free for every employee?

Workday says the Agent System of Record does not need its own SKU. The external-agent topic still limits that feature to Extend Professionals, and Production registration still requires UMSA opt-in. Usage of Workday’s own AI skills is metered in Flex Credits on Workday’s rate card. That meter is a different topic from Bridge’s company price.

Register interest in Kiweely Bridge. It is coming next.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.