How to Set Up a Microsoft Teams Bot with Unified
Blog post from Unified.to
Setting up a Microsoft Teams bot with Unified requires careful attention to packaging and installation details to ensure successful API calls and bot functionality. A common issue arises when API calls fail due to missing authorization information, which is often caused by using the wrong manifest schema or not installing the bot in the correct Teams scope. The Microsoft Teams manifest schema must be used instead of the Microsoft Entra app registration manifest, and the bot must be packaged in a .zip file containing a valid manifest.json, color and outline icons. To streamline the process and avoid manual errors, it is recommended to use the Teams Developer Portal to configure the bot, set scopes, and generate a valid app package. After uploading the app, the bot must be installed in the appropriate Team, channel, chat, or personal scope to function properly. Troubleshooting involves ensuring the manifest and app package are correct and that the bot is installed and connected with the required permissions and scopes.