Microsoft Copilot and ServiceNow integrate through three distinct paths in 2026, and only two of them can change anything in ServiceNow. The first-party Microsoft 365 Copilot connectors for ServiceNow (Tickets, Knowledge, and Catalog) are read-only: they index records into Microsoft Graph so Copilot can answer questions and cite the source, but they cannot open an incident, update a change request, or submit a catalog request. To write back, you build a Copilot Studio agent that holds a governed ServiceNow connection, or you connect a Copilot Studio agent to ServiceNow's own Model Context Protocol (MCP) server. Which path you choose depends on whether you need to read, write, or orchestrate multi-step work.

This guide is written for the IT directors, service-desk owners, and Power Platform architects who have been handed a "connect Copilot to ServiceNow" mandate and need a straight answer on what each path does, what it costs, and where the governance line sits. We map the read-only connectors, the Copilot Studio write path, and the new ServiceNow MCP servers side by side, then give you a decision you can defend in an architecture review.

Key Takeaways

• There are three integration paths, not one. Read-only Microsoft 365 Copilot connectors, a Copilot Studio agent that reads and writes, and ServiceNow's own MCP servers each solve a different job.
• The official connectors are read-only. The Tickets, Knowledge, and Catalog connectors index ServiceNow into Microsoft Graph for grounding and search; none of them write back to ServiceNow.
• Writing to ServiceNow means building an agent. Creating or updating an incident requires a Copilot Studio agent with a ServiceNow connection, or an MCP tool call, driven by a person in the conversation.
• ServiceNow's out-of-the-box MCP servers reached general availability on September 10, 2026. They cover ITSM, ITOM, CMDB, and SPM and work with Copilot, Claude, and Gemini as clients.
• MCP does not bypass ServiceNow access control. Every tool call runs in the authenticated user's context and respects existing ServiceNow ACLs and roles.
• Connector and tool calls are billed as agent actions. Each action is 5 Copilot Credits, so a write-capable agent's run rate scales with how often it touches ServiceNow, not with headcount.

The short answer: which path do you need?

Pick the path that matches the verb. If users only need to find and read ServiceNow data inside Copilot, use the connectors. If they need Copilot to do something in ServiceNow, build an agent.

• Read-only grounding and search: Deploy the Microsoft 365 Copilot ServiceNow connectors so Copilot can answer ticket, knowledge, and catalog questions with the record cited.
• Create and update records: Build a Copilot Studio agent with a ServiceNow connection (OAuth 2.0) so a user can open an incident, check its status, or order a catalog item in chat.
• Multi-step, workflow-heavy orchestration: Connect a Copilot Studio agent to a ServiceNow MCP server so the agent can call purpose-built ITSM, CMDB, or change tools that run ServiceNow's own logic server-side.
• Deflect-then-escalate support: Use the Copilot Studio to ServiceNow handoff pattern so a virtual agent deflects what it can and transfers the rest to a ServiceNow live agent with the transcript intact.

What can the Microsoft 365 Copilot ServiceNow connectors actually do?

Microsoft ships three first-party ServiceNow connectors in the Microsoft 365 admin center, and all three are Microsoft Graph connectors that index ServiceNow content on a schedule. They make records discoverable inside Copilot and Microsoft Search; they do not make them writable, and they do not run live queries.

The Tickets connector indexes the ServiceNow task table and its children, including incident, change_request, problem, service catalog request (sc_request), request item (sc_req_item), and the related task tables, so Copilot can answer "What is the status of the high-priority network outage ticket?" with a citation, per Microsoft's ServiceNow Tickets connector documentation. The Knowledge connector indexes KB articles, including comments, attachments, reusable knowledge blocks, and accordion content, so Copilot can answer "How do I set up a VPN connection?" from your own runbooks, according to Microsoft's ServiceNow Knowledge connector documentation. The Catalog connector indexes catalog items so users can discover orderable services.

Two limits matter in practice. First, these connectors are read-only and batch-indexed, so they cannot answer live aggregate questions like "how many P1 incidents are open right now" and cannot write anything back. Second, permission trimming depends on configuration: the Only people with access to this data source model enforces ServiceNow user criteria through Microsoft Entra ID identity mapping, while the Everyone option applies no permission enforcement and is intended only for isolated testing. Incremental crawls refresh content; only a full crawl updates identity and permission changes.

Can Copilot create or update a ServiceNow ticket?

