Single sign-on demo for Microsoft Teams apps using OAuth

Deploy Status


In this demo, we will show you how to authorize a user to access resources through a Microsoft Teams app with a bot. We will use Azure Active Directory for OAuth provider and Microsoft Graph for the protected resources.

After sign-in, this demo will keep OAuth token inside the Teams tab, and also send it to the bot via Web Chat backchannel. Because both web page and bot need to hold a single OAuth token, we are unable to use OAuth card in this demo.

When dealing with personal data, please respect user privacy. Follow platform guidelines and post your privacy statement online.


This sample is a simplified and reduced version of the sample “Single sign-on demo for enterprise apps using OAuth” and modified from “Single sign-on demo for Intranet apps using OAuth”. There are notable differences:

This demo does not include any threat models and is designed for educational purposes only. When you design a production system, threat-modelling is an important task to make sure your system is secure and provide a way to quickly identify potential source of data breaches. IETF RFC 6819 and OAuth 2.0 for Browser-Based Apps is a good starting point for threat-modelling when using OAuth 2.0.

How to run locally

This demo integrates with Azure Active Directory and Microsoft Teams. You will need to set it up in order to host the demo.

  1. Start ngrok tunnel for Microsoft Teams app
  2. Clone the code
  3. Setup OAuth via Azure Active Directory
  4. Setup Azure Bot Services
  5. Setup a new Microsoft Teams app and install it locally
  6. Prepare and run the code

Start ngrok tunnel for Microsoft Teams app

Since Microsoft Teams only supports https:// addresses, we will be using ngrok tunnel to provide a temporary HTTPS tunnel for this demo.

  1. Download ngrok
  2. Run ngrok http 5000
  3. Write down the Microsoft Teams app tunnel URL in this step
    • In the steps below, we will refer this URL as
    • You should replace it with the tunnel URL you obtained from this step

Clone the code

To host this demo, you will need to clone the code and run locally.

  1. Clone this repository
  2. Create two files for environment variables, /bot/.env and /web/.env
    • In /web/.env:
        • When Azure Active Directory completes the authorization flow, it will send the browser to this URL. This URL must be accessible by the browser from the end-user machine
      • Write PROXY_BOT_URL=http://localhost:3978
        • This will forward all traffic from to http://localhost:3978/api/messages, where your bot is listening to

Setup OAuth via Azure Active Directory

Setup Azure Bot Services

We prefer using Bot Channel Registration during development. This will help you diagnose problems locally without deploying to the server and speed up development.

Since we already setup PROXY_BOT_URL in our web server /web/.env in “Clone the code” step, we can reuse the same ngrok tunnel. It will forward traffic from the web server to the bot.

You can follow our instructions on how to setup a new Bot Channel Registration. Points the messaging URL to

  1. Save the Microsoft App ID and password to /bot/.env
    • MICROSOFT_APP_ID=12345678-1234-5678-abcd-12345678abcd
    • MICROSOFT_APP_PASSWORD=a1b2c3d4e5f6
  2. Save the Web Chat secret to /web/.env
    • DIRECT_LINE_SECRET=a1b2c3.d4e5f6g7h8i9j0

When you are building your production bot, never expose your Web Chat or Direct Line secret to the client. Instead, you should use the secret to generate a limited token and send it to the client. For information, please refer generating a Direct Line token and Enhanced Direct Line Authentication feature.

Setup a new Microsoft Teams app and install it locally

This section is based on the Microsoft Teams article named “Add tabs to Microsoft Teams apps”.

  1. Install App Studio app on Microsoft Teams
  2. In the App Studio, switch to “Manifest editor” tab
  3. Click “+ Create a new app” button
  4. Fill out “App details” under “Details”, for example:
    1. For “App names”, enter “Web Chat SSO”
    2. Under “Identification”
      1. Click “Generate” button on “App ID”
      2. For “Package Name”, enter “”
      3. For “Version”, enter “1.0.0”
    3. Under “Descriptions”
      1. For both “Short description” and “Long description”, enter “Company landing page with Web Chat and Single Sign-On”
    4. Under “Developer information”
      1. For “Name”, enter “My Company”
      2. For “Website”, enter
    5. Under “App URLs”
      1. For “Privacy statement”, enter
      2. For “Terms of use”, enter
  5. Fill out “Tabs” under “Capabilities”
    1. On “Add a personal tab” section, click “Add”
      1. For “Name”, enter “My Company”
      2. For “Entity ID”, enter “webchat”
      3. For “Content URL”, enter
        • This URL will be based on the ngrok tunnel you create in “Start ngrok tunnel” section
      4. Click “Save” button
  6. Under “Test and distribute” of “Finish” section
    1. Click “Install” button
    2. On the “Web Chat SSO” dialog, click “Install” button again

Prepare and run the code

  1. Under both the bot, and web folder, run the following:
    1. npm install
    2. npm start
  2. In Microsoft Teams, open the new app you just created in the “Setup a new Microsoft Teams app and install it locally” step
    1. Click “…” on the navigation bar below “Files”
    2. Click “Web Chat SSO”
    3. Click “My Company” tab

Things to try out



This sample includes multiple parts:



Content of the .env files

The .env files hold the environment variables critical to run the service. These are usually security-sensitive information and must not be committed to version control. Although we recommend keeping these keys in Azure Vault, for simplicity of this sample, we would keep them in .env files.

To ease the setup of this sample, here is the template of .env files.





Frequently asked questions

How can I reset my authorization?

To reset application authorization, please follow the steps below.

  1. On the AAD dashboard page, wait until “App permissions” loads. Here you see how many apps you have authorized
  2. Click “Change app permissions”
  3. In the “You can revoke permission for these apps” section, click the “Revoke” button below your app registration

Further reading

OAuth access token vs. refresh token

To make this demo simpler, we are obtaining the access token via Authorization Code Grant flow instead of the refresh token. Access token is short-lived and considered secure to live inside the browser.

In your production scenario, you may want to obtain the refresh token with “Authorization Code Grant” flow instead of using the access token. We did not use the refresh token in this sample as it requires server-to-server communications and secured persistent storage, it would greatly increase the complexity of this demo.

Threat model

To reduce complexity, this sample is limited in scope. In your production system, you should consider enhancing it and review its threat model.

Microsoft Teams: Personal tab vs. team tab

Because team tabs are designed to be used collaboratively by two or more users, content shown inside the team tab should be synchronized in terms of content and interactions. For example, a tab showing Microsoft Excel web app that two or more users can collaboratively edit the content.

For content that is not designed to be used by multiple users at the same time (for example, conversation with a bot), this type of content should be limited to personal tab only to reduce confusion.