Upload an app package to Microsoft Teams
To test your app experience within Microsoft Teams, you need to upload your app to Teams. Uploading adds the app to the team you select, and you and your team members can interact with it like end users.
Uploading an updated package for an existing app with a bot might not show tab changes when viewed through the Conversations window. It's better to access it via the Apps fly-out, or test on a clean test environment.
For bots designed only for personal conversations between a bot and a single user, see Adding a bot for personal chat only for an alternate way to access for testing purposes.
Create your upload package
For development as well as AppSource (formerly Office Store) submission you must create an uploadable package that contains the information to describe your experience. The package, a .zip file, contains the application manifest and icons that uniquely define your experience.
To create an upload package, see Create the package for your Microsoft Teams app.
Load your package into a team
With your package created, you can now upload it into a team. Once uploaded it will be available for all users in the selected team, and only the users of that team.
For uploading to work, your tenant admin must first enable uploading of apps.
Create a new team for testing, if necessary. Click Create and join team at the bottom of the left-hand panel.
In the target team, choose More options (⋯) and choose Manage team.
You must be the team owner, or the owner must allow users to add the appropriate app types for this functionality to appear.
Select the Apps tab, and then choose Upload a custom app on the lower right.
Browse to and select your .zip package from your computer.
After a brief pause you will see your uploaded app in the list.
If your app does not load, the most common reason is an error in the manifest, particularly ids for the app, bot and messaging extensions.
Accessing your uploaded configurable tab
If the app contains tabs, users can pin them to any channel on the team using the standard tab gallery flow:
Go to a channel in the team. Choose + (Add a tab) to the right of the existing tabs.
Select your tab from the gallery that appears.
Accept the consent prompt.
Configure your tab via its configuration page and choose Save.
Accessing your uploaded bot
When you add a bot to the team, it should be usable by anyone on that team, inside and outside the team channels, depending on bot scope definition. You and other team members will see a post in the General channel indicating that the bot has been added to the team.
For a teams-enabled bot, you can start by invoking your bot by @mentioning the name of the bot, which should autocomplete.
To test direct chats with your bot, you can either access it via the App home, @mention it in a channel, or search for it in the New Chat window.
Accessing your uploaded Connector
With the app loaded in the team, users can set up a Connector on any channel in the team using the standard Connectors gallery flow:
Go to a channel in the team. Choose More options (⋯) and choose Connectors.
Select your Connector from the Uploaded section at the bottom.
Configure your Connector via its configuration page and choose Save.
Accessing your uploaded messaging extension
An uploaded app with a messaging extension automatically appears in the More options (⋯) menu in the compose box.
Removing or updating your app
If you want to remove your app, select the trash-can icon next to the app name in the View Teams bots list.
If you change manifest information, you must first remove the app and then add the updated package (per Load your package into a team). Note that, in general, code changes on your service do not require you to re-upload your manifest, unless those changes require manifest updates (such as changes to the URL or the Microsoft app ID for its bot).
There is currently no way to completely remove a bot from personal context.