Not through the connectors. The only supported write path is a Copilot Studio agent that holds a ServiceNow connection. You create a ServiceNow agent in Copilot Studio, authenticate with OAuth 2.0, and the agent can then read and write structured tables such as Incident, letting a user escalate an issue and then view its status in the same conversation. Microsoft's IT Helpdesk agent template demonstrates exactly this pattern, but it is an agent a maker configures, not a turnkey feature of base Copilot.

The important design nuance: the write is a person clicking through the conversation, not an unattended automation. The agent proposes an action, the user confirms, and the record is created or updated under governed credentials. If you want work that runs on a schedule or system event instead of a chat turn, that belongs in a workflow, which is a different build decision covered in our guide on Copilot Studio agent flows versus Power Automate.

What is the ServiceNow MCP server, and when should you use it?

The Model Context Protocol (MCP) is an open standard that lets a Copilot Studio agent discover and call a server's tools as governed actions, and it is the fast-moving part of this integration. ServiceNow introduced its MCP Server Console in the Zurich release and, on September 10, 2026, made out-of-the-box MCP servers for ITSM, ITOM, CMDB, and SPM generally available for AI clients including Microsoft Copilot, according to ServiceNow's MCP launch announcement.

The reason to prefer MCP for complex work is that the tools are purpose-built around outcomes rather than raw table access. ServiceNow's own change-management benchmark reported roughly 52% lower client-side cost, 72% faster execution, and about 6.5 times fewer output tokens than hitting the Table API directly, because the domain logic runs server-side on the Now Platform. Two practical requirements: in Copilot Studio you must turn on generative orchestration to use MCP, per Microsoft's MCP documentation, and note that Microsoft does not publish a first-party ServiceNow MCP connector, so you connect to ServiceNow's hosted server or a custom one. If MCP is new to your team, start with our deeper walkthrough on connecting Copilot Studio agents to your systems with MCP.

The connector tells Copilot what ServiceNow knows; the agent lets Copilot act on it; MCP lets it act well at scale.

Choosing between these is rarely a one-time call, and the wrong pick shows up later as either a useless read-only bot or a brittle web of custom connectors. BabyBots runs fixed-fee Copilot and ServiceNow integration assessments that map your service-desk use cases to the right path (connector, agent, or MCP) and hand back a governed architecture, not a slide deck.

Three ways to connect Copilot and ServiceNow compared

Microsoft 365 Copilot connectors

• Best for: Grounding and search over tickets, knowledge, and catalog data.
• Direction: Read-only; indexed into Microsoft Graph on a schedule.
• Who builds it: A Microsoft 365 tenant admin in the admin center.
• Governance: Honors ServiceNow user criteria via Entra ID identity mapping when permission trimming is enabled.

Copilot Studio agent with a ServiceNow connection

• Best for: Creating and updating incidents, requests, and catalog orders in chat.
• Direction: Read and write, driven by a user turn.
• Who builds it: A Copilot Studio maker with a connection authenticated via OAuth 2.0.
• Governance: Runs under the connection's credentials and Power Platform data-loss-prevention policy.

ServiceNow MCP server

• Best for: Multi-step, workflow-heavy ITSM, CMDB, and change work.
• Direction: Read and write through purpose-built tools that run ServiceNow logic server-side.
• Who builds it: A maker who adds the MCP tool in Copilot Studio with generative orchestration on.
• Governance: Every tool call runs in the authenticated user's context and respects ServiceNow ACLs and roles.

How do you hand off from a Copilot agent to a ServiceNow live agent?

For contact-center scenarios, Copilot Studio supports a handoff to ServiceNow Virtual Agent and escalation to a ServiceNow live agent. The pattern uses an Azure Function as a relay between ServiceNow Bot Interconnect and the Copilot Studio Direct Line API, and it requires ServiceNow Virtual Agent and Bot Interconnect enabled on a supported release, per Microsoft's Copilot Studio ServiceNow handoff documentation. The design goal is deflect-first: the agent resolves what it can from knowledge, and only transfers the conversation, with context preserved, when a human is genuinely needed. Done well, that lowers ticket volume instead of adding a step in front of it.

What does a ServiceNow and Copilot Studio agent cost to run?

