An IT operations team wants their Copilot Studio agent to answer employee questions using content from their ServiceNow knowledge base. The agent must only surface articles from knowledge bases marked as 'Public' in ServiceNow, and answers must include a citation link back to the source article. The connection must authenticate using the ServiceNow service account credentials stored in the organization's key vault. Which configuration sequence correctly implements this integration?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Plugging ServiceNow into a Copilot Studio agent is like connecting a specialized reference library — you need the right library card (custom connector with auth), tell it which shelves to search (Public knowledge base filter), and make sure the librarian stamps every answer with the book's location (citation link). A custom connector is the enterprise-grade way to bring non-native data sources into an agent's knowledge layer with proper auth and filtering. That's the only path that checks all three boxes here.
Full explanation below image
![Portrait infographic (1536x2048) showing ServiceNow knowledge integration with Copilot Studio. Left column: 'ServiceNow Knowledge Base' icon with stacked article cards labeled 'Public' (green) and 'Private' (grey with X). Center: a 'Custom Connector' box with a key icon representing key vault authentication and an arrow labeled 'Public Filter' pointing to ServiceNow. Right column: 'Copilot Studio Agent' with a knowledge source plug-in icon and a chat bubble showing an answer with a 'Source: ServiceNow Article [link]' citation. Top annotation: 'Key Vault Credentials' feeding into the Custom Connector auth section. Color scheme: ServiceNow green and Microsoft blue on white. Clean enterprise integration diagram.](/media/microsoft/ab-620/AB-620-e6-q005-infographic.webp)
Full Explanation
Copilot Studio supports multiple knowledge source types: built-in connectors (SharePoint, websites, Dataverse), and custom connectors for external enterprise systems like ServiceNow and SAP. When integrating with ServiceNow, a custom connector is required because ServiceNow is not a natively supported built-in knowledge source type in Copilot Studio.
Option B is correct because it follows the proper integration sequence. A custom connector is built to interface with the ServiceNow Knowledge Management API, configured to authenticate using credentials retrieved from the key vault (either through environment variables or Azure Key Vault references in the connector definition). The custom connector is then registered as a knowledge source in the agent. The knowledge base filter is configured to restrict results to articles in knowledge bases with a 'Public' visibility value — this is a query parameter passed to the ServiceNow API. Citation generation is enabled in the knowledge source settings, which causes the agent to include source article URLs in its responses. This satisfies all three requirements: correct knowledge source type, visibility filtering, and citation links.
Option A is incorrect because ServiceNow is not a SharePoint Online knowledge source. These are fundamentally different systems with different APIs. Configuring a ServiceNow connection using SharePoint settings would fail at connection time and would not produce the intended filtering behavior. Key vault references are not used as SharePoint site URLs.
Option C is incorrect because while a Power Automate flow can retrieve ServiceNow data, this approach bypasses Copilot Studio's native knowledge source framework. The agent would not generate citations automatically from flow-returned JSON arrays — citation generation is a feature of the knowledge source layer, not the message layer. This solution would require custom citation formatting logic and lacks the semantic search capabilities that a registered knowledge source provides.
Option D is incorrect because Azure API Management is an API gateway, not a knowledge source endpoint that Copilot Studio's knowledge framework can semantically search. Registering an APIM endpoint as an HTTP knowledge source would require the endpoint to conform to the expected knowledge source response schema. Additionally, Copilot Studio's built-in Basic Auth setting does not support key vault credential references — custom connectors are the mechanism for enterprise-grade credential management.
Exam tip: For non-native enterprise systems (ServiceNow, SAP, Workday), the answer is almost always a custom connector registered as a knowledge source. Know that citation generation is a knowledge source setting, not a topic or message setting. Key vault credentials feed into custom connector authentication configurations, not into agent settings directly.