Skip to main content
This guide walks you through publishing MSPortal as a branded Microsoft Teams app for your clients. You configure the app’s name, branding, and tabs in MSPortal, download a ready-to-install app package, and upload it into Microsoft Teams.

​
Overview

The Microsoft Teams integration packages your portal as a custom Teams app that lives in the Teams left rail. With it, you can:
  • Give clients a branded app carrying your name, description, and accent color
  • Choose exactly which portal views appear as tabs: tickets, training, devices, reporting, and more
  • Let clients sign in with their Microsoft account and work with live portal data inside Teams
  • Rename and reorder tabs to match how your clients think about your services
The Microsoft Teams app is enabled per account. If the Microsoft Teams card does not appear on your Integrations page, contact support@msportal.ai to have it enabled.

​
Prerequisites

  • MSPortal.ai account with integration management permissions
  • Microsoft Teams in the client’s Microsoft 365 environment
  • Permission to upload custom apps in the client’s Teams environment (larger organizations may require a Teams administrator to approve the upload)

​
Part 1: Configure Your Teams App

Set up the app’s branding and tabs in MSPortal.
1

Navigate to Integrations

In MSPortal.ai, go to Settings > Integrations.
2

Open the Teams App Settings

Locate the Microsoft Teams card and click Set up Teams app (or Manage Teams app if you have configured it before).
3

Set the App Name and Descriptions

Configure how the app presents itself to your clients:MSPortal pre-fills these with sensible defaults based on your organization name.
4

Choose Your Tabs

In the Tabs section, pick which MSPortal views your clients see in the Teams left rail. For each tab you can:
  • Enable or disable it with the toggle
  • Rename it by editing the label
  • Reorder it with the up and down arrows
Home, Tickets, and Training are enabled by default. Click Reset to defaults to return to the default set at any time.
Teams allows up to 16 tabs per app, and at least one tab must be enabled.
5

Set the Accent Color

Pick the hex color Teams uses for app accents. It defaults to your brand’s primary color from Settings > Branding.
6

Set a Vanity Domain (Optional)

Optionally enter a custom domain (for example portal.yourmsp.com) to use for open-in-browser links. The domain must already point at MSPortal via DNS. Leave it blank to use the standard MSPortal address.
Tabs inside Teams always load from the standard MSPortal address so Microsoft sign-in works; the vanity domain only affects links that open in the browser.
7

Save

Click Save to store your configuration.

​
Part 2: Download and Install the App Package

MSPortal generates a Teams app package (a zip file) from your configuration. You or your clients upload it into Microsoft Teams.
1

Download the Package

Click Download Teams app package. This downloads a zip file containing your branded app.
2

Upload the App in Microsoft Teams

In Microsoft Teams, open Apps > Manage your apps > Upload a custom app > Upload for me or my teams.
3

Pick the Downloaded Zip

Select the zip file you downloaded from MSPortal.
4

Add the App

Click Add. Your portal appears in the Teams left rail with the tabs you configured.
Larger Microsoft 365 organizations may block direct custom app uploads. In that case, a Teams administrator can approve and deploy the custom app from the Teams admin center instead.

​
Available Tabs

You can offer any of the following MSPortal views as tabs in your Teams app: Inside Teams, users sign in with their Microsoft account and see live MSPortal data with your permission model applied.

​
Managing Your Teams App

Return to Settings > Integrations and click Manage Teams app at any time to update the configuration.

​
Updating an Installed App

Each time you save changes, MSPortal bumps the app’s version number. To roll changes out to clients who already installed the app, download the package again and upload the new version in Microsoft Teams; Teams recognizes it as an update to the existing app.

​
Troubleshooting

​
Security & Privacy

  • Sign-in: Users authenticate with their Microsoft account; all data access follows your existing MSPortal permission model
  • Fixed tab set: Tabs can only point at MSPortal views; the app cannot be configured to load arbitrary destinations
  • Data Isolation: Clients only see the data their MSPortal accounts already have access to

​
Next Steps

After publishing your Teams app:

Configure Branding

Set your brand colors and custom domains

Ticketing

Explore the ticketing experience your clients see in Teams

Training

Assign security training courses your clients complete from Teams

Other Integrations

Explore additional integration options

​
Need Help?

For assistance with the Microsoft Teams integration, contact support@msportal.ai.