Agents that touch ServiceNow are billed in Copilot Credits, and the key line item is the agent action. Each connector or tool call an agent makes is an agent action billed at 5 Copilot Credits, per Microsoft's Copilot Studio billing rates. Credits cost $0.01 each on pay-as-you-go, or $200 per month for a 25,000-credit capacity pack, according to Microsoft's Copilot Studio licensing guidance. Premium Power Platform connectors, including the ServiceNow connector, carry no separate license fee in Copilot Studio; the cost shows up as credit consumption on each call.

One meaningful offset: for employee-facing (business-to-employee) scenarios, internal agent usage by a user who holds a Microsoft 365 Copilot license is included and does not draw credits, subject to fair-use limits. That makes an internal IT-helpdesk agent for licensed staff far cheaper to run than a customer-facing one. For a full breakdown of how credits stack, see our guide on what AI agents actually cost in Microsoft 365.

Frequently Asked Questions

Can Microsoft 365 Copilot create a ServiceNow ticket?

Not through the standard connectors. The Tickets, Knowledge, and Catalog connectors are read-only and index data into Microsoft Graph for grounding and search. To create or update a ServiceNow record, you build a Copilot Studio agent with a ServiceNow connection, or connect the agent to a ServiceNow MCP server, and the write happens when a user confirms the action in the conversation.

Do the ServiceNow Copilot connectors work in real time?

No. They are synced Microsoft Graph connectors that crawl ServiceNow on a schedule, so Copilot answers from an index rather than a live query. That means they cannot reliably answer dynamic or aggregated questions such as how many incidents are open at this moment. Incremental crawls refresh content; only a full crawl updates identity and permission changes.

Is there an official Microsoft ServiceNow MCP connector for Copilot Studio?

No. Microsoft does not publish a first-party ServiceNow MCP connector. ServiceNow provides its own out-of-the-box MCP servers for ITSM, ITOM, CMDB, and SPM, generally available since September 10, 2026, and you connect a Copilot Studio agent to those (or to a custom MCP server) with generative orchestration enabled.

Do I need a premium license to use the ServiceNow connector in Copilot Studio?

There is no separate premium-connector license fee in Copilot Studio; standard, premium, and custom connectors are included in the Copilot Studio entitlement. The real cost is credit consumption: each connector call is an agent action billed at 5 Copilot Credits, with credits priced at $0.01 pay-as-you-go or $200 per 25,000-credit pack.

Does connecting Copilot to ServiceNow bypass ServiceNow permissions?

It should not, if configured correctly. The connectors enforce ServiceNow user criteria through Entra ID identity mapping when permission trimming is enabled, and ServiceNow's MCP servers run every tool call in the authenticated user's context and respect existing ACLs and roles. The risk is misconfiguration, such as choosing the Everyone access model, which applies no permission enforcement and is meant only for isolated testing.

Which integration path should we start with?

Start with the read-only connectors if the immediate goal is letting staff find ticket and knowledge answers inside Copilot, because it is an admin task with no custom build. Move to a Copilot Studio agent when users need to create or update records, and add a ServiceNow MCP server when the work is multi-step and workflow-heavy enough that purpose-built tools pay for themselves.

Where this is heading

The direction of travel is clear: ServiceNow is positioning itself as the governed system of action while AI clients like Copilot become the conversational front end, and MCP is the connective tissue that lets the two meet without brittle point-to-point code. For enterprises, that means the integration question is shifting from "can Copilot read ServiceNow" to "which actions do we let an agent take, and under whose identity." The organizations that win will be the ones that pick the right path per use case and wire governance in from the first agent, not after the first incident.

Map your Copilot and ServiceNow integration in one working session

If you run both Microsoft 365 and ServiceNow and need a defensible plan, book a BabyBots Copilot and ServiceNow integration assessment. In a single working session we inventory your top service-desk use cases, match each to the right path (connector, Copilot Studio agent, or MCP server), and hand back a governed architecture with the licensing and credit math already worked out.

Sources

• Microsoft Learn - ServiceNow Tickets connector overview
• Microsoft Learn - ServiceNow Knowledge connector overview
• Microsoft Learn - Hand off to ServiceNow (Copilot Studio)
• Microsoft Learn - Extend your agent with Model Context Protocol
• Microsoft Learn - Use Power Platform connectors as tools in Copilot Studio
• Microsoft Learn - Copilot Studio billing rates and management
• Microsoft - Copilot Studio licensing guidance
• ServiceNow - Out-of-the-box MCP Servers for Copilot, Claude, and Gemini (GA September 10, 2026)
• ServiceNow - MCP Server Console release notes (Zurich)