page_type | description | products | languages | extensions | urlFragment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
This sample shows meeting transcripts and recordings. |
|
|
|
officedev-microsoft-teams-samples-tab-meeting-transcript-recording-csharp |
This sample shows meeting transcripts and recordings.
-
.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
The simplest way to run this sample in Teams is to use Teams Toolkit for Visual Studio.
- Install Visual Studio 2022 Version 17.10 Preview 4 or higher Visual Studio
- Install Teams Toolkit for Visual Studio Teams Toolkit extension
- In the debug dropdown menu of Visual Studio, select default startup project > Microsoft Teams (browser)
- In Visual Studio, right-click your TeamsApp project and Select Teams Toolkit > Prepare Teams App Dependencies
- 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 menu in Visual Studio.
- 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.
- 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 appsettings.json.
- 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
.
- ex:
- 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.
- 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
- 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.
-
Select Microsoft Graph -> Application 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
andhttps://{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 appsettings.json.
- Create a policy for a demo tenant user for creating the online meeting on behalf of that user using the following PowerShell script
-
Follow this link- Configure application access policy
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
-
Run the app from a terminal or from Visual Studio, choose option A or B.
A) From a terminal, navigate to
samples/tab-meeting-transcript-recording/csharp
# run the app dotnet run
B) Or from Visual Studio
- Launch Visual Studio
- File -> Open -> Project/Solution
- Navigate to
samples/tab-meeting-transcript-recording/csharp
folder - Select
MeetingTranscriptRecording.sln
file - Press
F5
to run the project
-
In a terminal, navigate to
samples/tab-meeting-transcript-recording/csharp/MeetingTranscriptRecording/ClientApp
-
Inside ClientApp folder execute the below command.
# npm install # npm start
-
-
Open .env file from this path folder
samples/tab-meeting-transcript-recording/csharp/MeetingTranscriptRecording/ClientApp
and update:{{MicrosoftAppId}}
- Generated from Step 1 (Application (client) ID)is the application app id\
-
Modify the
/appsettings.json
and fill in the following details:{{MicrosoftAppId}}
- Generated from Step 1 (Application (client) ID)is the application app id{{TenantId}}
- Generated from Step 1(Directory (tenant) ID) is the tenant id{{MicrosoftAppPassword}}
- Generated from Step 1.14, also referred to as Client secret
This step is specific to Teams:
-
Edit the
manifest.json
contained in theAppPackage
folder to replace your Microsoft App Id{{MicrosoftAppId}}
(that was created when you registered your bot earlier) everywhere you see the place holder string{{MicrosoftAppId}}
(depending on the scenario the Microsoft App Id may occur multiple times in themanifest.json
) -
Edit the
manifest.json
for{{domain-name}}
with base Url domain. E.g. if you are using ngrok it would behttps://1234.ngrok-free.app
then your domain-name will be1234.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
AppPackage
folder to create amanifest.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.
You can interact with Teams Tab meeting sidepanel.
Install app:
Click Sign-In:
Click Consent:
Permissions Requested:
Sign-In Loading:
Meeting Detail Page:
Get Notification:
Loading Meetings, Fetching Transcript and Recordings:
Recording and Transcript Form: