Microsoft 365 Copilot + Zendesk: What the Integration Can (and Can't) Do in 2026
Partly — Microsoft ships two official Zendesk Copilot connectors, but both are read-only, and the one path that writes is a separate Zendesk-built agent scoped to your own tickets. The Zendesk Ticket connector and the Zendesk Help Center connector index tickets and Guide articles into Microsoft Graph so Copilot and Microsoft Search can ground answers and cite the record — they don’t change anything in Zendesk. Writing exists only through the Zendesk agent for Microsoft 365 Copilot, a separate app Zendesk publishes that lets you search the help center, create a ticket, add a public comment, and resolve tickets — but only tickets you created, and only comments and status, not arbitrary fields. And either way, everything happens inside a Copilot session you’re driving — nothing watches your queue between chats.
Here’s what each path actually does, how to turn them on, where the ceiling is, and what to use if you want Zendesk-adjacent work that runs on its own.
What Microsoft 365 Copilot can actually do with Zendesk
Through the two Copilot connectors (the default, read-only path):
- Search and summarize tickets. The Zendesk Ticket connector indexes ticket metadata — status, assignee, requester, priority, and other properties — so you can ask “Check the status of ticket CP-2234” or “Summarize CP-1234” from inside Teams or Outlook, with the record cited.
- Answer from your help center. The Zendesk Help Center connector indexes published Guide articles — title, body, category, labels, URLs — so Copilot can answer “What is the return policy?” or “How do I upgrade my subscription?” grounded in your own knowledge base.
- Respect Zendesk permissions. Both connectors map Zendesk identities to Microsoft Entra ID and enforce access, so a user only sees tickets and articles they’re already allowed to see in Zendesk.
- Ground custom agents. Developers can use either connector as a knowledge source in declarative agents built in Copilot Studio, Agent Builder, or the Microsoft 365 Agents Toolkit — still for retrieval, not writing.
Through the separate Zendesk agent for Microsoft 365 Copilot (a Zendesk-published app, the write path):
- Create a ticket from inside Copilot — type “Create a ticket” and a Create Support Ticket form opens, prefilled from your conversation if you’d been chatting with the agent first.
- Add a public comment and resolve a ticket — but only tickets you created, and the agent allows comments and status changes, not editing all ticket fields.
- Search the help center conversationally and open a ticket directly in Zendesk to keep working.
How to set it up
The read-only connectors are a tenant-admin job:
- In the Microsoft 365 admin center, go to Copilot → Connectors and add Zendesk Ticket and/or Zendesk Help Center, then follow Microsoft’s deployment guide.
- Authenticate to Zendesk and configure the crawl. The Ticket connector supports incremental crawls every 15 minutes and full crawls daily.
- Set the access model and map Zendesk identities to Entra ID so results honor Zendesk permissions.
- Test in Copilot with something read-only: “Summarize the open tickets for Contoso” or “What does our refund policy article say?”
To write, you set up the separate Zendesk agent for Microsoft 365 Copilot, which needs an admin in both Microsoft 365 and Zendesk:
- In the Zendesk Admin Center, go to Apps and integrations → Integrations, select Microsoft Copilot, accept terms, and connect your Microsoft account.
- In the Microsoft 365 admin center, go to Copilot → Agents, find the Zendesk Agent, and assign which users can install and use it.
- Note the dependency: if the Zendesk admin who set up the connection loses their admin role, the integration stops working until another admin reconnects it. The agent requires a supported Zendesk Suite or Support plan.
The limits that matter
- The connectors are read-only. They index for grounding and search — they can’t create a ticket, comment, or change a status in Zendesk. Attachments aren’t indexed, and the Help Center connector skips community posts and topics.
- The writing agent is narrow. It can create tickets, but it only lets you comment on and resolve tickets you created — not reassign, not edit fields across the queue, not touch a colleague’s tickets. It’s a self-service helper, not an agent-desk automation.
- Two admins, two products. The read path is a Copilot connector configured by a Microsoft 365 admin; the write path is a Zendesk-built agent that needs admins in both systems and a supported Zendesk plan. They’re separate setups with separate ceilings.
- No triggers, ever. Neither the connectors nor the agent fires on a Zendesk event. Copilot answers when you prompt it; the agent creates a ticket when a person types the request. A ticket can breach SLA or a VIP can reply over the weekend and nothing moves on its own.
- Session-bound. Every action needs a driver in a live Copilot session inside Teams or Outlook. There’s no standing watch on your queue.
If you want Zendesk-adjacent work that runs on its own: Carly
The moment you want something to happen around Zendesk without you in the chat — a high-priority ticket triaged and its owner emailed within minutes, an SLA-risk ticket flagged to the right Slack channel, a Monday backlog digest built and sent, a follow-up task created when a ticket sits untouched — you’ve crossed past what a grounding connector or a self-service agent is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a session:
- Fires on events and schedules, 24/7, in the cloud. When a ticket is created, updated, or breaches a threshold, Carly reacts — summarizes it, emails the owner, updates the ticket, posts to Slack — while your laptop is closed.
- Actually reads and writes. Zendesk is a native Carly integration, so Carly can create tickets, add comments, update status and fields, and route work — across the whole queue, not just tickets you personally opened.
- Sends, not just drafts. Carly drafts and sends email across Gmail and Outlook, books meetings, manages tasks, updates your CRM, and records meetings — the follow-through that stops at the chat with Copilot.
- Builds the workflow by interviewing you. Tell Carly “when a P1 ticket comes in unassigned, draft a summary, email the on-call lead, and post it to #support” in plain English; it interviews you and builds it — no admin center, no connector crawl, no prompt engineering.
Carly connects to 200+ tools across 40+ categories natively, plus any other tool via your own API key — paste it on carlyassistant.com/integrations. AI agents start at $35/month, and steps in a workflow that don’t use AI run free. See integrations.
Microsoft 365 Copilot vs Carly
| Microsoft 365 Copilot (Zendesk) | Carly | |
|---|---|---|
| Answer questions grounded in ticket data | Yes (connector, read-only) | Yes |
| Answer from help center articles | Yes (connector, read-only) | Yes |
| Search Zendesk records in Microsoft 365 | Yes | Via the integration |
| Create a ticket | Only via Zendesk agent | Yes, natively |
| Comment on / resolve tickets | Only your own tickets (Zendesk agent) | Yes, across the queue |
| Update ticket fields / reassign | No | Yes |
| Acts on Zendesk triggers / events | No | Yes |
| Monday backlog digest, on schedule | No | Yes |
| Sends email as part of the flow | No | Yes (Gmail + Outlook) |
| Works while laptop is closed | No (session-bound) | Yes (cloud, 24/7) |
| Setup | Admin center + connector (+ Zendesk agent for writes) | Describe it in plain English |
| Pricing | Microsoft 365 Copilot license per user | AI agents from $35/mo |
Copilot’s Zendesk connectors are a grounding layer that pulls ticket and article context into your chats, with the Zendesk agent adding a thin self-service write path. Carly is a teammate that acts on Zendesk events as they land.
Frequently Asked Questions
Does Microsoft 365 Copilot work with Zendesk?
Yes, mainly for reading. Microsoft ships two official connectors — the Zendesk Ticket connector and the Zendesk Help Center connector — that index tickets and Guide articles into Microsoft Graph so Copilot and Microsoft Search can answer questions grounded in your Zendesk data. Both are read-only. A separate Zendesk-built agent adds a limited write path.
Can Microsoft 365 Copilot create or update Zendesk tickets?
Only through the separate Zendesk agent for Microsoft 365 Copilot, and only within limits. It can create a ticket, add a public comment, and resolve a ticket — but only tickets you created, and it allows comments and status changes, not editing all fields. The two Copilot connectors themselves write nothing back to Zendesk.
How do I connect Copilot to Zendesk?
For reading, a Microsoft 365 admin adds the connectors in the admin center → Copilot → Connectors → Zendesk Ticket / Zendesk Help Center, authenticates to Zendesk, and configures the crawl per Microsoft’s deployment guide. For the write agent, you need to be an admin in both Microsoft 365 and Zendesk: connect Microsoft Copilot in the Zendesk Admin Center, then assign the Zendesk Agent to users under Copilot → Agents.
Can Copilot react to a new or escalated Zendesk ticket automatically?
No. Neither the connectors nor the Zendesk agent fires on Zendesk events — Copilot answers when you prompt it, and the agent creates a ticket when a person types the request. For “when a P1 ticket lands, triage it and email the owner” or “when a ticket is about to breach SLA, flag it,” you need a trigger-based assistant like Carly, which integrates natively with Zendesk and runs in the cloud around the clock.
More: Best AI customer support tools · Best AI agents for productivity · Claude + Zendesk · ChatGPT + Zendesk
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
