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:
Also, the application should be granted to use Microsoft Teams Protected API on the tenant. This is a manual process which is described in this article: https://docs.microsoft.com/en-us/graph/teams-protected-apis The process may take up to a week. |
| Windows | The account used to run the connector must be a local Administrator on the server and cannot be any of the built-in service accounts (NetworkService,local machine, etc.) |
Connector Features and Requirements
| 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. 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 |