Microsoft Graph Connectors for Microsoft Copilot for Microsoft 365

Microsoft Graph connectors provide a platform for you to ingest your unstructured, line-of-business data into Microsoft Graph, so that Copilot for Microsoft 365 can reason over the entirety of your enterprise content. Content ingested through Graph connectors is added to the Microsoft Graph; this unlocks semantic understanding of your users' prompts in Copilot for Microsoft 365. However, Graph connectors are not limited to Copilot for Microsoft 365. Graph connector content participates in other Microsoft 365 intelligent experiences like Microsoft Search, Context IQ, and the Microsoft 365 app.

In this article, you will learn how your Graph connector content participates in Copilot for Microsoft 365 and how to configure your custom Graph connections for Copilot for Microsoft 365.

This infographic summarizes how Microsoft Graph connectors make your data available to Microsoft 365 intelligent experiences

Watch the overview

How Microsoft Graph connector content surfaces in Copilot for Microsoft 365

By using Microsoft Graph connectors to ingest your external content into Microsoft Graph, your users can use Copilot for Microsoft 365 to find, summarize, and learn from your line-of-business data through natural language prompts.

A screenshot of Graph connectors in Copilot for Microsoft 365

In addition, users can hover over in-text citations in Copilot for Microsoft 365's response to get a preview of the external item referenced.

A screenshot of hovering over a Graph connectors response in Copilot for Microsoft 365

If users desire to dive deeper into the referenced content, they can click on one of the reference links at the bottom of the response.

A screenshot of Graph connectors reference list in Copilot for Microsoft 365

Create your own custom Microsoft Graph connection

You can use the Microsoft Graph connectors APIs to build custom Microsoft Graph connections that index content from line-of-business data sources into Microsoft Graph. You can use the Microsoft Graph connectors APIs to create and manage external Microsoft Graph connections, define and register the schema of external data types, ingest external data items into Microsoft Graph, and sync external groups.

Configuring your custom Microsoft Graph connection for Copilot for Microsoft 365

To make sure that Copilot for Microsoft 365 uses your content effectively:

  • Apply semantic labels. Semantic labels help Copilot for Microsoft 365 interpret the semantic meaning of your schema. Apply as many of them to your schema as applicable. The iconUrl, title, and url labels must be applied for content to surface in Copilot.
  • Add a urlToItemResolver in activitySettings when you create your connection. A urlToItemResolver enables the platform to detect when users share URLs from your external content with each other. Copilot for Microsoft 365 has a higher likelihood of displaying content that has been shared with that user.
  • Add user activities on your items. For a list of supported activity types, see externalActivity. Items that have more activities are boosted in importance.
  • Provide meaningful descriptions in the description property when creating connections. Rich descriptions improve the likelihood of displaying content in Copilot.

In addition, search administrators should ensure that your Graph Connector connections are enabled for inline results, using the following steps.

  • Open the Admin Center, go to Search & intelligence > Customizations > Verticals and select the All vertical.
  • Select Manage connector result. Ensure that Show results inline is selected and that the connections that you want to enable for Search and Copilot are checked.

Semantic Labels and Property Labels in Copilot for Microsoft 365

As stated earlier, it is recommended that you apply as many semantic labels to your schema as applicable. This is because your end-users can use semantic labels as part of their prompt in Copilot for Microsoft 365. For example, an end-user can ask Copilot for all of the files that were last modified within the last week. If the lastModifiedDateTime semantic label is not applied to your schema, then Copilot for Microsoft 365 will not be able to return the expected result to that user.

The searchable property label is the most important with respect to Copilot for Microsoft 365. It defines which properties can be searched against. If you would like your users' prompts in Copilot for Microsoft 365 to match content stored in certain properties, then you should make those properties searchable.

See also