Skip to main content

Microsoft 365 Copilot Data Source

The Microsoft 365 Copilot connector enables you to interact with Microsoft Graph External Connections API, allowing you to retrieve information about external connections, schemas, and items that have been ingested into Copilot. Microsoft 365 Copilot uses external connections to index and make searchable data from external sources, enabling users to query and access information from various systems through Copilot's AI-powered interface. This connector is particularly useful for applications that need to monitor Copilot external connection status, verify ingested data, analyze connection metadata, or audit what data has been made available to Copilot users. Follow the instructions below to create a new data flow that ingests data from a Microsoft 365 Copilot source in Nexla.
copilot_api.png

Microsoft 365 Copilot

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Microsoft 365 Copilot connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Microsoft 365 Copilot instance, and click Next; or, create a new Microsoft 365 Copilot credential for use in this flow.

  3. Microsoft 365 Copilot sources can be configured to ingest data from any valid Microsoft Graph External Connections API endpoint. Configuration options available for Microsoft 365 Copilot sources allow them to be fully customized to suit any use case—including using chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

    First, select the method that will be used for calls to the Microsoft 365 Copilot API from the Method pulldown menu. The most common methods are:

    • GET: For retrieving data from the API
    • POST: For sending data to the API or triggering actions
    • PUT: For updating existing data
    • PATCH: For partial updates to existing data
    • DELETE: For removing data

API Endpoint URL​

  1. Enter the URL of the Microsoft 365 Copilot API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Microsoft Graph API endpoints typically follow the pattern https://graph.microsoft.com/v1.0/external/connections or https://graph.microsoft.com/beta/external/connections for beta features.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. Microsoft Graph API uses versioned endpoints (v1.0 for stable APIs, beta for preview features).

Path to Data​

Optional

If only a subset of the data that will be returned by API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when API responses contain metadata, pagination information, or other data that you don't need for your analysis.

For example, when a request call is used to fetch a list of items, the API will typically return an array of records, along with metadata, in the response. By entering the path to the relevant data, you can configure Nexla to treat each element of the returned array as a record.

Path to Data is essential when API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.value[*] to access an array of items within a value object).

    • For responses in XML format, enter the XPath that points to the object/array containing relevant data. XPath uses slash notation (e.g., /response/value/item to access item elements).

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers are often required for API versioning, content type specifications, or custom authentication requirements.

    You do not need to include any headers already present in the credentials. Common headers like Authorization, Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration. Microsoft Graph API uses standard OAuth 2.0 Bearer token authentication.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Microsoft 365 Copilot data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.