Updates from: 06/18/2021 03:18:36
Service Microsoft Docs article Related commit history on GitHub Change details
platform Calls Meetings Bots Overview https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/bots/calls-and-meetings/calls-meetings-bots-overview.md
keywords: calling calls audio video IVR voice online meetings
# Calls and online meetings bots
-> [!NOTE]
-> Support for calls and online meeting bots is currently not supported on the Microsoft Teams mobile platform.
- Bots can interact with Teams calls and meetings using real-time voice, video, and screen sharing. With [Microsoft Graph APIs for calls and online meetings](/graph/api/resources/communications-api-overview?view=graph-rest-beta&preserve-view=true), Teams apps can now interact with users using voice and video to enhance the experience. These APIs allow you to add the following new features: * Interactive voice response (IVR).
Calls are either peer-to-peer between a person and your bot, or multiparty betwe
Following are the different call types and permissions required for the call: * A user can initiate a peer-to-peer call with your bot or invite your bot into an existing multiparty call. The multiparty call is not enabled yet in the Teams user interface.+
+ > [!NOTE]
+ > User initiated calls to a bot are currently not supported on Microsoft Teams mobile platform.
+ * Graph permissions are not necessary for a user to initiate a peer-to-peer call with your bot. Additional permissions are needed for your bot to participate in a multiparty call, or for your bot to initiate a peer-to-peer call with a user. * A call can start as peer-to-peer and eventually become a multiparty call. Your bot can initiate multiparty calls by inviting others, provided your bot has the proper permissions. If your bot does not have permissions to participate in group calls and if a participant adds another participant to the call, your bot is dropped from the call.
platform Authentication https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/authentication/authentication.md
Use the web-based authentication flow for [tabs](~/tabs/what-are-tabs.md) and ch
The Azure Bot FrameworkΓÇÖs OAuthPrompt makes authentication easier for apps using conversational bots. Use Azure Bot Framework's token service to assist with token caching.
-For more information on using the OAuthPrompt, see:
+For more information on using OAuthPrompt, see:
* [Bot authentication flow overview](~/bots/how-to/authentication/auth-flow-bot.md) describes how authentication works within a bot in the app in Teams. This shows a non-web-based authentication flow used for bots on Teams web, desktop app, and mobile apps. * [Bot authentication](~/bots/how-to/authentication/add-authentication.md) describes how to add OAuth authentication to the Teams bot.
platform Understand Use Cases https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/design/understand-use-cases.md
Knowing who your users are helps you to craft the right experience. Do you expec
Remember, users can discover your app in a variety of ways. They might be the ones installing it or they might be introduced to your app when another user uses it to share content. If you want more users to use your app, you must look for ways to introduce yourself to everyone.
-Above all else, remember that nobody likes spam. Blasting away with personal and channel messages is a good way to get un-installed quickly!
+Above all, remember that nobody likes spam. Blasting away with personal and channel messages is a good way to get un-installed quickly!
## Plan for the future
platform Mobile Camera Image Permissions https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
For effective integration, you must have a good understanding of [code snippets]
It is important to familiarize yourself with the [API response errors](#error-handling) to handle the errors in your Teams app. > [!NOTE]
-> Currently, Microsoft Teams support for media capabilities is only available for mobile clients.
+> * Currently, Microsoft Teams support for media capabilities is only available for mobile clients.
+> * Currently, Teams does not support device permissions for multi window apps, tabs, and the meeting sidepanel.
## Update manifest
platform Native Device Permissions https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/device-capabilities/native-device-permissions.md
By accessing the device capabilities, you can build richer experiences on the Te
* Record audio memos and save them for later use. * Use the location information of the user to display relevant information.
+> [!NOTE]
+> Currently, Teams does not support device permissions for multi window apps, tabs, and the meeting sidepanel.
+ ## Access device permissions The [Microsoft Teams JavaScript client SDK](/javascript/api/overview/msteams-client?view=msteams-client-js-latest&preserve-view=true) provides the tools necessary for your Teams mobile app to access the userΓÇÖs [device permissions](#manage-permissions) and build a richer experience.
platform First App Blazor https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/get-started/first-app-blazor.md
You can now use the **Preview in Teams** button at the top of the page to launch
## See also - [Create a Teams app with React](first-app-react.md)
+- [Create a Teams app as a SharePoint Web Part](first-app-spfx.md)
- [Create a conversational bot app](first-app-bot.md) - [Create a messaging extension](first-message-extension.md)
platform First App React https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/get-started/first-app-react.md
# Build and run your first Microsoft Teams app with React
-In this tutorial, you can create a new Microsoft Teams app in React that implements a simple personal app to pull information from the Microsoft Graph. (A *personal app* includes a set of tabs scoped for individual use.) During the tutorial, you can learn about the structure of a Teams app, how to run an app locally, and how to deploy the app to Azure.
+In this tutorial, you will create a new Microsoft Teams app in React that implements a simple personal app to pull information from the Microsoft Graph. For example, a *personal app* includes a set of tabs scoped for individual use. During the tutorial, you will learn about the structure of a Teams app, how to run an app locally, and how to deploy the app to Azure.
-The app that is built displays basic user information for the current user. When permission is granted, the app connects to Microsoft Graph as the current user to get the complete profile.
+The app that is built displays basic user information for the current user. When permission is granted, the app will connect to the Microsoft Graph as the current user to get the complete profile.
## Before you begin
-Make sure your development environment is set up by installing the [prerequisites](prerequisites.md)
+Make sure your development environment is set up by installing the [prerequisites](prerequisites.md).
> [!div class="nextstepaction"] > [Install prerequisites](prerequisites.md)
Use the `teamsfx` CLI to create your first project. Start from the folder where
teamsfx new ```
-The CLI walks through some questions to create the project. Each question tells you how to answer it, for example, use arrow keys to select an option. When you have answered the question, confirm your choice by pressing **Enter**.
+The CLI walks through some questions to create the project. Each question will tell you how to answer it, for example, use arrow keys to select an option. When you have answered the question, confirm your choice by pressing **Enter**.
1. Select **Create a new Teams app**. 1. Choose the **Tab** capability.
Your app is now displayed:
:::image type="content" source="../assets/images/teams-toolkit-v2/react-finished-app.png" alt-text="Screenshot of the completed app":::
-You can do normal debugging activities as if this were any other web application (such as setting breakpoints). The app supports hot reloading. If you change any file within the project, the page is reloaded.
+You can do normal debugging activities as if this were any other web application, such as setting breakpoints. The app supports hot reloading. If you change any file within the project, the page will be reloaded.
<!-- markdownlint-disable MD033 --> <details>
When you pressed F5, the Teams Toolkit:
1. *Sideloaded* your app in Teams. 1. Started your application backend running locally using [Azure Function Core Tools](/azure/azure-functions/functions-run-local?#start). 1. Started your application front-end hosted locally.
-1. Started Microsoft Teams in a web browser with a command to instruct Teams to side load the application from `https://localhost:3000/tab` (the URL is registered inside the application manifest).
+1. Started Microsoft Teams in a web browser with a command to instruct Teams to side load the application from `https://localhost:3000/tab`. This is the URL registered in the application manifest.
</details>
To successfully run your app in Teams, you must have a Teams account that allows
Before deployment, the application has been running locally:
-1. The backend runs using _Azure Functions Core Tools_.
+1. The backend runs using **Azure Functions Core Tools**.
1. The application HTTP endpoint, where Microsoft Teams loads the application, runs locally.
-Deployment involves provisioning resources on an active Azure subscription and deploying (uploading) the backend and frontend code for the application to Azure.
+Deployment involves provisioning resources on an active Azure subscription and deploying or uploading the backend and frontend code for the application to Azure.
-1. The backend (if configured) uses a variety of Azure services, including Azure App Service and Azure Storage.
-1. The frontend application is deployed to an Azure Storage account configured for static web hosting.
+1. The backend if configured uses a variety of Azure services, including Azure App Service and Azure Storage.
+1. The frontend application will be deployed to an Azure Storage account configured for static web hosting.
</details> ## See also
+- [Create a Teams app with Blazor](first-app-blazor.md)
- [Create a Teams app as a SharePoint Web Part](first-app-spfx.md) (Azure not required) - [Create a conversational bot app](first-app-bot.md) - [Create a messaging extension](first-message-extension.md)
platform Resource Specific Consent https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/graph-api/rsc/resource-specific-consent.md
keywords: teams authorization OAuth SSO AAD rsc Graph
# Resource-specific consent (RSC)
+> [!NOTE]
+> Resource-specific consent for chat scope is available in [public developer preview](../../resources/dev-preview/developer-preview-intro.md) only.
+ Resource-specific consent (RSC) is a Microsoft Teams and Microsoft Graph API integration that enables your app to use API endpoints to manage specific resourcesΓÇöeither teams or chatsΓÇöwithin an organization. The resource-specific consent (RSC) permissions model enables *team owners* and *chat owners* to grant consent for an application to access and/or modify a team's data and a chat's data, respectively. The granular, Teams-specific, RSC permissions define what an application can do within a specific resource: ## Resource-specific permissions
platform Test Resource Specific Consent https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/graph-api/rsc/test-resource-specific-consent.md
keywords: teams authorization OAuth SSO AAD rsc Postman Graph
# Test resource-specific consent permissions in Teams
+> [!NOTE]
+> Resource-specific consent for chat scope is available in [public developer preview](../../resources/dev-preview/developer-preview-intro.md) only.
+ Resource-specific consent (RSC) is a Microsoft Teams and Graph API integration that enables your app to use API endpoints to manage specific resourcesΓÇöeither teams or chatsΓÇöwithin an organization. For more information, see [Resource-specific consent (RSC) ΓÇö Microsoft Teams Graph API](resource-specific-consent.md). > [!NOTE]
Resource-specific consent (RSC) is a Microsoft Teams and Graph API integration t
>[!NOTE] >If the app is meant to support installation in both team and chat scopes, then both team and chat permissions can be specified in the same manifest under `applicationPermissions`.
-### Test added RSC permissions to a team using the Postman app
+## Test added RSC permissions to a team using the Postman app
To check whether the RSC permissions are being honored by the API request payload, you need to copy the [RSC JSON test code for team](test-team-rsc-json-file.md) into your local environment and update the following values:
platform Get Started Use App Studio https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/includes/get-started/get-started-use-app-studio.md
Complete the following steps to update the app package:
<img width="450px" alt="App Studio" src="~/assets/images/get-started/AppStudio.png"/>
- The sample comes with its own manifest and is designed to build an app package when the project is built. On .NET this is done in Visual Studio and on Node.js this is done by typing `gulp` at the command line in the root directory of the project.
+ The sample comes with its own manifest and is designed to build an app package when the project is built. You can build the app package on .NET with Visual Studio. In Visual Studio, the manifest.json file is located in under **Manifest** in `Microsoft.Teams.Samples.HelloWorld.Web`. This step is described by the following image:
+
+ <img width="450px" alt="Build the app package on .NET with Visual Studio" src="~/assets/images/get-started/app-package-on-.NET-with-Visual-Studio.png"/>
+
+ You can build the app package on Node.js by typing `gulp` at the command line in the root directory of the project.
```bash $ gulp
platform Whats New https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/whats-new.md
Developer preview is a public program that provides early access to unreleased T
| **Date** | **Notes** | **Changed topics** | | -- | | |
+|06/16/2021| Resource-specific consent for chats. |[Resource-specific consent](graph-api/rsc/resource-specific-consent.md), [Test resouce-specific consent permissions in Teams](graph-api/rsc/test-resource-specific-consent.md)|
|05/26/2021|Build tabs with Adaptive Cards|[Build tabs](tabs/how-to/build-adaptive-card-tabs.md)| |05/25/2021| Updated Teams Toolkit for [Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension) and [Visual Studio](https://marketplace.visualstudio.com/items?itemName=msft-vsteamstoolkit.vsteamstoolkit&ssr=false#overview). | [Get started with Teams app development](~/get-started/prerequisites.md) | |05/25/2021| New Developer Portal for Teams introduced for managing your Teams apps. | [Developer Portal for Teams](concepts/build-and-test/teams-developer-portal.md) |