This connector is built with the Elastic connector framework and is available as a self-managed connector client.
Availability and prerequisitesedit
This connector is available as a self-managed connector client. To use this connector, satisfy all connector client prerequisites.
This connector is in technical preview and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Technical preview features are not subject to the support SLA of official GA features.
To use this connector as a connector client, use the Microsoft Teams tile from the connectors list Customized connector workflow.
For additional operations, see Using connectors.
Connecting to Microsoft Teamsedit
To connect to Microsoft Teams you need to create an Azure Active Directory application and service principal that can access resources. Follow these steps:
- Go to the Azure portal and sign in with your Azure account.
- Navigate to the Azure Active Directory service.
- Select App registrations from the left-hand menu.
- Click on the New registration button to register a new application.
- Provide a name for your app, and optionally select the supported account types (e.g., single tenant, multi-tenant).
- Click on the Register button to create the app registration.
- After the registration is complete, you will be redirected to the app’s overview page. Take note of the Application (client) ID value, as you’ll need it later.
- Scroll down to the API permissions section and click on the "Add a permission" button.
- In the "Request API permissions pane, select "Microsoft Graph" as the API.
Select the following permissions:
Files.Read.All(Delegated and Application)
Calendars.Read(Delegated and Application)
- Click on the Add permissions button to add the selected permissions to your app.
- Click on the Grant admin consent button to grant the required permissions to the app. This step requires administrative privileges. If you are not an admin, you need to request the admin to grant consent via their Azure Portal.
Under the "Certificates & Secrets" tab, go to Client Secrets.
Generate a new client secret and keep a note of the string under the
After completion, use the following configuration parameters to configure the connector.
The following configuration fields are required:
Unique identifier for your Azure Application, found on the app’s overview page. Example:
String value that the application uses to prove its identity when requesting a token, available under the
Certificates & Secretstab of your Azure application menu. Example:
Unique identifier for your Azure Active Directory instance, found on the app’s overview page. Example:
Username for your Azure Application. Example:
Password for your Azure Application. Example:
Refer to Content extraction.
Documents and syncsedit
The connector syncs the following objects and entities:
- Files bigger than 10 MB won’t be extracted.
- Permissions are not synced. All documents indexed to an Elastic deployment will be visible to all users with access to that Elastic Deployment.
Basic sync rules are identical for all connectors and are available by default.
Advanced Sync Rulesedit
Advanced sync rules are not available for this connector in the present version.
The connector framework enables operators to run functional tests against a real data source. Refer to Connector testing for more details.
To perform E2E testing for the Teams connector, run the following command:
$ make ftest NAME=microsoft_teams
For faster tests, add the
make ftest NAME=microsoft_teams DATA_SIZE=small
- Messages in one-on-one chats for Chat with Self users are not fetched via Graph APIs. Therefore, these messages won’t be indexed into Elasticsearch.
Refer to Known issues for a list of known issues for all connectors.
Framework and sourceedit
This connector is included in the Elastic connector framework.
View the source code for this connector (branch 8.11, compatible with Elastic 8.11).