The Microsoft Teams connector provides connectivity to Microsoft Teams application.
Before using the Microsoft Teams connector, do the following tasks:
roles/secretmanager.viewerroles/secretmanager.secretAccessorA service account is a special type of Google account intended to represent a non-human user that needs to authenticate and be authorized to access data in Google APIs. If you don't have a service account, you must create a service account. The connector and the service account must belong to the same project. For more information, see Creating a service account.
secretmanager.googleapis.com (Secret Manager API)connectors.googleapis.com (Connectors API)To understand how to enable services, see Enabling services.
If these services or permissions have not been enabled for your project previously, you are prompted to enable them when configuring the connector.
A connection is specific to a data source. It means that if you have many data sources, you must create a separate connection for each data source. To create a connection, do the following:
For the list of all the supported regions, see Locations.
Connection names must meet the following criteria:
A node is a unit (or replica) of a connection that processes transactions. More nodes are required to process more transactions for a connection and conversely, fewer nodes are required to process fewer transactions. To understand how the nodes affect your connector pricing, see Pricing for connection nodes. If you don't enter any values, by default the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.
https://login.microsoftonline.com/TENANT_IDENTIFIER/oauth2/v2.0/authorize?prompt=consent.
For example, https://login.microsoftonline.com/9bxxxxxxxxx8112/oauth2/v2.0/authorize?prompt=consent. For the Authorization code authentication type, after creating the connection, you
must perform a few additional steps for configuring authentication. For more information,
see Additional steps after connection creation.
If you selected OAuth 2.0 - Authorization code for
authentication, you must do the following additional steps after creating the connection:
Notice that the Status for the new connector will be Authorization required.
This shows the Edit authorization pane.
If the authorization is successful, the connection status will be set to Active in the Connections page.
If you are using Authorization code authentication type and have made any cofiguration changes in your application,
you must re-authorize your Microsoft Teams connection. To re-authorize a connection, perform the following steps:
This opens the connection details page.
If required, make the necessary changes.
If the authorization is successful, the connection status will be set to Active in the Connections page.
The Microsoft Teams connector can process 30 transactions per minute, per
node for the List Operation for Team Members, Times Off, Channels, and Chats entities, and throttles any transactions beyond this limit.
By default, Integration Connectors allocates 2 nodes (for better availability) for a connection.
For information on the limits applicable to Integration Connectors, see Limits.
All the Integration Connectors provide a layer of abstraction for the objects of the connected application. You can access an application's objects only through this abstraction. The abstraction is exposed to you as entities, operations, and actions.
However, it is possible that a connector doesn't support or have any entities, in which case the
Entities list will be empty.
Selecting an entity from the available list, generates a list of
operations available for the entity. For a detailed description of the operations, see the Connectors task's
entity operations.
However, if a connector doesn't support any of the entity operations, such unsupported
operations aren't listed in the Operations list.
Actions list will be empty.
This section shows how to perform some of the actions operations in this connector.
This example sends a message to a specificChat entity.
Configure connector task dialog, click Actions.SendMessage from the Actions list.Actions operation, and then click
Done.connectorInputPayload and then enter a value similar to the following in the
Default Value field:
{ "TeamId": "cc110f3f-3088-4b4c-b965-e1f3e0a2dfab", "ChannelId": "19%3a7680178ef3ab4b1eb762a7078b990083%40thread.tacv2", "Content": "Hello Guys Lets play" }
This section shows how to perform some of the entity operations in this connector.
This example lists all the records in the Channel Members entity.
Configure connector task dialog, click Entities.Channel Members from the Entity list.List operation, and then click
Done.Id='13b1724a91ce448bad2f1986321fc70f'. You
can also specify multiple filter conditions by using the logic operators. For example, Id='13b1724a91ce448bad2f1986321fc70f' and Inactive=false.This example gets a record with the specified ID from the Chats entity.
Configure connector task dialog, click Entities.Chats from the Entity list.Get operation, and then click
Done.19:1956432abc05491bb26f51f9f7263020@thread.v2 in the Default Value field.
Here, 19:1956432abc05491bb26f51f9f7263020@thread.v2 is a primary key value in the Chats entity.
This example creates a record in the Group Owners entity.
Configure connector task dialog, click Entities.Group Owners from the Entity list.Create operation, and then click Done.connectorInputPayload and then enter a value similar to the following in the
Default Value field:
{ "GroupId": "1356c566-d799-4d49-86c0-b09ab6afdb47", "MemberId": "caf19b29-3af1-4191-b455-16468e6aba4b" }
If the integration is successful, your connector task's connectorOutputPayload field will have a
value similar to the following:
{ "Id": "c3c68bc9a1343242443ca8e5ddcaa0000" }
This example updates the record with the specified ID in the Teams entity.
Configure connector task dialog, click Entities.Teams from the Entity list.Update operation, and then click Done.connectorInputPayload and then enter a value similar to the following in the
Default Value field:
{ "displayName": "My Team Name Changed", "description": "Changed the description for my team" }
id = '953933bc-1024-4ce7-84dc-bae7f24dc2ca' in the Default Value field.
This example deletes the record with the specified ID in the Group Owners entity.
Configure connector task dialog, click Entities.Group Owners from the Entity list.Delete operation, and then click Done.You can use the Terraform resource to create a new connection.
To learn how to apply or remove a Terraform configuration, see Basic Terraform commands.
To view a sample terraform template for connection creation, see sample template.
When creating this connection by using Terraform, you must set the following variables in your Terraform configuration file:
| Parameter name | Data type | Required | Description |
|---|---|---|---|
| default_queue_name | STRING | False | The name of the default queue, may be overridden when executing action. |
| default_topic_name | STRING | False | The name of the default topic, may be overridden when executing action. |
| Bucket | STRING | True | The name of the bucket inside the project where tibjms.jar resides. |
| Object ID | STRING | True | The name of the .jar file inside the bucket. |
After you create the connection, it becomes available in both Apigee Integration and Application Integration. You can use the connection in an integration through the Connectors task.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-06-09 UTC.