Skip to content
AI.info

The Pulse

Zendesk brings service workflows to Microsoft Copilot via Bridge

Zendesk Bridge connects selected service tools and workflows to Microsoft Copilot experiences. Bridge is in early access, and integration availability must be confirmed.

Zendesk brings service workflows to Microsoft Copilot via Bridge

Selected Zendesk service tools and workflows can now be used inside Microsoft Copilot experiences through Zendesk Bridge, including workflows for employee onboarding and software access. The company described the connections at Microsoft Ignite in a November 17 post.

Bridge is in early access, and businesses need to confirm the availability of their Microsoft integration. The offering connects Zendesk capabilities with Copilot Cowork, Microsoft 365 Copilot and agents built in Microsoft Copilot Studio.

Requests in Cowork

A plugin connects employee requests in Copilot Cowork to Zendesk knowledge and configured workflows. Employees can start supported onboarding, equipment and software-access workflows and check their progress, including whether approval or fulfillment is still pending.

For example, a new employee might request a laptop and access to a sales reporting application. The process can involve equipment details, access requirements, manager approval and coordination across systems.

The plugin combines a connection to Bridge’s Model Context Protocol, or MCP, server with Zendesk-provided skills. Those skills are workflow instructions that guide which tools the assistant uses, their sequence and how it communicates results.

Equipment lookups are read-only. Allocation and software provisioning depend on configured Action Flows, and the assistant distinguishes completed actions from requests awaiting approval or fulfillment.

Connector for custom agents

A separate Microsoft-certified Zendesk MCP connector gives Microsoft 365 Copilot and agents built in Copilot Studio access to selected Zendesk capabilities. Teams can use service knowledge and context to build experiences that take permitted actions without building and maintaining custom API integrations.

In one example from Zendesk, an employee could ask an IT agent built with Copilot Studio for access to a sales reporting application. The agent can retrieve relevant Help Center guidance and submit a service request with the details IT needs to review it.

In Copilot Studio, teams add the connector from the MCP catalog and authorize the Zendesk connection through OAuth. They can then configure agent instructions for when to retrieve guidance, collect more information and submit or update a service request.

Permissions and records

Bridge makes only tools approved for a connection and user available to the assistant, while existing Zendesk permissions govern what that user can access and do. Businesses control which AI experiences connect and which capabilities those experiences can access.

For each Cowork tool call, Bridge records the calling application, connected user, requested tool, access decision and result. The records let teams review activity and investigate blocked or failed actions.

Zendesk manages the connector’s defined tool set. In Zendesk Admin Center, administrators can review the external AI connection, manage access for permitted Zendesk agent groups and disconnect the integration.

Sources

  1. Original source · Press release Zendesk · Zendesk brings its trusted service foundation to microsoft… zendesk.com

Other pages read

  1. Zendesk · Zendesk bridge for microsoft cowork zendesk.co.uk

Related stories

Explore

More articles