{"id":15867,"date":"2023-10-24T08:32:38","date_gmt":"2023-10-24T15:32:38","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/?p=15867"},"modified":"2023-10-24T08:32:38","modified_gmt":"2023-10-24T15:32:38","slug":"anatomy-of-a-microsoft-graph-connector","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/anatomy-of-a-microsoft-graph-connector\/","title":{"rendered":"Anatomy of a Microsoft Graph connector"},"content":{"rendered":"

In our recent post<\/a>, we introduced Microsoft Graph connectors and how they help bring your organization’s content into Microsoft Graph and Semantic Index for Copilot to appear across Microsoft 365 experiences, making it easy for users in your organization to easily discover and share content relevant to them while staying in the flow of work.<\/p>\n

Now, let’s go under the hood to better understand the building blocks of a Microsoft Graph connector.<\/p>\n

Key components of a Microsoft Graph connector<\/h2>\n

First, let\u2019s break things down \u2013 Microsoft Graph connectors are responsible for three things:<\/p>\n

    \n
  1. Creating an external connection to your data sources<\/li>\n
  2. Defining schema for the external content<\/li>\n
  3. Managing external content that\u2019s imported to Microsoft 365<\/li>\n<\/ol>\n

    The following diagram illustrates these responsibilities:<\/p>\n

    <\/p>\n

    An external connection<\/strong> defines the source of external content that you\u2019ll ingest into Microsoft 365. It contains information such as:<\/p>\n