---
title: "Add the portal to Microsoft Teams"
description: "Download a branded Teams app package for a client and upload it to their Teams admin center, so their people open the portal inside Teams."
url: "https://support.outpostplatform.com/client-portal/teams/"
product: "depot"
type: "how-to"
status: "draft"
ai_summary: "MSP plan. Settings > Client portal > Microsoft Teams: sign in through the Outpost sign-in service (a popup) or your own Entra app registration (silent). Download package per client or for every client, then upload it in the Teams admin center under Teams apps > Manage apps > Upload new app. Payment and remote access pages open in the browser."
availability:
  plans: ["msp"]
  permission: "clientportal:manage"
  preview: false
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/client-portal/teams.md"
license: "CC BY 4.0"
---

# Add the portal to Microsoft Teams

The Teams app puts the client portal in Microsoft Teams, as a personal app and
as a tab you can add to a channel or chat. People see the same portal, with
the same permissions, without leaving Teams. This page shows how to choose
how the app signs people in, build the package, and install it for a client.

## Before you begin

- You need `clientportal:manage`.
- Someone at the client can upload a custom app in their Teams admin center,
  or you manage their tenant.
- Pages that take payment or start a remote session always open in the
  browser.

## Choose how the app signs in

1. Select **Settings** > **Client portal**, then **Microsoft Teams**.
2. Under **Sign-in**, choose:
   - **The Outpost sign-in service**: nothing to register. People sign in once
     through a popup the first time they open the tab.
   - **Your own Entra app registration**: signs people in silently. Enter the
     **Application (client) id** and the **Application ID URI**, such as
     `api://portal.example.com/<app-id>`. The URI must be on your portal's
     address.
3. Optionally, in **Name in Teams**, enter the app's name, up to 30 characters.
   Empty uses your portal name.
4. Select **Save**.

With your own app registration, the silent sign-in works only when the
client's identity provider sign-in counts as the person's second factor. See
[Accept the identity provider's second factor](/client-portal/sso/#accept-the-identity-providers-second-factor).
When it does not, the app shows **Open in browser**, and the person uses the
portal in their browser instead.

## Download the package

1. Under the package section, in **Client**, choose the client. Its tab opens
   that client's portal, branded as that client sees it. **Every client (your
   own branding)** opens the portal's organization switcher instead.
2. Select **Download package**.

When you change the package, raise **Package version** before you upload it
again.

## Install it for the client

1. Send the package to the client's Teams administrator, or sign in to their
   Teams admin center if you manage it.
2. In the Teams admin center, open **Teams apps**, then **Manage apps**, and
   choose **Upload new app**.
3. Upload the package. Then allow it in the app permission policy for the
   people who should have it.
4. People find it under **Apps**, or the administrator pins it with an app
   setup policy.

To add it to a channel, a person adds the app as a tab and selects **Save**.
Everyone in the channel signs in with their own portal account.

## Verify

Open the app in Teams. After signing in, it shows the client's portal with
their branding.

## Next steps

- [Set up single sign-on and directory sync](/client-portal/sso/)
- [Brand the client portal](/client-portal/branding/)