ServiceNow Knowledge Connector
Authoritative reference for the Microsoft 365 Copilot ServiceNow Knowledge connector. Content indexed from Microsoft Learn on 2026-04-24.
When to use this skill
- Planning or executing a ServiceNow Knowledge connector deployment
- Explaining prerequisites (service account, ACLs, scoped roles, REST API)
- Helping choose Simple vs Advanced flow, or the right auth method
- Diagnosing indexing failures, missing articles, or permission issues
- Guidance on background scripts that automate ServiceNow-side setup
Scope discipline
Ground answers in the six reference docs listed below. If asked something outside that scope (Catalog/Tickets connectors, unrelated ServiceNow admin topics, unrelated Copilot connectors), say so and offer to look it up separately. Do not invent version-specific behavior, property names, or IP ranges.
Reference map
| Topic |
File |
| Overview, capabilities, limitations |
01-overview |
| ServiceNow admin setup (tables, ACLs, REST API, hierarchical permissions) |
02-admin-setup |
| Grant table access (user, role, row/field-level ACLs, HRSD roles) |
03-grant-table-access |
| Background scripts automation |
04-setup-scripts |
| Deployment in M365 admin center (flow, auth, defaults, schema) |
05-deployment |
| Troubleshooting |
06-troubleshooting |
Core decision points
Simple vs Advanced flow — Default is Simple. Choose Advanced only if any User Criteria uses advanced scripts. Check with:
<ServiceNowURL>/api/now/table/user_criteria?advanced=true&sysparm_limit=1
Auth methods — Federated Auth is recommended (no secret to rotate). OAuth 2.0 and Microsoft Entra ID OIDC are supported. Basic is not recommended for production.
Hierarchical permissions — Evaluate KB (parent) + article (child) user criteria. Requires sys_properties read access. Not available in government/sovereign clouds or dedicated forests.
HRSD scope — If KBs live in sn_hr_core, assign sn_hr_core.content_reader (minimum) or sn_hr_core.admin to the service account. Without it, HR-scoped user criteria silently filter and restricted HR articles can surface to everyone.
Critical gotchas
sys_properties access is required for both flows. Missing it silently defaults to the most restrictive settings — articles without user criteria disappear from search with no error shown.
- Don't apply
snc_read_only to the service account. It blocks writes to oauth_credential needed for token refresh.
getAllUserCriteria() is deprecated. The troubleshooting doc has an alternative script using sn_uc.UserCriteriaLoader.getMatchingCriteria().
- SSO "Logout successfully" loop — fix with private browser sign-in to ServiceNow + separate M365 admin tab.
- OIDC "Assignment required" — turn off in the enterprise app properties to avoid AADSTS501051.
- URL customization is set-once. To change AccessURL format, create a new connection.
- Incremental crawl does not refresh identity. Full crawl required after user/criteria attribute changes.
High-level deployment flow
- ServiceNow admin — configure environment (instance URL, portal URL, attribute mapping, advanced-script check).
- ServiceNow admin — prerequisites (service account, row/field ACLs, REST API for Advanced,
sys_properties access, HRSD roles, IP allowlist).
- Manual path: 03-grant-table-access
- Automated path: 04-setup-scripts
- Verify with the Copilot Connector Checker Tool.
- M365 admin — deploy via M365 admin center > Copilot > Connectors > Gallery > ServiceNow Knowledge. Pick flow, URL, auth, API namespace (if Advanced), staged rollout.
- Validate indexed count against the expected
sys_id count. When status is Ready, test with a known article's sys_id.
How to answer common asks
- "What permissions does the service account need?" → Point to the table in 02-admin-setup and call out Simple-only tables (marked **) and HRSD-scope requirements.
- "Articles missing from search" → Walk through the troubleshooting steps in order: user permissions → Entra mapping (2006 error) → advanced scripts →
sys_properties access → HRSD scope → Access Analyzer.
- "What do the background scripts do?" → Three scripts:
row_level_acl_setup.js (user + role + row ACLs), field_level_acl_setup.js (field-level ACLs), scripted_rest_api_setup.js (REST API for Advanced flow). Idempotent and non-destructive.
- "Which auth method should we use?" → Federated Auth if their ServiceNow version supports OIDC inbound integrations. OAuth 2.0 is the tried-and-true fallback. Never Basic for production.
- "Indexed item count check" → Use the console fetch snippet against
/api/now/table/kb_knowledge?sysparm_fields=sys_id&workflow_state=published and compare to the connector's reported count.
1---2name: servicenow-knowledge-connector3description: |4 Guide for deploying, configuring, and troubleshooting the Microsoft 365 Copilot5 ServiceNow Knowledge connector. Use when user asks to "deploy the ServiceNow6 connector", "set up ServiceNow Knowledge for Copilot", "index ServiceNow KB7 articles", "grant service account table access in ServiceNow", "run the8 background scripts for ServiceNow connector setup", "troubleshoot ServiceNow9 connector issues", "HR articles oversharing", "Advanced vs Simple flow",10 "Federated Auth for ServiceNow connector", or any ServiceNow Knowledge11 connector admin task. Do NOT use for ServiceNow Catalog or ServiceNow Tickets12 connectors — those have separate setup paths.13cowork:14 category: productivity15 icon: Book16metadata:17 source: https://skillmd.com/skills/eriic-builds/servicenow-knowledge-connector18---1920# ServiceNow Knowledge Connector2122Authoritative reference for the Microsoft 365 Copilot ServiceNow Knowledge connector. Content indexed from Microsoft Learn on 2026-04-24.2324## When to use this skill2526- Planning or executing a ServiceNow Knowledge connector deployment27- Explaining prerequisites (service account, ACLs, scoped roles, REST API)28- Helping choose Simple vs Advanced flow, or the right auth method29- Diagnosing indexing failures, missing articles, or permission issues30- Guidance on background scripts that automate ServiceNow-side setup3132## Scope discipline3334Ground answers in the six reference docs listed below. If asked something outside that scope (Catalog/Tickets connectors, unrelated ServiceNow admin topics, unrelated Copilot connectors), say so and offer to look it up separately. Do not invent version-specific behavior, property names, or IP ranges.3536## Reference map3738| Topic | File |39|---|---|40| Overview, capabilities, limitations | [01-overview](references/01-overview.md) |41| ServiceNow admin setup (tables, ACLs, REST API, hierarchical permissions) | [02-admin-setup](references/02-admin-setup.md) |42| Grant table access (user, role, row/field-level ACLs, HRSD roles) | [03-grant-table-access](references/03-grant-table-access.md) |43| Background scripts automation | [04-setup-scripts](references/04-setup-scripts.md) |44| Deployment in M365 admin center (flow, auth, defaults, schema) | [05-deployment](references/05-deployment.md) |45| Troubleshooting | [06-troubleshooting](references/06-troubleshooting.md) |4647## Core decision points4849**Simple vs Advanced flow** — Default is Simple. Choose Advanced only if any User Criteria uses advanced scripts. Check with:50`<ServiceNowURL>/api/now/table/user_criteria?advanced=true&sysparm_limit=1`5152**Auth methods** — Federated Auth is recommended (no secret to rotate). OAuth 2.0 and Microsoft Entra ID OIDC are supported. Basic is not recommended for production.5354**Hierarchical permissions** — Evaluate KB (parent) + article (child) user criteria. Requires `sys_properties` read access. Not available in government/sovereign clouds or dedicated forests.5556**HRSD scope** — If KBs live in `sn_hr_core`, assign `sn_hr_core.content_reader` (minimum) or `sn_hr_core.admin` to the service account. Without it, HR-scoped user criteria silently filter and restricted HR articles can surface to everyone.5758## Critical gotchas59601. **`sys_properties` access is required for both flows.** Missing it silently defaults to the most restrictive settings — articles without user criteria disappear from search with no error shown.612. **Don't apply `snc_read_only` to the service account.** It blocks writes to `oauth_credential` needed for token refresh.623. **`getAllUserCriteria()` is deprecated.** The troubleshooting doc has an alternative script using `sn_uc.UserCriteriaLoader.getMatchingCriteria()`.634. **SSO "Logout successfully" loop** — fix with private browser sign-in to ServiceNow + separate M365 admin tab.645. **OIDC "Assignment required"** — turn off in the enterprise app properties to avoid AADSTS501051.656. **URL customization is set-once.** To change AccessURL format, create a new connection.667. **Incremental crawl does not refresh identity.** Full crawl required after user/criteria attribute changes.6768## High-level deployment flow69701. **ServiceNow admin — configure environment** (instance URL, portal URL, attribute mapping, advanced-script check).712. **ServiceNow admin — prerequisites** (service account, row/field ACLs, REST API for Advanced, `sys_properties` access, HRSD roles, IP allowlist).72 - Manual path: [03-grant-table-access](references/03-grant-table-access.md)73 - Automated path: [04-setup-scripts](references/04-setup-scripts.md)743. **Verify** with the Copilot Connector Checker Tool.754. **M365 admin — deploy** via M365 admin center > Copilot > Connectors > Gallery > ServiceNow Knowledge. Pick flow, URL, auth, API namespace (if Advanced), staged rollout.765. **Validate** indexed count against the expected `sys_id` count. When status is Ready, test with a known article's `sys_id`.7778## How to answer common asks7980- **"What permissions does the service account need?"** → Point to the table in [02-admin-setup](references/02-admin-setup.md) and call out Simple-only tables (marked **) and HRSD-scope requirements.81- **"Articles missing from search"** → Walk through the troubleshooting steps in order: user permissions → Entra mapping (2006 error) → advanced scripts → `sys_properties` access → HRSD scope → Access Analyzer.82- **"What do the background scripts do?"** → Three scripts: `row_level_acl_setup.js` (user + role + row ACLs), `field_level_acl_setup.js` (field-level ACLs), `scripted_rest_api_setup.js` (REST API for Advanced flow). Idempotent and non-destructive.83- **"Which auth method should we use?"** → Federated Auth if their ServiceNow version supports OIDC inbound integrations. OAuth 2.0 is the tried-and-true fallback. Never Basic for production.84- **"Indexed item count check"** → Use the console fetch snippet against `/api/now/table/kb_knowledge?sysparm_fields=sys_id&workflow_state=published` and compare to the connector's reported count.