Home
Home
German Version
Support
Impressum
25.2 Release ►

Start Chat with Collection

    Main Navigation

    • Preparation
      • Connectors
      • Create an InSpire VM on Hyper-V
      • Initial Startup for G7 appliances
      • Setup InSpire G7 primary and Standby Appliances
    • Datasources
      • Configuration - Atlassian Confluence Connector
      • Configuration - Best Bets Connector
      • Configuration - Box Connector
      • Configuration - COYO Connector
      • Configuration - Data Integration Connector
      • Configuration - Documentum Connector
      • Configuration - Dropbox Connector
      • Configuration - Egnyte Connector
      • Configuration - GitHub Connector
      • Configuration - Google Drive Connector
      • Configuration - GSA Adapter Service
      • Configuration - HL7 Connector
      • Configuration - IBM Connections Connector
      • Configuration - IBM Lotus Connector
      • Configuration - Jira Connector
      • Configuration - JVM Launcher Service
      • Configuration - LDAP Connector
      • Configuration - Microsoft Azure Principal Resolution Service
      • Configuration - Microsoft Dynamics CRM Connector
      • Configuration - Microsoft Exchange Connector
      • Configuration - Microsoft File Connector (Legacy)
      • Configuration - Microsoft File Connector
      • Configuration - Microsoft Graph Connector
      • Configuration - Microsoft Loop Connector
      • Configuration - Microsoft Project Connector
      • Configuration - Microsoft SharePoint Connector
      • Configuration - Microsoft SharePoint Online Connector
      • Configuration - Microsoft Stream Connector
      • Configuration - Microsoft Teams Connector
      • Configuration - Salesforce Connector
      • Configuration - SCIM Principal Resolution Service
      • Configuration - SemanticWeb Connector
      • Configuration - ServiceNow Connector
      • Configuration - Web Connector
      • Configuration - Yammer Connector
      • Data Integration Guide with SQL Database by Example
      • Indexing user-specific properties (Documentum)
      • Installation & Configuration - Atlassian Confluence Sitemap Generator Add-On
      • Installation & Configuration - Caching Principal Resolution Service
      • Installation & Configuration - Mindbreeze InSpire Insight Apps in Microsoft SharePoint On-Prem
      • Mindbreeze InSpire Insight Apps in Microsoft SharePoint Online
      • Mindbreeze Web Parts for Microsoft SharePoint
      • User Defined Properties (SharePoint 2013 Connector)
      • Whitepaper - Mindbreeze InSpire Insight Apps in Salesforce
      • Whitepaper - Web Connector - Setting Up Advanced Javascript Usecases
    • Configuration
      • CAS_Authentication
      • Configuration - Alerts
      • Configuration - Alternative Search Suggestions and Automatic Search Expansion
      • Configuration - Back-End Credentials
      • Configuration - Chinese Tokenization Plugin (Jieba)
      • Configuration - CJK Tokenizer Plugin
      • Configuration - Collected Results
      • Configuration - CSV Metadata Mapping Item Transformation Service
      • Configuration - Entity Recognition
      • Configuration - Exporting Results
      • Configuration - External Query Service
      • Configuration - Filter Plugins
      • Configuration - GSA Late Binding Authentication
      • Configuration - Identity Conversion Service - Replacement Conversion
      • Configuration - InceptionImageFilter
      • Configuration - Index-Servlets
      • Configuration - InSpire AI Chat and Insight Services for Retrieval Augmented Generation
      • Configuration - Item Property Generator
      • Configuration - Japanese Language Tokenizer
      • Configuration - Kerberos Authentication
      • Configuration - Management Center Menu
      • Configuration - Metadata Enrichment
      • Configuration - Metadata Reference Builder Plugin
      • Configuration - Mindbreeze Proxy Environment (Remote Connector)
      • Configuration - Personalized Relevance
      • Configuration - Plugin Installation
      • Configuration - Principal Validation Plugin
      • Configuration - Profile
      • Configuration - Reporting Query Logs
      • Configuration - Reporting Query Performance Tests
      • Configuration - Request Header Session Authentication
      • Configuration - Shared Configuration (Windows)
      • Configuration - Vocabularies for Synonyms and Suggest
      • Configuration of Thumbnail Images
      • Cookie-Authentication
      • Documentation - Mindbreeze InSpire
      • I18n Item Transformation
      • Installation & Configuration - Outlook Add-In
      • Installation - GSA Base Configuration Package
      • JWT Authentication
      • Language detection - LanguageDetector Plugin
      • Mindbreeze Personalization
      • Mindbreeze Property Expression Language
      • Mindbreeze Query Expression Transformation
      • SAML-based Authentication
      • Trusted Peer Authentication for Mindbreeze InSpire
      • Using the InSpire Snapshot for Development in a CI_CD Scenario
      • Whitepaper - AI Chat
      • Whitepaper - Create a Google Compute Cloud Virtual Machine InSpire Appliance
      • Whitepaper - Create a Microsoft Azure Virtual Machine InSpire Appliance
      • Whitepaper - Create AWS 10M InSpire Appliance
      • Whitepaper - Create AWS 1M InSpire Appliance
      • Whitepaper - Create AWS 2M InSpire Appliance
      • Whitepaper - Create Oracle Cloud 10M InSpire Application
      • Whitepaper - Create Oracle Cloud 1M InSpire Application
      • Whitepaper - MMC_ Services
      • Whitepaper - Natural Language Question Answering (NLQA)
      • Whitepaper - SSO with Microsoft AAD or AD FS
      • Whitepaper - Text Classification Insight Services
    • Operations
      • Adjusting the InSpire Host OpenSSH Settings - Set LoginGraceTime to 0 (Mitigation for CVE-2024-6387)
      • app.telemetry Statistics Regarding Search Queries
      • CIS Level 2 Hardening - Setting SELinux to Enforcing mode
      • Configuration - app.telemetry dashboards for usage analysis
      • Configuration - Usage Analysis
      • Deletion of Hard Disks
      • Handbook - Backup & Restore
      • Handbook - Command Line Tools
      • Handbook - Distributed Operation (G7)
      • Handbook - Filemanager
      • Handbook - Indexing and Search Logs
      • Handbook - Updates and Downgrades
      • Index Operating Concepts
      • Inspire Diagnostics and Resource Monitoring
      • Provision of app.telemetry Information on G7 Appliances via SNMPv3
      • Restoring to As-Delivered Condition
      • Whitepaper - Administration of Insight Services for Retrieval Augmented Generation
    • User Manual
      • Browser Extension
      • Cheat Sheet
      • iOS App
      • Keyboard Operation
    • SDK
      • api.chat.v1beta.generate Interface Description
      • api.v2.alertstrigger Interface Description
      • api.v2.export Interface Description
      • api.v2.personalization Interface Description
      • api.v2.search Interface Description
      • api.v2.suggest Interface Description
      • api.v3.admin.SnapshotService Interface Description
      • Debugging (Eclipse)
      • Developing an API V2 search request response transformer
      • Developing Item Transformation and Post Filter Plugins with the Mindbreeze SDK
      • Development of a Query Expression Transformer
      • Development of Insight Apps
      • Embedding the Insight App Designer
      • Java API Interface Description
      • OpenAPI Interface Description
    • Release Notes
      • Release Notes 20.1 Release - Mindbreeze InSpire
      • Release Notes 20.2 Release - Mindbreeze InSpire
      • Release Notes 20.3 Release - Mindbreeze InSpire
      • Release Notes 20.4 Release - Mindbreeze InSpire
      • Release Notes 20.5 Release - Mindbreeze InSpire
      • Release Notes 21.1 Release - Mindbreeze InSpire
      • Release Notes 21.2 Release - Mindbreeze InSpire
      • Release Notes 21.3 Release - Mindbreeze InSpire
      • Release Notes 22.1 Release - Mindbreeze InSpire
      • Release Notes 22.2 Release - Mindbreeze InSpire
      • Release Notes 22.3 Release - Mindbreeze InSpire
      • Release Notes 23.1 Release - Mindbreeze InSpire
      • Release Notes 23.2 Release - Mindbreeze InSpire
      • Release Notes 23.3 Release - Mindbreeze InSpire
      • Release Notes 23.4 Release - Mindbreeze InSpire
      • Release Notes 23.5 Release - Mindbreeze InSpire
      • Release Notes 23.6 Release - Mindbreeze InSpire
      • Release Notes 23.7 Release - Mindbreeze InSpire
      • Release Notes 24.1 Release - Mindbreeze InSpire
      • Release Notes 24.2 Release - Mindbreeze InSpire
      • Release Notes 24.3 Release - Mindbreeze InSpire
      • Release Notes 24.4 Release - Mindbreeze InSpire
      • Release Notes 24.5 Release - Mindbreeze InSpire
      • Release Notes 24.6 Release - Mindbreeze InSpire
      • Release Notes 24.7 Release - Mindbreeze InSpire
      • Release Notes 24.8 Release - Mindbreeze InSpire
      • Release Notes 25.1 Release - Mindbreeze InSpire
      • Release Notes 25.2 Release - Mindbreeze InSpire
    • Security
      • Known Vulnerablities
    • Product Information
      • Product Information - Mindbreeze InSpire - Standby
      • Product Information - Mindbreeze InSpire
    Home

    Path

    Sure, you can handle it. But should you?
    Let our experts manage the tech maintenance while you focus on your business.
    See Consulting Packages

    Installation and Configuration
    Microsoft Teams Connector

    InstallationPermanent link for this heading

    Before installing the Microsoft Teams connector, make sure that Mindbreeze Server is installed. To install or update the connector, please use the Mindbreeze Management Center.

    Plugin installation via Mindbreeze Management CenterPermanent link for this heading

    To install the plug-in, open the Mindbreeze Management Center. Select “Configuration” from the menu pane on the left-hand side. Then navigate to the “Plugins” tab. Under “Plugin Management,” select the appropriate zip file and upload it by clicking “Upload.” This automatically installs or updates the connector, as the case may be. In the process, the Mindbreeze services are restarted.

    Configuring MindbreezePermanent link for this heading

    Select the “Advanced” installation method for configuration.

    Configuring the indexPermanent link for this heading

    To create a new index, navigate to the “Indices” tab and click the “Add new index” icon in the upper right corner.


    Change the display name of the created index as necessary.

    Configuring the data sourcePermanent link for this heading

    Add a new data source by clicking the “Add new custom source” icon at the top right. Select the category “Microsoft Teams” and configure the data source according to your needs.

    Creating the Application in AzurePermanent link for this heading

    In order to crawl Microsoft Teams with the Microsoft Teams Connector, a new app must first be created that has the permissions to read Microsoft Teams. This app can be created on portal.azure.com.

    Navigate to Azure Active Directory -> App registrations and click on the button "New Registration" to register a new app:

    After you have created the app, you have to create a secret so that the crawler can actually log in:

    When creating the Secret, you can set the expiration time. If you select "Never", the secret will never expire, which is easy to maintain, but involves some security risks. We recommend a runtime of 1-2 years, so that the Secret is changed regularly.

    After that you can copy the secret. When you leave the page, you can no longer view the secret, so make sure you enter the secret directly into the Mindbreeze configuration (see next section).

    Now you have to give the app the required permissions. To do this, navigate to "App permissions". The Microsoft Teams Crawler needs the following Application Permissions in Microsoft Graph:

    • ChannelMember.Read.All
    • ChannelMessage.Read.All
    • Group.Read.All
    • User.Read.All

    After you have given the app the permission, you have to grant "admin consent". Use the button "Grant admin consent for <MyInstance>" for this:

    Request access to protected APIsPermanent link for this heading

    Certain endpoints that we need for indexing Microsoft Teams are so-called "protected APIs". For these a request has to be made to Microsoft to get permission to use them. You can read more about this here: https://docs.microsoft.com/en-us/graph/teams-protected-apis

    The request form can be found here: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR1ax4zKyZjVBmutzKVo1pVtUQ1VJMlNTNUdJV1FKTzVZSVU4MlMwTTdOTSQlQCN0PWcu

    Access requests are reviewed every Wednesday and permissions are granted every Friday except during major holiday weeks in the US.

    You can fill out this form roughly as follows:

    • Your email address and any others you want to list as an owner (semicolon separated)
      • The email address(es) of the O365 admin(s).
    • May we contact you about your app's use of non-protected APIs? (E.g., reliability issues, advanced notice of breaking changes, throttling, etc)
      • No
    • Publisher name
      • Mindbreeze GmbH
    • App name
      • Mindbreeze Microsoft Teams Connector
    • App id(s) to enable application permissions for
      • App Id of the app created for the connector.
    • What does your app do? Why does it exist? (2-3 sentences explaining to an admin who has never heard of your app what it is and why they want it)
      • Mindbreeze InSpire is a software system enabling the search for information objects in a corporate context ("Enterprise Search Software"). Information objects can be any kind of information contained in structured, partially structured or unstructured storage systems. For most use cases these information objects will be document files in a file system, e-mails in an e-mail box system or documents in a document management system or archive.
        Microsoft Teams is one of many supported data sources and Mindbreeze InSpire needs to build an index of the channel messages for the customers.
    • Why does your app need read access to all messages in the tenant? (If you don't, you don't need protected APIs)
      • As stated above, Mindbreeze InSpire needs to fetch all messages from channels to build an index that the customer can search in. This index also contains many other data sources.
    • Data retention - select one of these options:
      • It is obvious to any admin installing this app that it will make a copy Microsoft Teams messages.
    • What are the tenant ID's that this app needs to run in? (semicolon-separated. Put "all" if you're writing software for other organizations to use.)
      • Tenant ID of your O365 tenant
    • Does your organization own all those tenants? (if no, your answer above should be "all", or you should get the tenant owner to submit the request)
      • Yes

    Section „Connection Settings“Permanent link for this heading

    In the "Connection Settings" area you can define your Microsoft Teams instance to be indexed. The following options are available:

    Setting

    Description

    Graph Service Root (Advanced Settings)

    The endpoint/URL of the Microsoft Graph API. By default, "https://graph.microsoft.com". Change this setting only if you are using a national (non-international) Microsoft Cloud. A list of all available national Microsoft Graph endpoints can be found below.

    Azure AD Url (Advanced Settings)

    The endpoint/URL to the Azure Active Directory. By default, "https://login.microsoftonline.com". Change this setting only if you are using a national (non-international) Microsoft Cloud. A list of all available national Azure AD endpoints can be found below.

    Trust all SSL certificates (Advanced Settings)

    Allows the use of non-secured connections, for example for test systems.  Must not be enabled in production.

    Tenant ID

    The Tenant ID of your Microsoft 365 instance. This can be found on the overview page of the app in Azure

    App ID

    The Application (Client) ID of the app created in Azure

    Client Secret

    The Credential created in the Network tab, which contains the created Client Secret

    SharePoint Online Category Instance

    Attachments of Teams messages are stored in Microsoft SharePoint Online. If a reference from Microsoft Teams to the files in Microsoft SharePoint Online is to be created, you must create the Microsoft SharePoint Online Crawler in the same index as the Microsoft Teams Crawler and enter its category instance here.

    To set up the SharePoint Online Connector, see Configuration - Microsoft SharePoint Online Connector

    Crawler Thread Count

    Number of threads used for indexing

    Log All Requests
    (Advanced Settings)

    If this option is activated, all requests against the Graph API are written to a logfile. Should only be activated for troubleshooting.

    Synthesized Title Length
    (Advanced Settings)

    If a message in Microsoft Teams has no subject, the content of the message is used as the title of the Mindbreeze document. This value determines the maximum length of titles that are set in this way. If the title is longer, it will be truncated with ...

    Max Retries
    (Advanced Settings)

    The maximum number of retries that will be attempted when the server sends certain throttling responses (e.g. 429).

    Enable Delta Crawl
    (Advanced Settings)

    As long as this option is activated, the crawler only retrieves all messages from all Microsoft Teams channels during the first crawl run; afterwards, only the changes in the channels are retrieved, which significantly improves performance.

    Only deactivate this option if there is an inconsistency between the index and the actual messages in Microsoft Teams.

    [Deprecated] Exclusively Use Beta API
    (Advanced Settings)

    This option is deprecated and should not be enabled. If this option is deactivated, make sure that the permissions of the app are correct (see Section 2.2.1 Creating the Application in Azure), because the /beta API sometimes allows API queries despite insufficient permissions.

    If this option is enabled, the crawler will only use the /beta API. Otherwise, the /beta API is only used to fetch all teams, and the /v1.0 API is used for all other requests.

    Available national Microsoft Graph endpointsPermanent link for this heading

    Microsoft Graph global service

    https://graph.microsoft.com

    Microsoft Graph for US Government L4

    https://graph.microsoft.us

    Microsoft Graph for US Government L5 (DOD)

    https://dod-graph.microsoft.us

    Microsoft Graph China operated by 21Vianet

    https://microsoftgraph.chinacloudapi.cn

    Available national Azure AD endpointsPermanent link for this heading

    Azure AD (global service)

    https://login.microsoftonline.com

    Azure AD for US Government

    https://login.microsoftonline.us

    Azure AD China operated by 21Vianet

    https://login.chinacloudapi.cn

    Content SettingsPermanent link for this heading

    Excluded Team Name Patterns

    Regular expressions that can be used to specify which teams should be excluded. The regex matches the display name of the team.

    Included Team Name Patterns

    Regular Expressions that can be used to specify which teams should be crawled. If this option is left empty, all teams will be crawled. The regex matches the display name of the team.

    Index Private Teams

    If this option is enabled, private teams will be indexed.

    Index Archived Teams

    If this option is enabled, archived teams will be indexed.

    Excluded Team IDs
    (Advanced Settings)

    This option allows you to specify the IDs of the teams that should be excluded.

    Included Team IDs
    (Advanced Settings)

    This option allows you to specify the IDs of the teams to be indexed.

    [Deprecated] Configuring the principal resolution servicePermanent link for this heading

    The Teams Principal Resolution Service has been deprecated. Use Microsoft Azure Principal Resolution Service instead. (For completeness, the following sections describe the configuration of the deprecated Teams Principal Resolution Service).

    Select “Advanced Settings” to configure the following settings.

    Enable the option “Enforce ACL Evaluation.”

    Scroll down and add a new service in the "Services" section by clicking on "Add Service". Select "Microsoft Teams Principal Resolution Service" and assign a display name.

    Section „Connection Settings“Permanent link for this heading

    In the "Connection Settings" area you can define your Microsoft Teams instance to be indexed. The following options are available:

    Tenant ID

    The Tenant ID of your Microsoft 365 instance. This can be found on the overview page of the app in Azure

    App ID

    The Application (Client) ID of the app created in Azure

    Client Secret

    The Credential created in the Network tab, which contains the created Client Secret

    Crawler Thread Count

    Number of threads used for processing groups

    Log All Requests
    (Advanced Settings)

    If this option is activated, all requests against the Graph API are written to a logfile. Should only be activated for troubleshooting.

    Enable Delta Update
    (Advanced Settings)

    As long as this option is enabled, the Principal Service will only fetch all groups from Microsoft Teams during the first update, after which only the changes to the groups will be fetched, which significantly improves performance.

    Only deactivate this option if an inconsistency has arisen between the Principal Service and the actual groups in Microsoft Teams.

    [Deprecated] Exclusively Use Beta API
    (Advanced Settings)

    This option is deprecated and should not be enabled. If this option is deactivated, make sure that the permissions of the app are correct (see Section 2.2.1 Creating the Application in Azure), because the /beta API sometimes allows API queries despite insufficient permissions.

    If this option is enabled, the Principal Resolution Service uses the /beta API. Otherwise, the /v1.0 API is used.

    Download PDF

    • Configuration - Microsoft Teams Connector

    Content

    • Installation
    • Configuring Mindbreeze

    Download PDF

    • Configuration - Microsoft Teams Connector