Connect Microsoft Outlook

This page describes how to connect Microsoft Outlook to Agentspace Enterprise. The connector supports both data ingestion and federated search. See the section for the approach you plan to use:

• Connect Microsoft Outlook (data ingestion)
• Connect Microsoft Outlook with federated search

Connect Microsoft Outlook (data ingestion)

Use the following procedure to sync data from Microsoft Outlook to Agentspace Enterprise.

After you set up your data source and import data the first time, the data store syncs data from that source at a frequency that you select during setup.

Before you begin

Before setting up your connection:

1. Set up access control for your data source. For information about setting up access control, see Use data source access control.

2. A Microsoft Outlook administrator must generate or obtain the following for integrating with Agentspace Enterprise:

   • Client ID
   • Client secret
   • Tenant ID

3. Configure the following scopes:

   View scopes

   • Calendars.Read
   • Calendars.ReadBasic.All
   • Contacts.Read
   • Mail.Read
   • Mail.ReadBasic
   • Mail.ReadBasic.All
   • User.Read.All
   • User.ReadBasic.All

Create a Microsoft Outlook connector

Next steps

• To attach your connector to an app, create an app and select your connector following the steps in Create a search app.

• To preview how your search results appear after your app is set up, see Get search results. If you used third-party access control, see Preview results for apps with third-party access control.

• To enable alerts for the data store, see Configure alerts for third-party data stores.

Connect Microsoft Outlook with federated search

Use the following procedure to search your Microsoft Outlook account using federated search.

About federated search

You can use federated search connectors to send your queries to third-party search APIs instead of ingesting and indexing all data into Agentspace Enterprise. Using this approach, you can access external data sources immediately, without waiting for ingestion.

However, this approach might not be suitable in all scenarios. While federated search is quick to set up, it has the following limitations:

• Compared to indexed data, federated search may deliver lower-quality results.
• Federated search may introduce higher latency, because it depends on the third-party search API.
• Not all connectors support federated search.

Before you begin

Perform the following steps before connecting to your Microsoft Outlook data store using federated search.

1. Register Agentspace Enterprise as an OAuth 2.0 application in Microsoft Entra ID. Copy the following credentials:

   • Client ID
   • Client secret
   • Tenant ID

2. Configure the following Microsoft Graph application permissions with the consent of a Microsoft Outlook administrator:

   Permission	Type	Description
   Mail.Read	Delegated	Read user mail
   Calendars.Read	Delegated	Read user calendars
   Contacts.Read	Delegated	Read user contacts

3. Add the following URLs as web callback URLs:

   • https://vertexaisearch.cloud.google.com/console/oauth/default_oauth.html
   • https://vertexaisearch.cloud.google.com/oauth-redirect

Create a federated search connector with Outlook

Use the following steps for Google Cloud console to perform federated search through Microsoft Outlook from Agentspace Enterprise.

1. In the Google Cloud console, go to the Agentspace page.

   Agentspace

2. In the navigation menu, click Data stores.

3. Click Create data store.

4. On the Select a data source page, select Outlook Federated to connect your third-party data source.

5. Under Authentication settings:

   1. Enter the Client ID, Client secret, and Tenant ID.

   2. Click Login.

   3. Click Continue.

      

6. Select the entities you want to include.

   1. Select from Mail, Events, and Contacts.

   2. Click Continue.

      

7. Select a region for your data source.

8. Enter a name for your data source.

9. Click Create. Agentspace Enterprise creates your data store and displays it on the Data stores page.

Once the data store is created, go to the Data stores page and click your data store name to see the status. When the Connector state changes from Creating to Active, the federated search connector is ready to be used.

User authorization

After creating a federated search data store, you see it listed as one of the data sources in your Agentspace Enterprise source management panel. If you haven't previously authorized Agentspace Enterprise, then you can't select the data source. Instead, an Authorize button appears.

To initiate the authorization flow:

1. Click Authorize. You are redirected to the Outlook authorization server.

2. Sign in to your account.

3. Click Grant access. After granting access, you are redirected back to Agentspace Enterprise to complete the authorization flow. Agentspace Enterprise obtains the access token and uses it to access the Microsoft Outlook search.

Query execution

After you authorize Microsoft Outlook, when you enter a search query:

1. Agentspace Enterprise sends your search query to the Microsoft Graph API.

2. Agentspace Enterprise blends the results with those from other sources and displays them.

Data handling

When using third-party federated search, your query string is sent to the third-party search backend. These third parties may associate queries with your identity. If multiple federated search data sources are enabled, the query might be sent to all of them.

Once the data reaches the third-party system, it is governed by that system's terms of service and privacy policies.

Note: An LLM might rewrite your query before it is sent. This rewritten query can incorporate information from your session-based query history. As a result, parts of that query history might also be included in the query that is sent to third-party search backends.