Name	Name	Last commit message	Last commit date
parent directory ..
.vscode	.vscode
Images	Images
Manifest	Manifest
api-server	api-server
assets	assets
env	env
public	public
src	src
.env	.env
.gitignore	.gitignore
README.md	README.md
aad.manifest.json	aad.manifest.json
package-lock.json	package-lock.json
package.json	package.json
teamsapp.local.yml	teamsapp.local.yml
teamsapp.yml	teamsapp.yml
tsconfig.json	tsconfig.json

page_type

description

products

languages

extensions

urlFragment

sample

This sample shows how to interact with Calendar, Mail, Profile, geolocation from personal tabs app.

office-teams

office

office-365

typescript

contentType	createdDate
samples	20/06/2023 01:38:27 PM

officedev-microsoft-teams-samples-tab-multi-hub-ts

Interact with Calendar, Mail, Profile, geolocation from Personal Tabs App

Interact with the user's calendar, mail, profile, geolocation from personal tabs app.

Included Features

Tabs
Outlook Calendar, Mail, Profile, geolocation

Interaction with app - Desktop

Interaction with app - Mobile

Prerequisites

NodeJS
M365 developer account or access to a Teams account with the appropriate permissions to install an app.
Ngrok (For local environment testing) Latest (any other tunneling software can also be used)
Teams Microsoft Teams is installed and you have an account
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.

1. Register you app with Azure AD

Register a new application in the Azure Active Directory – 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.
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 desktop, mobile)
- 5e3ce6c0-2b1f-4285-8d4b-75ee78787346 (Teams web)
- 4765445b-32c6-49b0-83e6-1d93765276ca (Microsoft 365 web)
- 0ec893e0-5785-4de6-99da-4ed124e5296c (Microsoft 365 desktop)
- d3590ed6-52b3-4102-aeff-aad2292ab01c (Microsoft 365 mobile)
- bc59ab01-8403-45c6-8796-ac3ef710b3e3 (Outlook web)
- 27922004-5251-4030-b22d-91ecd9a37ea4 (Outlook mobile)
Navigate to API Permissions, and make sure to add the follow permissions:

Select Add a permission
Select Microsoft Graph -> Delegated permissions.
- User.Read (enabled by default)
- Calendars.Read
- Calendars.ReadBasic
- Calendars.ReadWrite
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.

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.

2. Setup NGROK

Run ngrok - point to port 3978

ngrok http 3978 --host-header="localhost:3978"

Setup for code Clone the repository

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

Open .env file from this path folder samples/tab-multi-hub/ts/api-server and update
- {{CLIENT_ID}} - Generated from Step 1 (Application (client) ID)is the application app id
- {{CLIENT_SECRET}} - Generated from Step 1.14, also referred to as Client secret
Open .env file from this path folder samples/tab-multi-hub/ts and update
- {{REACT_APP_AZURE_APP_REGISTRATION_ID}} - Generated from Step 1 (Application (client) ID)is the application app id
- {{REACT_APP_BASE_URL}} - Your application's base url. E.g. https://12345.ngrok-free.app if you are using ngrok.
We have two different solutions to run, so follow below steps:

In a terminal, navigate to samples/tab-multi-hub/ts/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-multi-hub/ts 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

3. Setup Manifest for Teams

This step is specific to Teams. Edit the manifest.json contained in the Manifest/ folder to replace with your MicrosoftAppId (that was created in step1.1 and is the same value of MicrosoftAppId in .env file) 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. Zip up the contents of the Manifest/ folder to create a manifest.zip or Manifest_Hub/ folder to create a manifest_Hub.zip Upload the manifest.zip to Teams (in the left-bottom Apps view, click "Upload a custom app")