nodejs

page_type	description	products	languages	extensions	urlFragment
sample	This sample demonstrates how to retrieve and display meeting context and participant details in Microsoft Teams using the bot's Meeting API.	office-teams office office-365	nodejs	contentType createdDate samples 01/07/2022 05:00:25 PM	officedev-microsoft-teams-samples-meetings-context-app-nodejs

Teams Meeting Context Sample Node.js

This sample application illustrates how to display the meeting context object in a Microsoft Teams meeting tab, utilizing the bot's Meeting API to fetch participant and meeting details. Users can interact with the bot to obtain comprehensive information about participants and meeting specifics, such as start times, end times, and joining URLs, thereby enriching the collaborative experience within Teams.

Included Features

• Bots
• Meeting Chat
• Meeting Details
• RSC Permissions

Interaction with bot

Try it yourself - experience the App in your Microsoft Teams client

Please find below demo manifest which is deployed on Microsoft Azure and you can try it yourself by uploading the app package (.zip file link below) to your teams and/or as a personal app. (Sideloading must be enabled for your tenant, see steps here).

Teams Meeting Context Sample: Manifest

Prerequisites

• NodeJS
• dev tunnel or ngrok latest version or equivalent tunnelling solution
• Teams Toolkit for VS Code or TeamsFx CLI

Run the app (Using Teams Toolkit for Visual Studio Code)

The simplest way to run this sample in Teams is to use Teams Toolkit for Visual Studio Code.

1. Ensure you have downloaded and installed Visual Studio Code
2. Install the Teams Toolkit extension
3. Select File > Open Folder in VS Code and choose this samples directory from the repo
4. Using the extension, sign in with your Microsoft 365 account where you have permissions to upload custom apps
5. Select Debug > Start Debugging or F5 to run the app in a Teams web client.
6. In the browser that launches, select the Add button to install the app to Teams.

Setup

Note these instructions are for running the sample on your local machine.

1. Run ngrok - point to port 3978

   ngrok http 3978 --host-header="localhost:3978"

   Alternatively, you can also use the dev tunnels. Please follow Create and host a dev tunnel and host the tunnel with anonymous user access command as shown below:

   devtunnel host -p 3978 --allow-anonymous

2. Setup for Bot

Register your application with Azure AD

• Register a new application in the Microsoft Entra ID – App Registrations portal.

• On the overview page, copy and save the Application (client) ID, Directory (tenant) ID. You’ll need those later when updating your Teams application manifest and in the appsettings.json.

• Navigate to the Certificates & secrets. In the Client secrets section, click on "+ New client secret". Add a description (Name of the secret) for the secret and select “Never” for Expires. Click "Add". Once the client secret is created, copy its value, it need to be placed in the .env file.

• In Azure portal, create a Azure Bot resource.

• Ensure that you've enabled the Teams Channel

3. Clone the repository

   git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git

   A) If you are using Visual Studio Code

   • Launch Visual Studio code
   • File -> Open Folder
   • Navigate to samples/meeting-context-app folder
   • Select nodejs folder

   B) Install node modules For Server

   Inside node js folder, open your local terminal and run the below command to install node modules. You can do the same in Visual Studio code terminal by opening the project in Visual Studio code.

   npm install

   C) Install node modules For Client

   Navigate to folder client folder, open your local terminal and run the below command to install node modules. You can do the same in Visual Studio code terminal by opening the project in Visual Studio code.

   npm install

4. Update the .env configuration file.

   Update configuration with the MicrosoftAppId, MicrosoftAppPassword and MicrosoftAppTenantId.

5. Run your app for server and client

   npm start

   • Your server will start running on 3000 PORT
   • Your client will start running on 3978 PORT.

6. This step is specific to Teams.

   • Edit the manifest.json contained in the appManifest folder to replace your Microsoft App Id (that was created when you registered your bot earlier) everywhere you see the place holder string <<YOUR-MICROSOFT-APP-ID>> (depending on the scenario the Microsoft App Id may occur multiple times in the manifest.json)
   • Edit the manifest.json for validDomains with base Url domain. E.g. if you are using ngrok it would be https://1234.ngrok-free.app then your domain-name will be 1234.ngrok-free.app and if you are using dev tunnels then your domain will be like: 12345.devtunnels.ms.
   • Zip up the contents of the appManifest folder to create a manifest.zip (Make sure that zip file does not contains any subfolder otherwise you will get error while uploading your .zip package)
   • Upload the manifest.zip to Teams (In Teams Apps/Manage your apps click "Upload an app". Browse to and Open the .zip file. At the next dialog, click the Add button.)
   • Add the app to personal/team/groupChat scope (Supported scopes)

Running the sample

• Add the app in meeting/group channel.

• The details of the meeting context object will be shown on tab based.

• You can expand/reduce the JSON for the context object and can also copy a particular object slice.

• You can send one of these two commands: Meeting Context or Participant Context

• It will send you the output of TeamsInfo.getMeetingInfo and TeamsInfo.getMeetingParticipant

1. Particpant Details : User can see the details of current participant by the name id and other feilds respectively.

2. Meeting Details : In this user can track the detials of meeting start time, end time, joining url and other details respectively.

Note: If you are facing any issue in your app, please uncomment this line and put your debugger for local debug.

Further reading

• Tab Basics
• Azure Portal
• Get-context-for-tabs
• Meeting API reference