Teams Toolkit v5.0 Pre-release

What does pre-release mean?

Pre-release is meant for those who are eager to try the latest Teams Toolkit features and fixes. Even though pre-releases are not intended for use in production, they are at a sufficient quality level for you to generally use and provide feedback. However, pre-release versions can and probably will change, and those changes could be major.

We've addressed a number of reported bugs and added major changes in this release based on your feedback to make Teams Toolkit more flexible. Some of the key highlights to these changes include:

Use existing infrastructure, resource groups, and more when provisioning
Use an existing Teams app ID
Use an existing Azure AD app registration ID
Use a different tunneling solution or customize the defaults
Add custom steps to debugging, provisioning, deploying, publishing, etc.

What about my existing Teams Toolkit projects?

The changes in this pre-release require upgrades to the TeamsFx configuration files. We recommend that you create a new app using this version. In the future, we'll provide a way to automatically upgrade existing Teams apps that were created with a previous version of Teams Toolkit.

Learn more about the changes in this pre-release at https://aka.ms/teamsfx-v5.0-guide.

Search based message extension across Microsoft 365

Search-based message extensions allow users to search an external system and share results through the compose message area of the Microsoft Teams client. You can now build and run your search-based message extensions in Teams, Outlook for Windows desktop and web experiences.

Prerequisites

Node.js, supported versions: 14, 16, 18
An M365 account. If you do not have M365 account, apply one from M365 developer program
Set up your dev environment for extending Teams apps across Microsoft 365

Please note that after you enrolled your developer tenant in Office 365 Target Release, it may take couple days for the enrollment to take effect.

Teams Toolkit Visual Studio Code Extension or TeamsFx CLI

Getting Started

Follow below instructions to get started with this application template for local debugging.

Test your application with Visual Studio Code

Press F5 or use the Run and Debug Activity Panel in Visual Studio Code.
Select a target Microsoft application where the message extension runs: Debug in Teams, Debug in Outlook and click the Run and Debug green arrow button.

Test your application with TeamsFx CLI

Executing the command teamsfx provision --env local in your project directory.
Executing the command teamsfx deploy --env local in your project directory.
Executing the command teamsfx preview --env local --m365-host <m365-host> in your project directory, where options for m365-host are teams or outlook.