> ## Documentation Index > Fetch the complete documentation index at: https://docs.getthread.com/llms.txt > Use this file to discover all available pages before exploring further. # Install the Teams Companion App > Connect the Thread Companion App to your own Microsoft Teams tenant: authorise Microsoft 365, upload the app manifest, add it to a setup policy, and add it to a team. The **Teams Companion App** puts your service threads inside Microsoft Teams for your own technicians — notifications when you're assigned a thread, ticket updates in-line in a channel, and full thread management without leaving Teams. This guide connects the Companion App to **your own** Microsoft 365 tenant, for your service team. To deploy a Teams app to a **customer's** tenant, use the [Teams Service App](/messenger/create-teams-app) instead — they are different apps with different audiences. ## What you get * **Notifications** when you're assigned as owner of a thread. * **Custom Flows** that route threads to a Teams channel you choose. * **Real-time updates** — replies, internal notes, status and board changes, as they happen in your PSA or Inbox. * **Thread management** — collaborate internally, sync notes to the PSA, reply to the customer, and change status, priority, board and contact from Teams. ## Before you start You need administrator credentials for your company's Microsoft 365 environment, and access to the [Microsoft Teams admin center](https://admin.teams.microsoft.com). ## Connect Microsoft 365 In the Thread Admin Panel, go to **Integrations → Microsoft 365 & Teams app**. Microsoft 365 and Teams app tile on the Integrations page of the Thread Admin Panel Connect button on the Microsoft 365 and Teams integration panel Connect with Microsoft Teams option in the Thread Admin Panel Sign in to your company's Microsoft 365 environment with administrator credentials. Microsoft Online sign-in page requesting administrator credentials Review the permissions the app requests and click **Accept**. The full list is documented in the [Microsoft Teams app permissions reference](/security-billing/microsoft-teams-app-permissions). Microsoft consent screen listing the permissions requested by the Thread Teams app After consent you're redirected to the Teams app setup instructions. Teams app setup instructions shown after granting Microsoft consent ## Upload the app to your tenant Download the Teams Companion App manifest from the setup instructions screen. Upload it as a **`.zip`** — do not extract it. In the same browser session, sign in to [admin.teams.microsoft.com](https://admin.teams.microsoft.com) and go to **Teams Apps → Manage Apps**. Manage Apps page under Teams Apps in the Microsoft Teams admin center Choose to upload a custom app, then select the `.zip` you downloaded. Upload custom app dialog in the Teams admin center with a zip file selected Confirmation that the Thread app was added to the Teams tenant ## Add it to a setup policy Uploading makes the app available; a setup policy installs it for your users. Close the **New app added** prompt, then go to **Teams Apps → Setup Policies** and select **Global (Org-wide default)**. Global org-wide default setup policy in the Teams admin center Under **Installed apps**, click **Add apps**, search for "Thread", select it and click **Add**. Add apps panel with the Thread app selected for the setup policy You can pin Thread to the Teams app bar, though it isn't required. Click **Save**. Pinned apps list in the Teams setup policy with Thread added The app appears faster in Teams on the web. Give the desktop client up to **24 hours**. ## Add the app to a team Adding the app to a team is what lets you route threads to that team's channels and interact with the bot from inside it. In the Teams admin center, go to **Teams Apps → Manage Apps** and search for the Thread Companion App you just installed. Thread Companion App located in the Manage Apps list Type the team you want to add it to. The **team** matters more than the channel — when you build a Flow in Thread you can create new channels under that team from inside Thread. The bot **cannot** interact with private channels. Decide whether to announce Thread in the channel, then click **Save**. The integration now shows as connected on the [Admin Panel integrations page](https://admin.getthread.com/dashboard/integrations). Thread Admin Panel integrations page showing the Teams integration connected You can now create a Flow in Inbox and get notified about those threads in Teams. Thread notification for a service thread posted in a Microsoft Teams channel ## FAQ Repeat **Add the app to a team** for each team you want. You only need to add the app to a given team once — after that the bot can reach any public channel created under it, and you can create new channels under that team from Thread's Flow builder. Check your permissions in the Teams admin center. The permissions Thread requests, and why, are listed in the [Microsoft Teams app permissions reference](/security-billing/microsoft-teams-app-permissions). ## Next step Choose [which ticket updates post to a channel](/companion-apps/choose-which-ticket-updates-post-to-channel) so the channel stays useful rather than noisy. ## Related topics - [Install the Slack Companion App](/companion-apps/install-the-slack-companion-app.md) - [How Notifications Work for your Team](/notifications/how-will-notifications-work-internally.md) - [How to Use the Slack Companion App for Service Teams](/companion-apps/how-to-use-the-slack-companion-app-for-service-teams.md)