Priscilla is an enterprise architect at Fenway Consulting advising a client on which data sources can be surfaced to a Copilot Studio agent through prebuilt Copilot connectors without building custom connectors. The client has four data repositories they want to make available: (1) SharePoint Online document libraries, (2) Microsoft Graph-indexed content from Teams channels, (3) A legacy on-premises Oracle database, (4) ServiceNow incident records. Which of the following correctly identifies which sources are natively supported by prebuilt Copilot connectors?
Select an answer to reveal the explanation.
Short Explanation
You can surface SharePoint Online, Teams/Graph, and ServiceNow through prebuilt Copilot connectors because they're cloud SaaS platforms with accessible APIs. An on-premises Oracle database isn't a SaaS cloud service, so you need custom connector work with an on-premises data gateway bridge.
Full Explanation
Copilot connectors in Microsoft Copilot Studio are designed to surface data from cloud-based enterprise platforms that expose searchable APIs or Microsoft Graph integrations. The Copilot connector gallery grows over time, but understanding which sources are natively supported helps architects set realistic expectations.
The correct identification is that SharePoint Online and Microsoft Teams (via Microsoft Graph) are natively supported by prebuilt Copilot connectors, ServiceNow also has a Copilot connector, and the on-premises Oracle database requires a custom connector or data gateway-based approach. Microsoft provides prebuilt Copilot connectors for Microsoft 365 content surfaces including SharePoint Online (document libraries and sites), Microsoft Teams (including channel messages and meeting content indexed via Microsoft Graph), and major SaaS enterprise platforms including ServiceNow. These connectors handle authentication, search API calls, and result formatting automatically.
The on-premises Oracle database is the exception. On-premises databases are not SaaS cloud services — they run inside private networks and require either a custom connector (using Power Platform's custom connector wizard with an On-Premises Data Gateway to route traffic) or an API layer (such as an Azure API Management façade in front of an on-premises SQL gateway). Neither approach uses a prebuilt Copilot connector.
The claim that all four sources are supported — SharePoint, Teams, Oracle, and ServiceNow all have prebuilt Copilot connectors in the gallery — is incorrect because the on-premises Oracle database does not have a prebuilt Copilot connector. On-premises systems generally require custom integration work.
The claim that only SharePoint Online is supported as a Copilot connector, and all other sources require custom connectors regardless of whether a SaaS version exists, is incorrect because it severely understates the Copilot connector ecosystem. Beyond SharePoint, the gallery includes Teams/Graph, ServiceNow, Salesforce, Confluence, and other enterprise SaaS platforms.
The claim that SharePoint Online and Oracle are supported, Teams content is not available through Copilot connectors, and ServiceNow requires a paid marketplace add-on before its connector appears in the gallery, is incorrect on two counts: Teams content is available through Copilot connectors via Microsoft Graph, and ServiceNow does not require a paid marketplace add-on — its connector is available in the standard Copilot connector gallery.
Exam tip: Copilot connectors are for cloud SaaS platforms with accessible APIs. On-premises systems, legacy databases, and custom APIs require custom connectors or API layers. Know this boundary — it is a recurring exam theme.