Teams Connector Prerequisites

User Accounts and Application Permissions

Required Permission	Description
Azure	The installation user account must be able to register, configure and grant Access for an Azure application.
Azure App Permissions	The application configured for the connector must have the following Graph API permissions granted in Microsoft Azure: ChannelMessage.Read.All Directory.Read.All Group.Read.All Member.Read.Hidden User.Read.All Team.ReadBasic.All
Windows	The account used to run the connector must be a local Administrator on the server. This cannot be any of the built-in service accounts (NetworkService Local account used by the service control manager. Not recognized by the security subsystem, so you cannot specify its name in a call to the LookupAccountName function. Has minimum privileges on the local computer and acts as the computer on the network.,local machine, etc.)

Required Permission

Description

Azure

The installation user account must be able to register, configure and grant Access for an Azure application.

Azure App Permissions

The application configured for the connector must have the following Graph API permissions granted in Microsoft Azure:

Windows

Features	Supported	Additional Information
Teams version
Searchable content types	Yes	All content types.
Content Update	Full and Incremental	All BA Insight Connectors support both Full and Incremental crawls, unless noted.
Permission Types	Yes	All BA Insight Connectors support fetch ACLs from the source system Your Source System is the repository where your data is stored (data to be indexed). This repository is managed by applications such as: - SharePoint O365 - SharePoint 2013/16/19 - Documentum - File Share - OpenText - Lotus Notes - etc. Your Source System repository can also be a database such as SQL or Oracle.. To make items *public* or *restricted* to a single user/set of users, you can do so within the Connector Framework.
Required Software	IIS .NET Framework v4.7.2	ASP.Net must be enabled