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 selected team and all the 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. You can access the app through the apps fly-out or test in a clean environment.
Create your upload package
For development and AppSource submission, you must create a package that you can upload. The package must contain the information to describe your experience. The package is a .zip file that 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.
After you create the package, upload it into a team. The uploaded package is only available to the users of the selected team.
Load your package into Teams
You can test your package by uploading it into Teams.
For uploading to work, your tenant admin must first enable uploading of apps.
There are two ways to upload your app to Teams:
- Using the Store
- Using the Apps tab
Upload your package into a team or conversation using the Store
- In the lower left corner of Teams, choose the Store icon. On the Store page, choose Upload a custom app.
In the Open dialog, navigate to the package you want to upload and choose Open.
The uploaded package must be available for use in the team or conversation specified in the consent dialog. If your app does not appear, the most common reason is an error in the manifest, particularly IDs for the app, bot, and messaging extensions. If the app is not scoped for conversations that option does not appear.
Apps in conversations is currently in Developer Preview, and the option does not appear if Teams is not running in that mode.
Upload your package into a team using the Apps tab
In the target team, choose More options (⋯) and select Manage team.
You must be the team owner or the owner must give access to users to add the appropriate app types for this functionality to appear.
Select the Apps tab and choose Upload a custom app on the lower right.
Select your .zip package from the computer.
You can 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.
Access your uploaded configurable tab
If the app contains tabs, users can pin them to any conversation or team channel using the standard tab gallery flow:
Go to a channel in the team. Choose + to 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 through its configuration page and select Save.
Access your uploaded bot
After adding the bot to a team, it must be usable by anyone on that team, inside and outside the team channels, depending on bot scope definition. All team members can see a post in the General channel indicating that the bot has been added to the team.
For a Teams bot, you can start by invoking your bot by @mentioning the name of the bot.
To test direct chats with your bot, you can either access it through the App home, @mention it in a channel, or search for it in the New Chat window.
You can @mention the bot in a conversation or search for it in the New Chat window to test direct chats with your bot.
Access your uploaded Connector
With the app loaded in the team or conversation, users can set up a Connector using the standard Connectors gallery flow:
Go to a channel in the team. Choose More options (⋯) and choose Connectors.
Select your Connector from the Sideloaded section at the bottom.
Configure your connector through its configuration page and select Save.
Access your uploaded messaging extension
An uploaded app with a messaging extension automatically appears in the More options (⋯) menu in the compose box.
Add a default install scope and group capability
The default install scope and group capability is currently available in developer preview only.
Although installing an app in the personal scope works for most apps, some of the apps in Teams Store support both personal and team scopes.
Some of these apps are intended to work in a team, meetings, or a groupchat, with personal app experience being secondary.
The default install scope selection helps you to specify the
defaultInstallScope for the apps that you publish. The app installation experience makes the default options available to the user, while the rest is moved under the chevron as highlighted in the image.
defaultInstallScope property supports values, such as personal, team, groupchat, or meetings.
defaultGroupCapability provides the default capability that is added to the team, groupchat or meetings. Choose a tab, bot, or connector as the default capability for your app, but you must ensure that you have provided the selected capability in your app definition.
Remove or update your app
To remove your app, select the delete icon next to the app name in the View Teams bots list. If you change manifest information, first remove the app and then add the updated package, see Load your package into a team. Code changes on your service do not require you to upload your manifest again. However, if the code changes require manifest updates, such as changes to the URL or the Microsoft app ID for its bot, you must upload the manifest again.
You cannot remove a bot from a personal context entirely. If the bot is removed and added again, additional communication with the bot appends to the previous conversation.