nodejs

page_type	description	products	languages	extensions	urlFragment
sample	This sample demos a bot with capability to upload files to SharePoint site and same files can be viewed in Teams file viewer.	office-teams office office-365	nodejs javascript	contentType createdDate samples 16-11-2021 00:15:13	officedev-microsoft-teams-samples-bot-sharepoint-file-viewer-nodejs

Bot with SharePoint file to view in Teams file viewer

Using this Nodejs sample, a bot with capability to upload files to SharePoint site and same files can be viewed in Teams file viewer.

Key features

Prerequisites

• Microsoft Teams is installed and you have an account (not a guest account)
• NodeJS
• ngrok or equivalent tunneling solution
• M365 developer account or access to a Teams account with the appropriate permissions to install an app.

To try this sample

Note these instructions are for running the sample on your local machine, the tunnelling solution is required because the Teams service needs to call into the bot.

1. Setup for Bot SSO

In Azure portal, create a Bot Framework registration resource.

• Ensure that you've enabled the Teams Channel

Add this permission to app registration

2. Setup Sharepoint site configuration

• Login to sharepoint

• Click on Create site and select Team site

  

  • Enter site name and description of site.

  .

  • From site address eg: 'https://m365x357260.sharepoint.com/sites/SharePointTestSite' m365x357260.sharepoint.com - value is sharepoint tenant name.

  • Click on next. (optional step)Add aditional owner and member.

  • Click on Finish.

3. Run your bot sample

1. Clone the repository

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

2. In a terminal, navigate to samples/bot-sharepoint-file-viewer/nodejs

3. Install modules

   npm install

4. Run ngrok - point to port 3978

   ngrok http -host-header=rewrite 3978

5. Update the .env configuration for the bot to use the MicrosoftAppId and MicrosoftAppPassword and ConnectionName from the Bot Framework registration. (Note that the MicrosoftAppId is the AppId created in step 1 (Setup for Bot SSO), the MicrosoftAppPassword is referred to as the "client secret" in step 1 (Setup for Bot SSO) and you can always create a new client secret anytime.) Also update the SharepointTenantName with your tenant name and SharepointSiteName with your sharepoint site name. For ApplicationBaseUrl provide the application base url.

6. Run your bot at the command line:

   npm start

• Manually update the manifest.json

  • Edit the manifest.json contained in the /appPackage folder to and fill in MicrosoftAppId (that was created in step 1 and it is the same value of MicrosoftAppId as in .env file) everywhere you see the place holder string <<YOUR-MICROSOFT-APP-ID>> (depending on the scenario it may occur multiple times in the manifest.json)
  • Zip up the contents of the /appPackage folder to create a manifest.zip
  • Upload the manifest.zip to Teams (in the left-bottom Apps view, click "Upload a custom app")

  IMPORTANT: The manifest file in this app adds "token.botframework.com" to the list of validDomains. This must be included in any bot that uses the Bot Framework OAuth flow.

Interacting with the bot.

Add the bot to personal scope.

Send login message to the bot, you will recieve a consent card by the bot in your personal scope.