Microsoft 365 Copilot + ServiceNow: What the Integration Can (and Can't) Do in 2026
Partly — Microsoft ships three official ServiceNow Copilot connectors, but every one of them is read-only. The Tickets, Knowledge, and Catalog connectors index ServiceNow data into Microsoft Graph so Copilot, Copilot Search, and Microsoft Search can ground answers in your incidents, KB articles, and catalog items and cite the record. None of them write back: Copilot can’t open an incident, update a change request, or submit a catalog request through them. Creating or updating a ticket exists only if you build a Copilot Studio agent that holds a ServiceNow connection — a separate product and a maker’s job. 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 it on, where the ceiling is, and what to use if you want ServiceNow-adjacent work that runs on its own.
What Microsoft 365 Copilot can actually do with ServiceNow
Through the official connectors (the default, read-only path):
- Answer questions grounded in ticket records. The Tickets connector indexes the
tasktable and its children —incident,problem, andchange_request— plus user tables likesys_userandsys_user_group. Ask “What’s the status of the high-priority network outage ticket?” or “Show all open tickets assigned to me” and Copilot answers from the index, with the record cited, without leaving Teams or Outlook. - Retrieve knowledge-base answers. The Knowledge connector indexes KB articles — including comments, attachments, knowledge blocks, and accordions — so Copilot can answer “How do I request a new device?” or “How do I set up a VPN connection?” from your own runbooks.
- Surface service-catalog items. The Catalog connector indexes catalog items (
sc_cat_item) with title, description, price, delivery time, and owner, so users can discover “available laptops for new employees” in Copilot. - Respect ServiceNow permissions. The Knowledge and Catalog connectors evaluate ServiceNow user criteria and role-based permissions (including nested/parent-level permissions) via Entra ID identity mapping, so users only see records they can already see in ServiceNow.
- Ground custom agents. Developers can use any of these connectors 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 a Copilot Studio agent you build (the only write path):
- Help a user create a ServiceNow ticket to escalate an issue, then view its details and status. Microsoft’s IT Helpdesk agent template does exactly this — but it’s an agent a maker configures with a ServiceNow connection, not a turnkey feature of base Copilot. The write is a person clicking through the conversation, not an automated action.
How to set it up
The read-only connectors are a tenant-admin job. For each one:
- In the Microsoft 365 admin center, go to Copilot → Connectors and pick the ServiceNow connector you want — Tickets, Knowledge, or Catalog. These run on Microsoft Graph, not MCP.
- Authenticate to your ServiceNow instance with a service account and configure the crawl (which tables and properties to index).
- Set the access model — Only people with access to this data source (enforces ServiceNow user criteria via Entra ID identity mapping) or Everyone (no permission enforcement; test-only) — and run a full crawl. Schedule full crawls off-peak; incremental crawls only update content, not permission changes.
- Test in Copilot with something read-only: “Show all open incidents assigned to me this week.”
To write to ServiceNow, you build a Copilot Studio agent: a maker needs a Copilot Studio license and message capacity, installs the IT Helpdesk template (or builds an agent from scratch), and adds a ServiceNow connection with user credentials and the instance URL in the agent’s Connect your data settings. It’s a heavier lift, and it’s a different product from the base connector.
The limits that matter
- The connectors are read-only. All three index for grounding and search — they cannot open an incident, update a stage, or submit a catalog request back in ServiceNow. Microsoft’s own docs describe them purely as making records “searchable” and “discoverable.”
- Coverage gaps in the index. The Tickets connector doesn’t index attachments or comments and doesn’t read ACL rules for ticket items — access control there leans on the user fields you configure (
AssignedTo,OpenedBy,ClosedBy, or roles likeitil). Custom widget-based catalog forms aren’t indexed either. - Write-back means building and licensing an agent. The Copilot Studio path can create a ticket and check status, but it requires a Copilot Studio license, message capacity, a ServiceNow connection, and a maker to configure it — and every ticket is a person acting in a live chat.
- No triggers, ever. Neither path fires on a ServiceNow event. Copilot answers when you prompt it; the Copilot Studio agent creates a ticket when a person clicks. An incident can breach SLA or a change can sit unapproved over the weekend and nothing moves on its own. (The May 2026 ServiceNow–Microsoft governance work — AI Control Tower plus Agent 365 — is about overseeing agents, not a new write connector.)
- Session-bound and tenant-scoped. Every action needs a driver in a live session, and access is bounded by your tenant’s licensing and each user’s ServiceNow permissions. There’s no standing watch on your queue.
If you want ServiceNow-adjacent work that runs on its own: Carly
The moment you want something to happen around ServiceNow without you in the chat — a P1 incident summarized and emailed to the on-call owner within minutes, a nudge when a change request stalls unapproved, a Monday backlog digest built and sent, a breached-SLA ticket posted to the right Slack channel — you’ve crossed past what a grounding connector or a hand-built Copilot Studio 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 an incident is created or a change request changes state, Carly reacts — summarizes it, emails the owner, updates the record, posts to Slack — while your laptop is closed.
- Actually reads and writes. Carly can create and update ServiceNow records — open incidents, log work notes, move a change through states — not just surface them in a chat.
- 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 incident opens, draft a status email to the service owner and post a summary in the incidents channel” in plain English; it interviews you and builds it — no admin center, no Copilot Studio, no prompt engineering.
ServiceNow’s programmatic surface is its Table and REST APIs with a scoped service account, so ServiceNow connects to Carly via your own credentials — paste your API key on carlyassistant.com/integrations and Carly can do whatever that access allows. Carly also connects to 200+ tools across 40+ categories natively. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. See integrations.
Microsoft 365 Copilot vs Carly
| Microsoft 365 Copilot (ServiceNow) | Carly | |
|---|---|---|
| Answer questions grounded in ticket/KB data | Yes (connectors, read-only) | Yes |
| Search ServiceNow records in Microsoft 365 | Yes | Via the integration |
| Create / update tickets in ServiceNow | Only via a Copilot Studio agent you build | Yes |
| Submit a catalog request | No (Catalog connector is read-only) | Yes |
| Data reachable | 3 indexed connectors (Tickets/KB/Catalog) | Full API scope |
| Acts on ServiceNow 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 + connectors (+ Copilot Studio for writes) | Describe it in plain English |
| Pricing | Microsoft 365 Copilot license per user | AI agents from $35/mo |
Copilot’s ServiceNow connectors are a grounding layer that pulls ITSM context into your chats. Carly is a teammate that acts on ServiceNow events as they land.
Frequently Asked Questions
Does Microsoft 365 Copilot work with ServiceNow?
Yes, for reading. Microsoft ships three official ServiceNow Copilot connectors — Tickets, Knowledge, and Catalog — that index ticket records, KB articles, and catalog items into Microsoft Graph so Copilot and Microsoft Search can answer questions grounded in your ServiceNow data. They’re read-only: they surface and search records but don’t write anything back.
Can Microsoft 365 Copilot create or update a ServiceNow ticket?
Not through the connectors. Creating a ticket exists only if you build a Copilot Studio agent — for example from Microsoft’s IT Helpdesk template — and give it a ServiceNow connection. That agent can help a user open a ticket and check its status inside a conversation, but it requires a Copilot Studio license, message capacity, and a maker to configure it, and every ticket is a person acting in a live chat.
How do I connect Copilot to ServiceNow?
A tenant admin adds the connector in the Microsoft 365 admin center → Copilot → Connectors → ServiceNow (Tickets, Knowledge, or Catalog), authenticates to the ServiceNow instance with a service account, configures the crawl, sets the access model, and runs a full crawl. These connectors run on Microsoft Graph, not MCP. Full crawls consume ServiceNow API capacity, so schedule them off-peak.
Can Copilot react to a new incident or a stalled change request automatically?
No. Neither the connectors nor a Copilot Studio agent fires on ServiceNow events — Copilot answers when you prompt it, and the agent opens a ticket when someone clicks. For “when a P1 incident opens, email the owner and post to Slack” or “when a change stalls, nudge the approver,” you need a trigger-based assistant like Carly, which reads and writes ServiceNow via its API and runs in the cloud around the clock.
More: Claude + ServiceNow · Best AI agents for productivity · Microsoft 365 Copilot + Salesforce
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."
