| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Meeting App Extensibility | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/meeting-app-extensibility.md | To add tabs to an existing meeting: 1. In your calendar, select a meeting to which you want to add a tab. 1. Select the **Details** tab and select <img src="~/assets/images/apps-in-meetings/plusbutton.png" alt="Plus button" width="30"/>. The tab gallery appears. - <img src="../assets/images/apps-in-meetings/PreMeeting.png" alt="Pre-meeting experience" width="900"/> + :::image type="content" source="~/assets/images/apps-in-meetings/Pre-Meeting-002.png" alt-text="Pre-meeting app experience"::: 1. In the tab gallery, select the app that you want to add and follow the steps as required. The app is installed as a tab. To add tabs to an existing meeting: # [Desktop](#tab/desktop) - # [Mobile](#tab/mobile) To use tabs during a meeting: # [Desktop](#tab/desktop) - - # [Mobile](#tab/mobile) After entering the meeting and adding the app from desktop or web, the app is visible in mobile Teams meeting under the **Apps** section. Select **Apps** to show the list of apps. User can launch any of the apps as an in-meeting side panel of the app. The following image displays the **Contoso** tab with results of poll and feedba # [Desktop](#tab/desktop) - # [Mobile](#tab/mobile) -<img src="../assets/images/apps-in-meetings/mobilePostMeeting.png" alt="Mobile post meeting view" width="200"/> The Teams unified meetings apps allow you to design your app based on participan ## Participant roles in a meeting - The default participant settings are determined by an organization's IT administrator. The following are the participant roles in a meeting: |
| platform | Moodle Lti Apps | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/moodle-lti-apps.md | - Title: Moodle LTI apps -description: Classification of Moodle LTI apps -----# Moodle LTI apps --Learning Tools Interoperability (LTI) is a specification developed to integrate learning applications with learning management platforms. The following list provides LTI's apps for Moodle LMS: --## OneDrive LTI app --The OneDrive LTI app allows the faculty and students to access their OneDrive files in LMS, which also includes the following: --* Access to class files in shared ODSP libraries from within LMS. -* Share files using links within LMS. --## Class Teams LTI app --Class Teams LTI app allows faculty and students to easily navigate between Teams and their respective courses in LMS. --Based on the enrolment roster of the LMS course, faculty can do the following: --* Create a class team app with proper user roles for the LMS course. -* Create a class team app, which adheres to LMS privacy policies and also supports teams administrator. --After creating the Class team app, both faculty and students can do the following: --* Access the team from within the LMS course or Teams. -* Engage using desktop, mobile, and web platforms. --## Teams Meetings LTI app --The Teams meetings LTI app helps faculty and students to integrate class meetings to their courses and also allows the users to do the following: --* Schedule individual or recurring meetings within the course in LMS and set meeting options. -* View past and upcoming meetings within LMS course calendar. -* Join or edit the details of Teams meeting from the LMS course. -* Engage using desktop and web platforms. --> [!NOTE] -> The Team Meeting LTI app doesn't support channel meetings, display of meeting recordings, or syncing of meetings with the LMS calendar. --## See also --* [Microsoft 365 plugins](m365-plugins/m365-plugins-overview.md) -* [Partner apps for Moodle](partner-apps-for-moodle.md) |
| platform | Moodle Overview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/moodle-overview.md | keywords: moodle LMS mConnect deep links <!-- [Moodle](https://moodle.com/about/) is the worldΓÇÖs largest open-source learning management system (LMS). With greater than 30 years of experience in remote learning, it has attracted around 300 million users worldwide with its rich set of hosted and cloud-based services. Combining Moodle LMS and Teams provides an enhanced learning experience with modern superpowers. This content is modified as per the requirement.--> - The following image demonstrates Moodle LMS: - <!-- Query on this image about what is meant by section --> + <!--The following image demonstrates Moodle LMS: + Query on this image about what is meant by section ## Moodle LMS accessibility Moodle LMS helps users access the following apps: -* **Moodle LTI apps**: The following Learning Tools Interoperability (LTI) apps are available for Moodle LMS: - * OneDrive LTI app, which provides services like accessing and sharing personal and class files within LMS. - * Class Teams LTI app, which helps faculty to create a class with user roles within the LMS courses. The Class LTI app provides required access to students to various engaging courses. - * Teams meetings LTI app, which helps faculty and students to engage using desktop, web platforms, and to integrate class meetings in their LMS course. For more information, see [Moodle LTI apps](moodle-lti-apps.md). - * **Microsoft 365 plugins**: The Microsoft 365 plugins are designed to ensure integration between Moodle sites and Microsoft Teams. These plugins can be used independently, or in partnership to achieve distinct user requirements. For more information, see [Microsoft 365 plugins](m365-plugins/m365-plugins-overview.md). * **Partner apps for Moodle**: All the partner set of apps for Moodle and Teams are available in Microsoft Store. For more information see [Partner apps for Moodle](partner-apps-for-moodle.md). The following scenarios describe the accelerated learning potential combining Mi ## See also * [Microsoft 365 plugins](m365-plugins/m365-plugins-overview.md)-* [Moodle LTI Apps](moodle-lti-apps.md) * [Partner apps for Moodle](partner-apps-for-moodle.md) * [Moodle FAQ](faqs.md) |
| platform | Manifest Schema Dev Preview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema-dev-preview.md | Specify and consolidate authorization related information for the app. |Name| Type|Maximum size|Required |Description| |||||| |`type`|string||Γ£ö| The type of the resource-specific permission. Options: `Application` and `Delegated`.|-|`name`|string|128 characters|Γ£ö|The name of the resource-specific permission. <br> For more information, see [Application permissions](../../graph-api/rsc/resource-specific-consent.md) and [Delegated permissions](#delegated-permissions).| +|`name`|string|128 characters|Γ£ö|The name of the resource-specific permission. For more information, see [Resource-specific application permissions](#resource-specific-application-permissions) and [Resource-specific delegated permissions](#resource-specific-delegated-permissions)| -### Delegated permissions +#### Resource-specific application permissions -Delegated permissions allow the app to access data on behalf of the signed-in user. +Application permissions allow the app to access data without a signed-in user. For information on application permissions, see [Resource Specific Consent for MS Graph and MS BotSDK](../../graph-api/rsc/resource-specific-consent.md). -* **Resource-specific permissions for teams** +#### Resource-specific delegated permissions ++Delegated permissions allow the app to access data on behalf of the signed-in user. ++* **Resource-specific delegated permissions for teams** |**Name**|**Description**| ||| Delegated permissions allow the app to access data on behalf of the signed-in us |`InAppPurchase.Allow.Group`| Allows the app to show marketplace offers to users in this team and complete their purchases within the app, on behalf of the signed-in user.| |`ChannelMeetingStage.Write.Group`| Allows the app to show content on the meeting stage in channel meetings associated with this team, on behalf of the signed-in user.| -* **Resource-specific permissions for chats or meetings** +* **Resource-specific delegated permissions for chats or meetings** |**Name**|**Description**| ||| Delegated permissions allow the app to access data on behalf of the signed-in us |`OnlineMeetingParticipant.Read.Chat`|Allows the app to read participant information, including name, role, id, joined, and left times, of meeting associated with this chat, on behalf of the signed-in user.| |`OnlineMeetingParticipant.ToggleIncomingAudio.Chat`|Allows the app to toggle incoming audio for participants in meetings associated with this chat, on behalf of the signed-in user.| -* **Resource-specific permissions for users** +* **Resource-specific delegated permissions for users** |**Name**|**Description**| ||| |
| platform | Manifest Schema | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema.md | Specify and consolidate authorization related information for the app. |Name| Type|Maximum size|Required |Description| |||||| |`type`|string||Γ£ö| The type of the resource-specific permission. Options: `Application` and `Delegated`.|-|`name`|string|128 characters|Γ£ö|The name of the resource-specific permission. <br> For more information, see [Application permissions](../../graph-api/rsc/resource-specific-consent.md) and [Delegated permissions](#delegated-permissions).| +|`name`|string|128 characters|Γ£ö|The name of the resource-specific permission. For more information, see [Resource-specific application permissions](#resource-specific-application-permissions) and [Resource-specific delegated permissions](#resource-specific-delegated-permissions)| -### Delegated permissions +#### Resource-specific application permissions ++Application permissions allow the app to access data without a signed-in user. For information on application permissions, see [Resource Specific Consent for MS Graph and MS BotSDK](../../graph-api/rsc/resource-specific-consent.md). ++#### Resource-specific delegated permissions Delegated permissions allow the app to access data on behalf of the signed-in user. -* **Resource-specific permissions for teams** +* **Resource-specific delegated permissions for teams** |**Name**|**Description**| ||| Delegated permissions allow the app to access data on behalf of the signed-in us |`InAppPurchase.Allow.Group`| Allows the app to show marketplace offers to users in this team and complete their purchases within the app, on behalf of the signed-in user.| |`ChannelMeetingStage.Write.Group`| Allows the app to show content on the meeting stage in channel meetings associated with this team, on behalf of the signed-in user.| -* **Resource-specific permissions for chats or meetings** +* **Resource-specific delegated permissions for chats or meetings** |**Name**|**Description**| ||| Delegated permissions allow the app to access data on behalf of the signed-in us |`OnlineMeetingParticipant.Read.Chat`|Allows the app to read participant information, including name, role, id, joined, and left times, of meeting associated with this chat, on behalf of the signed-in user.| |`OnlineMeetingParticipant.ToggleIncomingAudio.Chat`|Allows the app to toggle incoming audio for participants in meetings associated with this chat, on behalf of the signed-in user.| -* **Resource-specific permissions for users** +* **Resource-specific delegated permissions for users** |**Name**|**Description**| ||| |
| platform | Access Teams Context | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/access-teams-context.md | The following code provides an example of context variable: "sessionId": "The unique ID for the current Teams session for use in correlating telemetry data", "userTeamRole": "The user's role in the team", "isTeamArchived": "Indicates if team is archived",- "hostClientType": "The type of host client. Possible values are android, ios, web, desktop, rigel", + "hostClientType": "The type of host client. Possible values are android, ios, web, desktop, surfaceHub, teamsRoomsAndroid, teamsPhones, teamsDisplays rigel (deprecated, use teamsRoomsWindows instead)", "frameContext": "The context where tab URL is loaded (for example, content, task, setting, remove, sidePanel)", "sharepoint": "The SharePoint context is available only when hosted in SharePoint", "tenantSKU": "The license type for the current user tenant. Possible values are enterprise, free, edu, unknown", |
| platform | Visual Studio Overview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/visual-studio-overview.md | description: Get started building great custom apps directly within Visual Studi keywords: teams visual studio toolkit ms.localizationpriority: medium Last updated : 1/13/2022 -# Build apps with the Teams Toolkit and Microsoft Visual Studio +# Teams Toolkit for Visual Studio -The Microsoft Teams Toolkit enables you to create custom Teams apps directly within the Visual Studio integrated development environment (IDE). The Microsoft Teams toolkit guides you through the process and provides everything you need to build, debug, and launch your Teams app. +Build, test, and develop for Teams inside your IDE. -## Prerequisites +Teams Toolkit's extension for Visual Studio makes it easy to create new projects for Teams, automatically setup apps in Teams Developer Portal, run and debug in Teams, configure cloud hosting, and use [TeamsFx](https://github.com/OfficeDev/teamsfx) from your IDE. -1. [Enable developer preview](../resources/dev-preview/developer-preview-intro.md#enable-developer-preview). +## Install Teams Toolkit for Visual Studio -2. Make sure that the **<span>ASP.NET</span> and web development module** has been added to your Visual Studio instance. For more information, see [Modify Visual Studio by adding or removing workloads and components](/visualstudio/install/modify-visual-studio?view=vs-2019&preserve-view=true). +>[!NOTE] +> As a prerequisite, ensure you use Visual Studio 2022 17.1 Preview 2 or newer to follow the instructions below. - +1. If you already have Visual Studio 2022 17.1 Preview 2 installed, skip to the next step. Otherwise, [install Visual Studio 2022 Preview](https://visualstudio.microsoft.com/vs/preview/). +2. Open the Visual Studio Installer. +3. Select **Modify** for your existing VS 2022 Preview installation. +4. Select the **ASP.NET and web development** workload. +5. On the right, expand the **ASP.NET and web development** section and select **Microsoft Teams development tools** in the Optional list of components. +6. Select **Install** or **Modify** in the Visual Studio Installer to complete the installation process. -## Install the Teams Toolkit + -The Microsoft Teams Toolkit for Visual Studio is available for download from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=msft-vsteamstoolkit.vsteamstoolkit) or directly from the **Extensions** menu within Visual Studio. +## Get started quickly with a new project -## Use the toolkit +Teams Toolkit project templates provide all code, files, and configuration you need to get started with a Teams app project. -- [Set up a new project](#set-up-a-new-teams-project)-- [Configure your app](#configure-your-app)-- [Run your app in Teams](#install-and-run-your-app-locally)-- [Validate your app](#validate-your-app)-- [Publish your app](#publish-your-app-to-teams)+The Microsoft Teams App project template allows you to specify a Microsoft 365 account that is required to automatically register and configure your new Teams app. -## Set up a new Teams project +> [!NOTE] +> If you do not have a Microsoft 365 account, you can sign up for a [Microsoft 365 Developer Program](https://developer.microsoft.com/microsoft-365/dev-program) subscription. It's free for 90 days and renews as long as you are using it for development activity. If you have a Visual Studio Enterprise or Professional subscription, both programs include a free Microsoft 365 [developer subscription](https://aka.ms/MyVisualStudioBenefits), active for the life of your Visual Studio subscription. For more information, see [set up a Microsoft 365 developer subscription](/office/developer-program/office-365-developer-program-get-started). -1. Launch Visual Studio 2019. -2. Select **Create a new project**. -3. Search for **Microsoft Teams App** and select **Next**. -4. In the **Configure your new project**, enter the **Project name**, **Location**, and **Solution name**. -5. Select **Next** to enter a name for the app. -6. In the Additional Information screen, enter an **Application Name** and **Developer or Company name** for your Teams app. +1. Launch Visual Studio 2022. +1. In the start window, choose **Create a new project**. +1. In the **Search for templates** box, enter Microsoft Teams App. +1. Select the **Microsoft Teams App** template and select **Next**. +1. In the **Configure your new project** window, type or enter _HelloTeams_ in the **Project name** box. Then, select **Create**. +1. In the **Create a new Teams application** window, choose or sign in to a Microsoft 365 account using the **Choose an account** selector. Then, select **Create**. -## Configure your app + -At its core, the Teams app embraces three components: +Visual Studio will open up your new project and Teams Toolkit will setup you new project in Teams Developer Portal. The project will be added for the Teams organization linked to the Microsoft 365 account you chose in the steps above and create a new Azure Active Directory registration. This is required for the app to run in Teams. -- The Microsoft Teams client (web, desktop or mobile) where users interact with your app.-- A server that responds to requests for content displayed in Teams. For example, HTML tab content or a bot adaptive card.-- A Teams app package consists of three files:+## Run and debug your app in Teams - > [!div class="checklist"] - > - > - The manifest.json - > - A [color icon](../resources/schem#icons) for your app to display in the public or organization app catalog. - > - An [outline icon](../resources/schem#icons) for display on the Teams activity bar. +You can launch your app project running locally from Visual Studio. -When an app is installed, the Teams client parses the manifest file to determine needed information like the name of your app and the URL where the services are located. +1. Open or [create a Teams app project](#get-started-quickly-with-a-new-project). +2. Press **F5** or select **Debug > Start Debugging** in Visual Studio. -> [!NOTE] ->If you have not done so already, you must sign in to your Microsoft 365 account to continue with the development process. -> -> If you do not have a Microsoft 365 account, you can sign up for a [Microsoft 365 Developer Program](https://developer.microsoft.com/microsoft-365/dev-program) subscription. It's free for 90 days and renews as long as you are using it for development activity. If you have a Visual Studio Enterprise or Professional subscription, both programs include a free Microsoft 365 [developer subscription](https://aka.ms/MyVisualStudioBenefits), active for the life of your Visual Studio subscription. For more information, see [set up a Microsoft 365 developer subscription](/office/developer-program/office-365-developer-program-get-started). +Visual Studio will launch your Teams app project in a browser and start debugging. ++## Host your Teams app in the cloud and preview it ++You can create and automatically configure cloud resources for hosting your app in Azure using Teams Toolkit. -### Configuration steps +1. Select the **Project > Teams Toolkit > Provision in the Cloud** menu. +2. In the Select your subscription window, choose the Azure subscription you want to use to create resources with. -1. To configure your app, select the **Project > TeamsFx > Configure for SSO...** menu. +Teams Toolkit will create Azure resources in this subscription but no code is deployed during this step. To deploy your project to these new resources: -When prompted, sign in to your Microsoft account that has an M365 tenant. +1. Select the **Project > Teams Toolkit > Deploy in the Cloud** menu. -## Install and run your app locally +## Preview your app running from cloud resources -Press F5 to start debugging. The app installation dialog box appears in the Teams client. +You can run your app in a browser using the remote resources to verify that everything works. It's not possible to debug during in this scenario yet. -## Validate your app +1. Select the **Project > Teams Toolkit > Preview Teams app** menu. -The **Project > TeamsFx Validate > Teams Manifest** menu allows you to check that your app package is valid. +Your app will open in a browser and use the resources created by the Provision and Deploy steps. ## Publish your app to Teams |