Skip to content

Latest commit

 

History

History
131 lines (87 loc) · 6 KB

README.md

File metadata and controls

131 lines (87 loc) · 6 KB
Raw
page_type description products languages extensions urlFragment
sample
This sample illustrates how you can use Teams App Installation Life Cycle by calling Microsoft Graph APIs through teams tab.
office-teams
office
office-365
csharp
contentType createdDate
samples
07-07-2021 13:38:26
officedev-microsoft-teams-samples-graph-app-installation-lifecycle-csharp

App Installation

This sample app demonstarte the installation lifecycle for Teams Apps which includes create, update delete Apps

Included Features

  • Tabs
  • Graph API

Interaction with app

Try it yourself - experience the App in your Microsoft Teams client

Please find below demo manifest which is deployed on Microsoft Azure and you can try it yourself by uploading the app package (.zip file link below) to your teams and/or as a personal app. (Sideloading must be enabled for your tenant, see steps here).

App Installation: Manifest

Prerequisites

  • .NET Core SDK version 6.0

    determine dotnet version

    dotnet --version

  • Ngrok (For local environment testing) Latest (any other tunneling software can also be used)

  • Teams Microsoft Teams is installed and you have an account

Setup

  1. Register a new application in the Azure Active Directory – App Registrations portal.
  • You need to add following permissions mentioned in the below screenshots to call respective Graph API
  1. Setup for Bot

  • Register a AAD aap registration in Azure portal.

  • Also, register a bot with Azure Bot Service, following the instructions here.

  • Ensure that you've enabled the Teams Channel

  • While registering the bot, use https://<your_ngrok_url>/api/messages as the messaging endpoint.

    NOTE: When you create your app registration, you will create an App ID and App password - make sure you keep these for later.

  1. Setup NGROK
  • Run ngrok - point to port 3978
# ngrok http 3978 --host-header="localhost:3978"
  1. Setup for code

  • Clone the repository

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

  • Modify the /appsettings.json and fill in the following details:

    • {{Your Microsoft App Id}} - Generated from Step 1 while doing AAd app registration in Azure portal.
    • {{ Your Microsoft App Password }} - Generated from Step 1, also referred to as Client secret

  • Build your solution

    • Launch Visual Studio
    • File -> Open -> Project/Solution
    • Navigate to samples/graph-app-installation-lifecycle/csharp/AppInstallation folder
    • Select AppInstallation.csproj file
    • Press F5 to run the project
  1. Setup Manifest for Teams

  • This step is specific to Teams.

    • Edit the manifest.json contained in the ./Manifest 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.
    • Zip up the contents of the Manifest 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 ./Manifest folder, select the zip folder, and choose Open.
    • Select Add in the pop-up dialog box. Your app is uploaded to Teams.

  • Upload app manifest file (zip file) to your team

Note: If you are facing any issue in your app, please uncomment this line and put your debugger for local debug.

Running the sample

Further Reading