nodejs

page_type	description	products	languages	extensions	urlFragment
sample	This sample illustrates how you can use Teams App Installation Life Cycle by calling Microsoft Graph APIs through teams tab.	office-teams office office-365	nodejs	contentType createdDate samples 06-10-2021 01:48:56	officedev-microsoft-teams-samples-graph-app-installation-lifecycle-nodejs

App Installation

This sample app demonstarte the installation lifecycle for Teams Apps which includes create, update delete Apps

Included Features

• Tabs
• Graph API

Interaction with app

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).

App Installation: Manifest

Prerequisites

• Microsoft Teams is installed and you have an account (not a guest account)
• To test locally, NodeJS must be installed on your development machine (version 16.14.2 or higher)
• ngrok or equivalent tunneling solution
• M365 developer account or access to a Teams account with the

Setup

1. Register a new application in the Azure Active Directory – App Registrations portal.

   • Your app must be registered in the Azure AD portal to integrate with the Microsoft identity platform and call Microsoft Graph APIs. See Register an application with the Microsoft identity platform.
   • You need to add following permissions mentioned in the below screenshots to call respective Graph API

2. Setup for Bot

• In Azure portal, create a Azure Bot resource.
• Ensure that you've enabled the Teams Channel
• While registering the bot, use https://<your_ngrok_url>/api/messages as the messaging endpoint. NOTE: When you create app registration, you will create an App ID and App password - make sure you keep these for later.

3. Setup NGROK

   • Run ngrok - point to port 3978

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

4. Setup for code

• Clone the repository

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

• Update the .env configuration for the bot to use the ClientID and ClientSecret. (Note the MicrosoftAppId is the AppId created in step 1 (Setup for Bot), the MicrosoftAppPassword is referred to as the "client secret" in step 1 (Setup for Bot) and you can always create a new client secret anytime.)

• In a terminal, navigate to `samples/graph-app-installation-lifecycle/nodejs

• Install modules

  npm install

• Run your bot at the command line:

  npm start

5. Setup Manifest for Teams

• This step is specific to Teams.

  • Edit the manifest.json contained in the ./Manifest folder to replace your Microsoft App Id (that was created when you registered your app registration earlier) everywhere you see the place holder string {{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 and replace {{domain-name}} with base Url of your 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.
  • Zip up the contents of the Manifest 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 the Apps view click "Upload a custom app")

  • Go to Microsoft Teams. From the lower left corner, select Apps
  • From the lower left corner, choose Upload a custom App
  • Go to your project directory, the ./Manifest folder, select the zip folder, and choose Open.
  • Select Add in the pop-up dialog box. Your app is uploaded to Teams.

Running the sample

![](Images/DeleteApp.png)

![](Images/AppDeleteSuccess.png)

Further reading

• Graph-app-installation
• Bot Framework Documentation
• Bot Basics
• Azure Bot Service Introduction
• Azure Bot Service Documentation