Name		Name	Last commit message	Last commit date
parent directory ..
.vscode		.vscode
Images		Images
appManifest		appManifest
assets		assets
client		client
controller		controller
env		env
helper		helper
template		template
.env		.env
.gitignore		.gitignore
README.md		README.md
aad.manifest.json		aad.manifest.json
auth.js		auth.js
build.js		build.js
package-lock.json		package-lock.json
package.json		package.json
server.js		server.js
teamsapp.local.yml		teamsapp.local.yml
teamsapp.yml		teamsapp.yml

README.md

page_type

description

products

languages

extensions

urlFragment

sample

This sample application demonstrates bulk creation of Teams meetings using file uploads.

office-teams

office

office-365

nodejs

contentType	createdDate
samples	09/08/2022 12:00:00 AM

officedev-microsoft-teams-samples-graph-bulk-meetings-nodejs.

Graph bulk meetings

This sample application demonstrates how to bulk create meetings in Microsoft Teams using file uploads via an intuitive tab interface. It utilizes the Graph API for interaction, includes prerequisites for setup, and provides comprehensive instructions for Azure registration, bot setup, and manifest configuration.

Included Features

Tabs
Graph API

Interaction with app

Prerequisites

Microsoft Teams is installed and you have an account (not a guest account)
NodeJS
dev tunnel or ngrok latest version or equivalent tunneling 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.

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

If you do not have permission to upload custom apps (sideloading), Teams Toolkit will recommend creating and using a Microsoft 365 Developer Program account - a free program to get your own dev environment sandbox that includes Teams.

Setup

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 API Permissions, and make sure to add the follow permissions:
Select Add a permission
Select Microsoft Graph -> Application permissions.
Calendars.Read,
Calendars.ReadWrite.All,
OnlineMeetings.Read.All,
OnlineMeetings.ReadWrite.All
Click on Add permissions. Please make sure to grant the admin consent for the required permissions.
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.

Setup for Bot

In Azure portal, create a [Azure Bot resource](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-authentication?view=azure-bot-service- 4.0&tabs=csharp%2Caadv2).
Ensure that you've enabled the Teams Channel NOTE: When you create app registration, you will create an App ID and App password - make sure you keep these for later.

Setup NGROK

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
```

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 App-Id, App-Secret and Tenant-ID. (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.) for the Tenant-ID is referred to as the "Directory (tenant) ID" in step 1
In a terminal, navigate to samples/graph-bulk-meetings/nodejs

Install node modules and run client

 npm install

npm start

npm install moment --save

Setup Manifest for Teams

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 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 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 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 ./appManifest folder, select the zip folder, and choose Open.
- Select Add in the pop-up dialog box. Your app is uploaded to Teams.