Skip to content

Latest commit

 

History

History
 
 
page_type description products languages extensions urlFragment
sample
This sample illustrates how you can use Resource Specific Consent (RSC) to call Graph APIs.
office-teams
office
office-365
nodejs
contentType createdDate
samples
07/07/2021 01:38:26 PM
officedev-microsoft-teams-samples-graph-rsc-nodeJs

Resource specific consent with Graph API

This sample illustrates you can use Resource Specific Consent to call Graph API.

Interaction with app.

Broadcast from user

Prerequisites

  • NodeJS version v16.14.2 or Higher Version
  • ngrok or equivalent tunnelling solution
  • M365 developer account or access to a Teams account with the appropriate permissions to install an app.

Setup

  1. Register your app with Microsoft identity platform via the Azure AD portal (AAD app registration in Azure portal)

  2. Clone the repository

    git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
  3. In a terminal, navigate to samples/graph-rsc/nodejs

  4. Install modules

    npm install
  5. Run ngrok - point to port 3978

    ngrok http -host-header=rewrite 3978
  6. Update the .env file configuration (ClientId, ClientSecret) for the bot to use the Microsoft App Id and App Password from the AAD app registration in your Azure Portal or from Bot Framework registration. (Note the App Password is referred to as the "client secret" in the azure portal and you can always create a new client secret anytime.)

  7. Run your bot at the command line:

    npm start
  8. This step is specific to Teams.

    • Edit the manifest.json contained in the teamsManifest folder to replace your Microsoft App Id (that was created when you registered your bot earlier) everywhere you see the place holder string <<app id>> (depending on the scenario the Microsoft App Id may occur multiple times in the manifest.json)
    • [Your Ngrok Domain] with base Url domain. E.g. if you are using ngrok it would be https://1234.ngrok.io then your domain-name will be 1234.ngrok.io.
    • Zip up the contents of the teamsManifest folder to create a manifest.zip
    • Upload the manifest.zip to Teams (in the Apps view click "Upload a custom app")

Running the sample

App review: Overview

App permission: Permission

Permission list: Permissionlist

Further Reading.

-Graph RSC