Skip to content

Latest commit

 

History

History
 
 

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
page_type description products languages extensions urlFragment
sample
This sample illustrates how you can use Graph API Channel Life Cycle to call Graph APIs through teams tab.
office-teams
office
office-365
nodejs
contentType createdDate
samples
07/07/2021 01:38:26 PM
officedev-microsoft-teams-samples-graph-channel-lifecycle-nodejs

Channel life cycle using Node js

This sample show the Channel life cycle which includes create, update delete a channel.

Included Features

  • Tabs
  • Graph API
  • RSC Permissions

Interaction with app

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. NOTE: When you create app registration, you will create an App ID and App password - make sure you keep these for later.
  1. Setup NGROK
  • Run ngrok - point to port 3978
```bash
ngrok http 3978 --host-header="localhost:3978"
```
  1. Setup for code
  • Clone the repository

    git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
  • In a terminal, navigate to `samples/graph-channel-lifecycle/nodejs

  • Update the .env configuration with the Microsoft ClientId and ClientSecret

  • Install modules

    npm install
  • Run your bot at the command line:

    npm start
  1. Setup Manifest for Teams
  • This step is specific to Teams.
    • Edit the manifest.json contained in the teamsManifest/ folder to replace with your MicrosoftAppId (that was created in step1.1 and is the same value of MicrosoftAppId in .env file) everywhere you see the place holder string {MicrosoftAppId} (depending on the scenario the Microsoft App Id may occur multiple times in the manifest.json)

    • Zip up the contents of the teamsManifest/ folder to create a manifest.zip

    • Upload the manifest.zip to Teams (in the left-bottom Apps view, click "Upload a custom app")

Running the sample.

Grpah-Channel-lifecycel