A Message Extension allows users to interact with your web service while composing messages in the Microsoft Teams client. Users can invoke your web service to assist message composition, from the message compose box, or from the search bar.
Message Extensions are implemented on top of the Bot support architecture within Teams.
This is a simple hello world application with Message extension capabilities.
- Node.js, supported versions: 16, 18
- An M365 account. If you do not have M365 account, apply one from M365 developer program
- Teams Toolkit Visual Studio Code Extension version 5.0.0 and higher or TeamsFx CLI
- From Visual Studio Code: Start debugging the project by hitting the
F5
key in Visual Studio Code. - Alternatively use the
Run and Debug Activity Panel
in Visual Studio Code and click theRun and Debug
green arrow button. - From TeamsFx CLI:
- Install ngrok and start your local tunnel service by running the command
ngrok http 3978
. - In the
env/.env.local
file, fill in the values forBOT_DOMAIN
andBOT_ENDPOINT
with your ngrok URL.BOT_DOMAIN=sample-id.ngrok.io BOT_ENDPOINT=https://sample-id.ngrok.io
- 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
in your project directory.
- Install ngrok and start your local tunnel service by running the command
You can find the Teams app manifest in ./appPackage
folder. The folder contains one manifest file:
manifest.json
: Manifest file for Teams app running locally or running remotely (After deployed to Azure).
This file contains template arguments with ${{...}}
statements which will be replaced at build time. You may add any extra properties or permissions you require to this file. See the schema reference for more information.
Deploy your project to Azure by following these steps:
From Visual Studio Code | From TeamsFx CLI |
---|---|
|
|
Note: Provisioning and deployment may incur charges to your Azure Subscription.
Once the provisioning and deployment steps are finished, you can preview your app:
-
From Visual Studio Code
- Open the
Run and Debug Activity Panel
. - Select
Launch Remote (Edge)
orLaunch Remote (Chrome)
from the launch configuration drop-down. - Press the Play (green arrow) button to launch your app - now running remotely from Azure.
- Open the
-
From TeamsFx CLI: execute
teamsfx preview --env dev
in your project directory to launch your application.
To check that your manifest file is valid:
- From Visual Studio Code: open the command palette and select:
Teams: Validate Application
. - From TeamsFx CLI: run command
teamsfx validate
in your project directory.
- From Visual Studio Code: open the Teams Toolkit and click
Zip Teams App Package
or open the command palette and selectTeams: Zip Teams App Package
. - Alternatively, from the command line run
teamsfx package
in the project directory.
Once deployed, you may want to distribute your application to your organization's internal app store in Teams. Your app will be submitted for admin approval.
- From Visual Studio Code: open the Teams Toolkit and click
Publish
or open the command palette and select:Teams: Publish
. - From TeamsFx CLI: run command
teamsfx publish
in your project directory.
This template provides some sample functionality:
-
You can search for
npm
packages from the search bar. -
You can create and send an adaptive card.
-
You can share a message in an adaptive card form.
-
You can paste a link that "unfurls" (
.botframework.com
is monitored in this template) and a card will be rendered.
To trigger these functions, there are multiple entry points:
-
@mention
Your message extension, from thesearch box area
. -
@mention
your message extension from thecompose message area
. -
Click the
...
under compose message area, find your message extension. -
Click the
...
next to any messages you received or sent.