This repository contains community samples that demonstrate different usage patterns for developing on Microsoft Teams as a platform. Samples are generally not production-ready, but are intended to show developers specific patterns and use cases for use in complete applications.
We welcome community contributions to the samples folder in this repository for demonstrating different patterns and use cases with Microsoft Teams. Samples should follow folder naming conventions, and should contain a readme markdown file based on the appropriate template. Due to the diversity of technologies in use, each sample readme includes instructions for building and testing the sample. Please see our contribution guidelines for details.
If you use 3rd party libraries, please make sure that library license allows distributions of it as part of your sample.
Microsoft Teams is highly extensible, allowing 3rd party and custom applications to run alongside the many Office 365 services already included in Teams. Just as you can add a Word tab or the Who bot in Teams, you can write your own tabs and bots. You can also write applications that run outside the Teams UI and use the Microsoft Graph API to access and curate Teams content.
The best way to navigate the samples is to use the Sample Navigator. It will allow you to dial in the Teams app features, language, and other technologies you want samples for.
Each sample is in a folder named with a prefix as follows:
Prefix | Description |
---|---|
app- | These are samples of apps that have multiple features such as a tab and a bot |
bot- | These are simple bots, intended to show a single capability or pattern |
msgext- | These are simple messaging extensions, intended to show a single capability or pattern |
tabs- | These are simple tabs, intended to show a single capability or pattern |
If you have issues or questions on a specific sample, please use the issues list in this repository.
If you have issues with the libraries, SDKs, services, or tools used to develop your applications, please file them in the appropriate location for that technology.
Technology | Location for issues/questions |
---|---|
Bot Framework SDK | Bot Framework resources |
Microsoft Graph | Microsoft Graph Support |
Microsoft Teams JavaScript SDK | Use the feedback link at the footer of the docs page |
SharePoint Framework with Teams | sp-dev-docs repository issue list |
Due to the diversity of the samples and technologies, there are no fixed instructions for building or using the samples. Each sample should include a readme file with build instructions.
These samples are from the Microsoft 365 developer community. We welcome your samples and suggestions for new samples.
Please have a look on our Contribution Guidance before submitting your pull requests, so that we can get your contribution processed as fast as possible. Thx.
Sharing is caring!
-
App Templates for Microsoft Teams: These open source, production-ready applications are also great samples showing how to build robust Teams applications complete with Resource Manager templates for easy deployment in Azure
-
BotBuilder-Samples: Dozens of simple samples showing how to do various things in Bot Builder SDK, including some Teams examples
-
Contoso HR Sample: HR recruiting sample for hands-on lab experience. Uses Bot Framework 4.4 with Teams-specific operations hard-coded; needs update to 4.6+ to follow best practices.
- Microsoft Teams Sample Complete (C#, Node): This Bot sample uses v3 of the Bot Builder SDK which is now obsolete
- Azure Bot Service: main page
- Azure Bot SDK: main page, repo
- Azure Cognitive Services:
- QnA Maker finds answers to questions
- LUIS predicts user's intent and enties
- QnA Maker and LUIS together
- Bots in Teams
- Tutorials:
- Microsoft Teams JavaScript Library: This library is used in Teams tabs to allow JavaScript running on the tab's web page to interact with Microsoft Teams