Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to connect Microsoft Outlook to Agentspace. The connector
supports both data ingestion and federated search. See the section for the
approach you plan to use:
Use the following procedure to sync data from Microsoft Outlook to
Agentspace.
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:
Set up access control for your data source. For information
about setting up access control, see
Use data source access control.
A Microsoft Outlook administrator must generate or obtain the
following for integrating with Agentspace:
Client ID
Client secret
Tenant ID
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
Console
To use the Google Cloud console to sync data from Microsoft Outlook to
Agentspace, follow these steps:
In the Google Cloud console, go to the Agentspace page.
On the Select a data source page, scroll or search for Microsoft Outlook to connect your third-party source.
Enter your Microsoft Outlook authentication information and click Continue.
Select which entities to sync:
Mail
Calendar
Contact
Mail Attachment
To filter entities out of the index or ensure that they are included in the
index, click Filter.
Specify filters to include or exclude entities.
Click Save.
Click Continue.
Select the Sync frequency for Full sync
and the Incremental sync frequency for Incremental data sync.
For more information, see
Sync schedules.
If you want to schedule separate full syncs of entity and identity data,
expand the menu under Full sync and then select Custom options.
Setting separate schedules for full entity sync and full identity sync.
Select a region for your data store.
Enter a name for your data connector.
Click Create. Agentspace creates your data store and
displays your data stores on the Data stores page.
To check the status of your ingestion, go to the Data stores page and
click your connector name to see details about it on its Data page. The
Connector state changes from Creating to Running when it starts
synchronizing data. When ingestion is complete, the state changes to
Active to indicate that the connection to your data source is set up and
awaiting the next scheduled synchronization.
Depending on the size of your data, ingestion can take several
minutes or several hours.
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.
On the Select a data source page, select Outlook Federated to connect
your third-party data source.
Under Authentication settings:
Enter the Client ID, Client secret, and Tenant ID.
Click Login.
Click Continue.
Login using the copied OAuth 2.0 credentials
Select the entities you want to include.
Select from Mail, Calendar, and Contact.
Click Continue.
Select the Microsoft Outlook entities you want to include
Select a region for your data source.
Enter a name for your data source.
Click Create. Agentspace creates your data store and displays
it on the Data stores page.
After 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, the Agentspace source
management panel lists it as one of your data sources. If you haven't
previously authorized Agentspace, you can't select the
data source. Instead, an Authorize button appears.
Authorize Agentspace Enterprise to access your new data source
To initiate the authorization flow:
Click Authorize. You are redirected to the Outlook authorization server.
Sign in to your account.
Click Grant access. After granting access, you are redirected back to
Agentspace to complete the authorization flow.
Agentspace 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:
Agentspace sends your search query to the Microsoft Graph API.
Agentspace 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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[],[],null,["This page describes how to connect Microsoft Outlook to Agentspace. The connector\nsupports both data ingestion and federated search. See the section for the\napproach you plan to use:\n\n- [Connect Microsoft Outlook (data ingestion)](#ingestion)\n- [Connect Microsoft Outlook with federated search](#federated-search) (Preview)\n\nConnect Microsoft Outlook (data ingestion) Use the following procedure to sync data from Microsoft Outlook to Agentspace.\n\n\u003cbr /\u003e\n\nAfter you set up your data source and import data the first time, the data store\nsyncs data from that source at a frequency that you select during setup.\n\n\nBefore you begin **Note:** To enforce data source access control and secure data in Google Agentspace, ensure that you have [configured your identity provider](/agentspace/docs/configure-identity-provider).\n\nBefore setting up your connection:\n\n1. Set up access control for your data source. For information\n about setting up access control, see\n [Use data source access control](/agentspace/docs/identity).\n\n2. A Microsoft Outlook administrator must generate or obtain the\n following for integrating with Agentspace:\n\n - Client ID\n - Client secret\n - Tenant ID\n3. Configure the following scopes:\n\n View scopes\n - `Calendars.Read`\n - `Calendars.ReadBasic.All`\n - `Contacts.Read`\n - `Mail.Read`\n - `Mail.ReadBasic`\n - `Mail.ReadBasic.All`\n - `User.Read.All`\n - `User.ReadBasic.All`\n\n \u003cbr /\u003e\n\nCreate a Microsoft Outlook connector \n\nConsole\n\nTo use the Google Cloud console to sync data from Microsoft Outlook to\nAgentspace, follow these steps:\n\n1. In the Google Cloud console, go to the **Agentspace** page.\n\n [Agentspace](https://console.cloud.google.com/gen-app-builder/)\n2. In the navigation menu, click **Data stores**.\n\n3. Click add **Create data store**.\n\n4. On the **Select a data source** page, scroll or search for **Microsoft Outlook** to connect your third-party source.\n\n5. Enter your Microsoft Outlook authentication information and click **Continue**.\n\n6. Select which entities to sync:\n\n - **Mail**\n\n - **Calendar**\n\n - **Contact**\n\n - **Mail Attachment**\n\n7. To filter entities out of the index or ensure that they are included in the\n index, click **Filter**.\n\n\n Specify filters to include or exclude entities.\n\n \u003cbr /\u003e\n\n8. Click **Save**.\n\n9. Click **Continue**.\n\n10. Select the **Sync frequency** for **Full sync**\n and the **Incremental sync frequency** for **Incremental data sync** .\n For more information, see\n [Sync schedules](/agentspace/docs/introduction-to-connectors-and-data-stores#sync-schedules).\n\n If you want to schedule separate full syncs of entity and identity data,\n expand the menu under **Full sync** and then select **Custom options**.\n Setting separate schedules for full entity sync and full identity sync.\n11. Select a region for your data store.\n\n12. Enter a name for your data connector.\n\n13. Click **Create** . Agentspace creates your data store and\n displays your data stores on the **Data stores** page.\n\n14. To check the status of your ingestion, go to the **Data stores** page and\n click your connector name to see details about it on its **Data** page. The\n **Connector state** changes from **Creating** to **Running** when it starts\n synchronizing data. When ingestion is complete, the state changes to\n **Active** to indicate that the connection to your data source is set up and\n awaiting the next scheduled synchronization.\n\n Depending on the size of your data, ingestion can take several\n minutes or several hours.\n\n\u003cbr /\u003e\n\nNext steps\n\n- To attach your connector to an app, create an app and select your connector\n following the steps in\n [Create a search app](/agentspace/docs/create-app).\n\n- To preview how your search results appear after your app is set up, see [Get\n search results](/agentspace/docs/preview-search-results).\n\n- To enable alerts for the data store, see [Configure alerts for third-party data stores](/agentspace/docs/configure-periodic-data-alerts).\n\nConnect Microsoft Outlook with federated search **Preview:** You must be on the allowlist to use federated search.\nUse the following procedure to search your Microsoft Outlook account using federated search.\n\n\u003cbr /\u003e\n\nBefore you begin **Note:** To enforce data source access control and secure data in Google Agentspace, ensure that you have [configured your identity provider](/agentspace/docs/configure-identity-provider).\n\nPerform the following steps before connecting to your Microsoft Outlook data\nstore using federated search.\n\n1. Register Agentspace as an OAuth 2.0 application in Microsoft\n Entra ID. Copy the following credentials:\n\n - Client ID\n - Client secret\n - Tenant ID\n2. Configure the following Microsoft Graph application permissions with the\n consent of a Microsoft Outlook administrator:\n\n |----------------|-----------|---------------------|\n | Permission | Type | Description |\n | Mail.Read | Delegated | Read user mail |\n | Calendars.Read | Delegated | Read user calendars |\n | Contacts.Read | Delegated | Read user contacts |\n\n3. Add the following URLs as web callback URLs:\n\n - `https://vertexaisearch.cloud.google.com/console/oauth/default_oauth.html`\n - `https://vertexaisearch.cloud.google.com/oauth-redirect`\n\nCreate a federated search connector with Outlook\n\nUse the following steps for Google Cloud console to perform federated search through\nMicrosoft Outlook from Agentspace.\n\n1. In the Google Cloud console, go to the **Agentspace** page.\n\n [Agentspace](https://console.cloud.google.com/gen-app-builder/)\n2. In the navigation menu, click **Data stores**.\n\n3. Click **Create data store**.\n\n4. On the **Select a data source** page, select **Outlook Federated** to connect\n your third-party data source.\n\n5. Under **Authentication settings**:\n\n 1. Enter the **Client ID, Client secret** , and **Tenant ID**.\n\n 2. Click **Login**.\n\n 3. Click **Continue**.\n\n\n Login using the copied OAuth 2.0 credentials\n\n \u003cbr /\u003e\n\n6. Select the entities you want to include.\n\n 1. Select from **Mail** , **Calendar** , and **Contact**.\n\n 2. Click **Continue**.\n\n\n Select the Microsoft Outlook entities you want to include\n\n \u003cbr /\u003e\n\n7. Select a region for your data source.\n\n8. Enter a name for your data source.\n\n9. Click **Create** . Agentspace creates your data store and displays\n it on the **Data stores** page.\n\nAfter the data store is created, go to the **Data stores** page and click your\ndata store name to see the status. When the **Connector state** changes from\n**Creating** to **Active**, the federated search connector is ready to be used.\n\nUser authorization\n\nAfter creating a federated search data store, the Agentspace source\nmanagement panel lists it as one of your data sources. If you haven't\npreviously authorized Agentspace, you can't select the\ndata source. Instead, an **Authorize** button appears.\nAuthorize Agentspace Enterprise to access your new data source\n\nTo initiate the authorization flow:\n\n1. Click **Authorize**. You are redirected to the Outlook authorization server.\n\n2. Sign in to your account.\n\n3. Click **Grant access**. After granting access, you are redirected back to\n Agentspace to complete the authorization flow.\n Agentspace obtains the access token and uses it to access the\n Microsoft Outlook search.\n\nQuery execution\n\nAfter you authorize Microsoft Outlook, when you enter a search query:\n\n1. Agentspace sends your search query to the Microsoft Graph API.\n\n2. Agentspace blends the results with those from other sources and\n displays them.\n\nData handling\n\nWhen using third-party federated search, your query string is sent to the\nthird-party search backend. These third parties may associate queries with your\nidentity. If multiple federated search data sources are enabled, the query might\nbe sent to all of them.\n\nOnce the data reaches the third-party system, it is governed by that system's\nterms of service and privacy policies.\n| **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's sent to third-party search backends."]]