Microsoft-Teams-Samples/samples/tab-meeting-transcript-recording/nodejs at main · OfficeDev/Microsoft-Teams-Samples

Name	Name	Last commit message	Last commit date
parent directory ..
Images	Images
api-server	api-server
appManifest	appManifest
assets	assets
public	public
src	src
.env	.env
.gitignore	.gitignore
README.md	README.md
package-lock.json	package-lock.json
package.json	package.json

page_type

description

products

languages

extensions

urlFragment

sample

This sample application for Microsoft Teams allows users to capture meeting transcripts and recordings, providing an efficient way to document discussions and decisions. With easy setup and integration using Node.js, it enhances team collaboration and ensures that important meeting details are never lost.

office-teams

office

office-365

nodejs

contentType	createdDate
samples	11-22-2023 10:00:01

officedev-microsoft-teams-samples-tab-meeting-transcript-recording-nodejs

Meeting Transcripts Recordings

This Microsoft Teams sample application facilitates the capture and management of meeting transcripts and recordings, ensuring that key discussions are accurately documented. Designed for seamless integration with Node.js, it offers straightforward setup instructions, enabling teams to focus on collaboration while retaining a comprehensive record of their meetings.

Interaction with app

Prerequisites

.NET Core SDK version 6.0

determine dotnet version
```
dotnet --version
```
dev tunnel or ngrok latest version or equivalent tunnelling solution.
Teams Microsoft Teams is installed and you have an account

Setup Register you app with Azure AD.

Register a new application in the Microsoft Entra ID – App Registrations portal.
Select New Registration and on the register an application page, set following values:
- Set name to your app name.
- Choose the supported account types (any account type will work)
- Leave Redirect URI empty.
- Choose Register.
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 .env files.
Under Manage, select Expose an API.
Select the Set link to generate the Application ID URI in the form of api://{base-url}/{AppID}. Insert your fully qualified domain name (with a forward slash "/" appended to the end) between the double forward slashes and the GUID. The entire ID should have the form of: api://fully-qualified-domain-name/{AppID}
- ex: api://%ngrokDomain%.ngrok-free.app/00000000-0000-0000-0000-000000000000.
Select the Add a scope button. In the panel that opens, enter access_as_user as the Scope name.
Set Who can consent? to Admins and users
Fill in the fields for configuring the admin and user consent prompts with values that are appropriate for the access_as_user scope:
- Admin consent title: Teams can access the user’s profile.
- Admin consent description: Allows Teams to call the app’s web APIs as the current user.
- User consent title: Teams can access the user profile and make requests on the user's behalf.
- User consent description: Enable Teams to call this app’s APIs with the same rights as the user.
Ensure that State is set to Enabled
Select Add scope
- The domain part of the Scope name displayed just below the text field should automatically match the Application ID URI set in the previous step, with /access_as_user appended to the end:
  - `api://[ngrokDomain].ngrok-free.app/00000000-0000-0000-0000-000000000000/access_as_user.
In the Authorized client applications section, identify the applications that you want to authorize for your app’s web application. Each of the following IDs needs to be entered:
- 1fec8e78-bce4-4aaf-ab1b-5451cc387264 (Teams mobile/desktop application)
- 5e3ce6c0-2b1f-4285-8d4b-75ee78787346 (Teams web application)
- 4765445b-32c6-49b0-83e6-1d93765276ca (Microsoft 365 web application)
- 0ec893e0-5785-4de6-99da-4ed124e5296c (Microsoft 365 desktop application)
- d3590ed6-52b3-4102-aeff-aad2292ab01c (Outlook desktop application)
- bc59ab01-8403-45c6-8796-ac3ef710b3e3 (Outlook web application)
- 27922004-5251-4030-b22d-91ecd9a37ea4 (Outlook mobile application)
Navigate to API Permissions, and make sure to add the follow permissions:

Select Add a permission
Select Microsoft Graph -> Delegated permissions.
Click on Add permissions. Please make sure to grant the admin consent for the required permissions.

Navigate to Authentication If an app hasn't been granted IT admin consent, users will have to provide consent the first time they use an app.

Set a redirect URI:
- Select Add a platform.
- Select Single-page application.
- Enter the redirect URI for the app in the following format: https://{Base_Url}/auth-end and https://{Base_Url}/auth-start.

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.

Setup

Note these instructions are for running the sample on your local machine.

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

Clone the repository

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

We have two different solutions to run, so follow below steps:

In a terminal, navigate to samples/tab-meeting-transcript-recording/nodejs/api-server folder, Open your local terminal and run the below command to install node modules. You can do the same in Visual studio code terminal by opening the project in Visual studio code
```
npm install
```
```
npm start
```
The server will start running on 5000 port
In a different terminal, navigate to samples/tab-meeting-transcript-recording/nodejs folder, Open your local terminal and run the below command to install node modules. You can do the same in Visual studio code terminal by opening the project in Visual studio code
```
npm install
```
```
npm start
```
The client will start running on 3978 port

Open .env file from this path folders samples/tab-meeting-transcript-recording/nodejs and samples/tab-meeting-transcript-recording/nodejs/api-server update:
- APP_REGISTRATION_ID - Generated from Step 1 (Application (client) ID)is the application app ids
- CLIENT_SECRET - Generated from Step 1.14, also referred to as Client secret
- BASE_URL - Your application's base url. E.g. https://12345.ngrok-free.app if you are using ngrok and if you are using dev tunnels, your URL will be like: https://12345.devtunnels.ms.

Note : Global Administrator can grant consent using following link: https://login.microsoftonline.com/common/adminconsent?client_id=<%appId%>

This step is specific to Teams:

Edit the manifest.json contained in the AppManifest folder to replace your Microsoft App Id {{Microsoft-App-id}} (that was created when you registered your bot 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 {{domain-name}} with base Url 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 Teams Apps/Manage your apps click "Upload an app". Browse to and Open the .zip file. At the next dialog, click the Add button.)
Add the app to personal static tabs.