Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to connect Microsoft Teams 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 Teams 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 Teams administrator must generate or obtain the following for
integrating with Agentspace Enterprise:
Client ID
Client secret
Tenant ID
Configure the following Microsoft Graph (Application) permissions with the
consent of a Microsoft Teams administrator:
View scopes
TeamSettings.Read.All
GroupMember.Read.All
User.Read.All
Directory.Read.All
ChannelSettings.Read.All
Chat.ReadBasic.All
ChannelMessage.Read.All
Chat.Read.All
Files.Read.All
ChannelMember.Read.All
Create a Microsoft Teams connector
Console
To use the Google Cloud console to sync data from Microsoft Teams 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 Teams to connect your third-party source.
Enter your Microsoft Teams authentication information and click Continue.
Select which entities to sync:
Team
Channel
Channel Message
Channel File
Chat Message
To filter entities out of the index or ensure that they are included in the
index, click Filter. You can specify filters for Root or
Chat Message 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.
Use the following procedure to search through your Microsoft Teams account using federated search.
About federated search
With data federation, Agentspace directly retrieves
information from the third-party data sources using APIs, instead of
copying the data into Agentspace. Using this approach,
you can access external data sources immediately, without waiting for ingestion.
Before you begin
Register Agentspace as an OAuth 2.0 application in
Microsoft Entra ID and collect the following credentials:
Client ID
Client secret
Tenant ID
Configure these Microsoft Graph (Application) permissions with administrator
consent:
On the Select a data source page, scroll or search for Microsoft Teams Federated
to connect your third-party source.
Select a data source
Under Authentication settings:
Enter the Client ID, Client secret, and Tenant ID.
Click Authenticate.
Click Continue.
Enter the authentication information
Entities to search option is automatically skipped because the data
source supports only one entity type.
Select a region for your data source.
Enter a name for your data source.
Configure your data connector
Click Create. Agentspace
creates your data store and
displays your data stores 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. If the Connector state changes from
Creating to Active, the federated search connector is ready to be used.
Query execution
When you enter a search query:
A new data source appears in each user's Agentspace
and should be authorized for each user before using it.
If Microsoft Teams is authorized, Agentspace sends
the query to the Microsoft Teams 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 may 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 (not by Google Cloud's terms).
[[["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,["# Connect Microsoft Teams\n\n\u003cbr /\u003e\n\n| **Preview:** You must be on the allowlist to use this connector.\n\n\u003cbr /\u003e\n\nThis page describes how to connect Microsoft Teams to Agentspace.\nThe connector supports both data ingestion and federated search. See the section\nfor the approach you plan to use:\n\n- [Connect Microsoft Teams (data ingestion)](#ingestion)\n- [Connect Federated Search with Microsoft Teams](#federated-search)\n\nConnect Microsoft Teams (data ingestion)\n----------------------------------------\n\nUse the following procedure to sync data from Microsoft Teams to\nAgentspace.\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### Before you begin\n\n| **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 Teams administrator must generate or obtain the following for\n integrating with Agentspace Enterprise:\n\n - Client ID\n - Client secret\n - Tenant ID\n3. Configure the following Microsoft Graph (Application) permissions with the\n consent of a Microsoft Teams administrator:\n\n View scopes\n - `TeamSettings.Read.All`\n - `GroupMember.Read.All`\n - `User.Read.All`\n - `Directory.Read.All`\n - `ChannelSettings.Read.All`\n - `Chat.ReadBasic.All`\n - `ChannelMessage.Read.All`\n - `Chat.Read.All`\n - `Files.Read.All`\n - `ChannelMember.Read.All`\n\n \u003cbr /\u003e\n\n### Create a Microsoft Teams connector\n\n### Console\n\nTo use the Google Cloud console to sync data from Microsoft Teams 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 Teams** to connect your third-party source.\n\n5. Enter your Microsoft Teams authentication information and click **Continue**.\n\n6. Select which entities to sync:\n\n - **Team**\n - **Channel**\n - **Channel Message**\n - **Channel File**\n - **Chat Message**\n7. To filter entities out of the index or ensure that they are included in the\n index, click **Filter** . You can specify filters for **Root** or\n **Chat Message** 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 frequency](/agentspace/docs/introduction-to-connectors-and-data-stores#sync-frequency).\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\n### Next steps\n\n- To attach your connector to an app, create an app and select your connector\n following the steps in [Create a search app](/agentspace/docs/create-app).\n\n- To preview how your search results appear after your app is set up,\n see [Get 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 Federated Search with Microsoft Teams\n---------------------------------------------\n\nUse the following procedure to search through your Microsoft Teams account using federated search.\n\n\u003cbr /\u003e\n\n| **Preview:** You must be on the allowlist to use this connector.\n\n\u003cbr /\u003e\n\n### About federated search\n\nWith data federation, Agentspace directly retrieves\ninformation from the third-party data sources using APIs, instead of\ncopying the data into Agentspace. Using this approach,\nyou can access external data sources immediately, without waiting for ingestion.\n\n### Before you begin\n\n| **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\n1. Register Agentspace as an OAuth 2.0 application in Microsoft Entra ID and collect the following credentials:\n - Client ID\n - Client secret\n - Tenant ID\n2. Configure these Microsoft Graph (Application) permissions with administrator\n consent:\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\n### Create a federated search connector with Microsoft Teams\n\n### Console\n\nUse the following steps for Google Cloud console to perform federated search through\nMicrosoft Teams 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 add **Create data store**.\n\n4. On the **Select a data source** page, scroll or search for **Microsoft Teams Federated**\n to connect your third-party source.\n\n \u003cbr /\u003e\n\n Select a data source\n\n \u003cbr /\u003e\n\n5. Under **Authentication settings**:\n\n 1. Enter the **Client ID** , **Client secret** , and **Tenant ID**.\n 2. Click **Authenticate**.\n 3. Click **Continue**.\n\n Enter the authentication information\n6. **Entities to search** option is automatically skipped because the data\n source supports only one entity type.\n\n7. Select a **region** for your data source.\n\n8. Enter a name for your data source.\n\n \u003cbr /\u003e\n\n Configure your data connector\n\n \u003cbr /\u003e\n\n9. Click **Create** . Agentspace\n creates your data store and\n displays your data stores on the **Data stores** page.\n\nOnce the data store is created, go to the **Data stores** page and click your\ndata store name to see the status. If the **Connector state** changes from\n**Creating** to **Active**, the federated search connector is ready to be used.\n\n\u003cbr /\u003e\n\n### Query execution\n\nWhen you enter a search query:\n\n- A new data source appears in each user's Agentspace\n and should be authorized for each user before using it.\n\n- If Microsoft Teams is authorized, Agentspace sends\n the query to the Microsoft Teams API.\n\n- Agentspace blends the results with those from other\n sources and displays them.\n\n### Data 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\nyour identity. If multiple federated search data sources are enabled, the\nquery may be 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 (not by Google Cloud's terms).\n| **Note:** An LLM may 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 history may also be included in what is sent to the third-party backends."]]
