-Messaging bots use HTTP, but calls and online meeting bots use the lower-level TCP. Ngrok supports TCP tunnels in addition to HTTP tunnels.

->

-

- - Cloud Service.

- - Service Fabric with Virtual Machine Scale Sets (VMSS).

- - Infrastructure as a Service (IaaS) Virtual Machine (VM).

- - For obtaining and configuring an ILPIP for an Azure Cloud Service, see [instance level public IP classic overview](/azure/virtual-network/virtual-networks-instance-level-public-ip).

- - For configuring an ILPIP for a VM Scale Set, see [public IPv4 per virtual machine](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine).

- - For an Azure Cloud Service, this requires an instance input endpoint. For more information, see [enable communication for role instances in Azure](/azure/cloud-services/cloud-services-enable-communication-role-instances).

- - For a VM Scale Set, a NAT rule on the load balancer must be configured. For more information, see [virtual networks and virtual machines in Azure](/azure/virtual-machines/windows/network-overview).

-> By adding your chatbot to Microsoft Teams, some of the data, such as bot content and user chat content, is shared with Microsoft Teams. It means that your data flows outside of your [organizationΓÇÖs compliance and geographic or regional boundaries](/power-virtual-agents/data-location). <br/>

- > [!IMPORTANT]

- > [!IMPORTANT]

- > The bot stores the token it receives from the identity provider and associates it with a specific user, but it is marked as "pending validation".

- 1. **Validate what's received from the identity provider.** The value of the `state` parameter must be confirmed against what was saved earlier.

-**To upload a file to a user**

-> * The `ChannelMessage.Read.Group` RSC permission may not be used by bots as a way to extract large amounts of customer data.

- await turnContext.SendActivityAsync(MessageFactory.Text("Using RSC the bot can recieve messages across channels in team without being @mentioned."));

-|Channel messages with RSC permissions| Microsoft Teams sample app demonstrating on how a bot can receive all channel messages with RSC without being @mentioned.| [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-receive-channel-messages-withRSC/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-receive-channel-messages-withRSC/nodejs) |

- self, channel_info: ChannelInfo, team_info: TeamInfo, turn_context: TurnContext

- return await turn_context.send_activity(

- MessageFactory.text(

- f"The new channel is {channel_info.name}. The channel id is {channel_info.id}"

- )

- )

- self, channel_info: ChannelInfo, team_info: TeamInfo, turn_context: TurnContext

- return await turn_context.send_activity(

- MessageFactory.text(f"The new channel name is {channel_info.name}")

- )

- self, channel_info: ChannelInfo, team_info: TeamInfo, turn_context: TurnContext

- return await turn_context.send_activity(

- MessageFactory.text(f"The deleted channel is {channel_info.name}")

- )

- self, channel_info: ChannelInfo, team_info: TeamInfo, turn_context: TurnContext

- return await turn_context.send_activity(

- MessageFactory.text(

- f"The restored channel is {channel_info.name}. The channel id is {channel_info.id}"

- )

- )

- self, teams_members_added: [TeamsChannelAccount], turn_context: TurnContext

- for member in teams_members_added:

- await turn_context.send_activity(

- MessageFactory.text(f"Welcome your new team member {member.id}")

- )

- return

- self, teams_members_removed: [TeamsChannelAccount], turn_context: TurnContext

- for member in teams_members_removed:

- await turn_context.send_activity(

- MessageFactory.text(f"Say goodbye to {member.id}")

- )

- return

- self, team_info: TeamInfo, turn_context: TurnContext

- return await turn_context.send_activity(

- MessageFactory.text(f"The new team name is {team_info.name}")

- )

- self, team_info: TeamInfo, turn_context: TurnContext

- //handle delete event

- )

- self, team_info: TeamInfo, turn_context: TurnContext

- return await turn_context.send_activity(

- MessageFactory.text(f"The team name is {team_info.name}")

- )

- self, team_info: TeamInfo, turn_context: TurnContext

- return await turn_context.send_activity(

- MessageFactory.text(f"The team name is {team_info.name}")

- )

- self, team_info: TeamInfo, turn_context: TurnContext

- return await turn_context.send_activity(

- MessageFactory.text(f"The team name is {team_info.name}")

- )

- self, message_reactions: List[MessageReaction], turn_context: TurnContext

- for reaction in message_reactions:

- activity = await self._log.find(turn_context.activity.reply_to_id)

- if not activity:

- await self._send_message_and_log_activity_id(

- turn_context,

- f"Activity {turn_context.activity.reply_to_id} not found in log",

- )

- else:

- await self._send_message_and_log_activity_id(

- turn_context,

- f"You added '{reaction.type}' regarding '{activity.text}'",

- )

- return

- self, message_reactions: List[MessageReaction], turn_context: TurnContext

- for reaction in message_reactions:

- activity = await self._log.find(turn_context.activity.reply_to_id)

- if not activity:

- await self._send_message_and_log_activity_id(

- turn_context,

- f"Activity {turn_context.activity.reply_to_id} not found in log",

- )

- else:

- await self._send_message_and_log_activity_id(

- turn_context,

- f"You removed '{reaction.type}' regarding '{activity.text}'",

- )

- return

-

-> For Microsoft Teams to refer to your bot's app ID, enable [sideloading of apps](/microsoftteams/platform/concepts/build-and-test/prepare-your-o365-tenant#enable-custom-teams-apps-and-turn-on-custom-app-uploading).

-> * The thread limit of 3600 seconds and 1800 operations applies only if multiple bot messages are sent to a single user.

-* * *

-* * *

-## See also

-* [Authenticate a user in a Microsoft Teams tab](../../tabs/how-to/authentication/auth-tab-aad.md)

-1. [Localize strings in your app manifest](#localize-strings-in-your-app-manifest).

-You must use the Microsoft Teams app schema `v1.5` and later to localize your app. You can do this by setting the `$schema` attribute in your manifest.json file to **https://developer.microsoft.com/en-us/json-schemas/teams/v1.5/MicrosoftTeams.schema.json** or higher and updating the `manifestVersion` property to `$schema` version (`1.5` in this case).

- "defaultLanguageTag": "en",

- "additionalLanguages": [

- {

- "languageTag": "es-mx",

- "file": "es-mx.json"

- }

- ]

- }

-If the user's language is set to 'en-ca', the following changes take place based on the language selection:

-Therefore, you must provide top level, language only translations in your manifest. For example, 'en' instead of 'en-us'. You must provide region level overrides only for the few strings that need them.

-Test your bot locally. For more information, see [debug your bot locally with an IDE](~/bots/how-to/debug/locally-with-an-ide.md). You can also debug your bot with [inspection middleware](/azure/bot-service/bot-service-debug-inspection-middleware?view=azure-bot-service-4.0&tabs=csharp&preserve-view=true) and [adaptive tools](/azure/bot-service/bot-service-debug-adaptive-tools?view=azure-bot-service-4.0&preserve-view=true).

-To view the console logs, view or modify html, css, and network requests during runtime, add breakpoints to your JavaScript code, and perform interactive debugging access the DevTools. For more information, see [Access the DevTools for Teams tabs](~/tabs/how-to/developer-tools.md).

-* [Debug your tab](~/tabs/how-to/developer-tools.md)

-**To configure the default install scope in your app manifest**

-**To configure details in app manifest**

-3. For the selected group capability, the available group capabilities are, `bot`, `tab`, or `connector`.

-You can sideload Microsoft Teams apps without having to publish to your organization or the Teams store. This makes sense in the following scenarios:

-* You built an app just for yourself. For example, to automate a workflow.

-* Create your [app package](~/concepts/build-and-test/apps-package.md) and [validate it](https://dev.teams.microsoft.com/appvalidation.html) for errors.

-* Make sure that your app is running and accessible via HTTPs.

-1. Select **Apps** and choose **Upload a custom app**.

-1. Select your app package .zip file. An install dialog displays.

-1. Add your app to Teams.

-> [!NOTE]

-> `onInstallationUpdateActivityAsync()` method is used to get Microsoft Teams Locale while adding the bot to Microsoft Teams.

-## Troubleshoot upload issues

-If your app fails to sideload, do the following until the issue resolves:

-1. Go back through the instructions for [creating your app package](../../concepts/build-and-test/apps-package.md).

-1. [Validate your app package](https://dev.teams.microsoft.com/appvalidation.html) again.

-1. Ensure your app manifest matches the latest [schema](../../resources/schem).

->

- * Support ticket number.

- * Your seller ID.

- * A screenshot of the issue (if possible).

-1. [Plan your SaaS offer](#plan-your-saas-offer).

-1. [Integrate with the SaaS Fulfillment APIs](#integrate-with-the-saas-fulfillment-apis).

-1. [Build a landing page for subscription management](#build-a-landing-page-for-subscription-management).

-1. [Create your SaaS offer](#create-your-saas-offer).

-1. [Configure your app for the SaaS offer](#configure-your-app-for-the-saas-offer).

-1. [Publish your app to the Teams store](#publish-your-app).

-

-## Build a landing page for subscription management

-1. Create a [Partner Center](https://partner.microsoft.com/) account if you donΓÇÖt have one.

-1. Configure the subscription plans, pricing details, and more for your transactable SaaS offer. In particular, make sure you complete the following steps:

-

-**Include a SaaS offer with your app**

-**Free trials**

-**Test preview for monetized app**

-[Include a SaaS offer with your Microsoft Teams app](~/concepts/deploy-and-publish/appsource/prepare/include-saas-offer.md)

-* Ensure to target appropriate user persona on mobile. For example, if you're building an app that provides service to end users, and also provides data access to developers and senior managers, then the end users can use the app more while you start to build app on Teams mobile. You can cater to all the personas that you have on your desktop app however, it's recommended to start with persona with a larger base and possible early adopters for smaller screen experience. As per the example, the end users are the appropriate user personas. You can gradually add functionalities to support other user personas on your Teams mobile.

-**Consumption**

-You can show the following information:

-* Charts, graphs, and tables

-**Quick actions**

-**Enablement**

-**Consumption**

-**Quick actions**

-* Move the tasks into different categories

-**Enablement**

-**Consumption**

-**Quick Actions**

-**Enablement**

-> The latest update on how device permissions are handled in the browser is currently available in [public developer preview](../../resources/dev-preview/developer-preview-intro.md) only.

-If your Teams app has declared in the [application manifest](native-device-permissions.md#specify-permissions) that it needs device permissions, then the **App permissions** option appears for the users to enable the app's device permissions. The **App permissions** option is available in the following capabilities:

- * Camera

- * Microphone

- * Gallery

- * QR or barcode scanner

-After getting access to the device capabilities, you can integrate them with the Teams platform to enhance the collaborative experience.

-

- ## Integrate device capabilities

-You can use [Microsoft Teams JavaScript client SDK](/javascript/api/overview/msteams-client?view=msteams-client-js-latest&preserve-view=true), which provides the tools necessary for your app to access the userΓÇÖs [native device capabilities](native-device-permissions.md). Use the location APIs, such as [getLocation](/javascript/api/@microsoft/teams-js/microsoftteams.location?view=msteams-client-js-latest#getLocation_LocationProps___error__SdkError__location__Location_____void_&preserve-view=true) and [showLocation](/javascript/api/@microsoft/teams-js/microsoftteams.location?view=msteams-client-js-latest#showLocation_Location___error__SdkError__status__boolean_____void_&preserve-view=true) to integrate the capabilities within your app.

-The main advantage of integrating location capabilities in your Teams apps is that it allows web app developers on Teams platform to leverage location functionality with Microsoft Teams JavaScript client SDK.

-To integrate location capabilities, you must update the app manifest file and call the APIs. For effective integration, you must have a good understanding of [code snippets](#code-snippets) for calling the location APIs.

-> [!NOTE]

-> * The **Request Permissions** prompt is automatically displayed when a relevant Teams API is initiated. For more information, see [request device permissions](native-device-permissions.md).

-> * Device permissions are different in the browser. For more information, see [browser device permissions](browser-device-permissions.md).

-You must ensure to handle these errors appropriately in your Teams app. The following table lists the error codes and the conditions under which the errors are generated:

-|Sample name | Description | C# | Node.js |

-To integrate media capabilities you must update the app manifest file and call the media capability APIs.

-You must ensure to handle these errors appropriately in your Teams app. The following table lists the error codes and the conditions under which the errors are generated:

-You can use [Microsoft Teams JavaScript client SDK](/javascript/api/overview/msteams-client?view=msteams-client-js-latest&preserve-view=true), which provides `selectPeople` API to integrate the People Picker within your web app.

-## Advantages of integrating the native People Picker

-* People Picker helps with scenarios involving task assignment, tagging, notifying a user.

-You must call the `selectPeople` API to integrate People Picker control in your Teams app. For effective integration, you must have an understanding of [code snippet](#code-snippet) for calling the API.

-> [!NOTE]

-## `selectPeople` API

-|`setSelected`|String| It is an optional parameter. You must pass Microsoft Azure Active Directory (Azure AD) IDs of the people to be preselected. This parameter preselects people while launching the People Picker control. In case of single selection, only the first valid user is prepopulated ignoring the rest. |Null|

-You must ensure to handle the errors appropriately in your web app. The following table lists the error codes and the conditions under which the errors are generated:

-Barcode is a method of representing data in a visual and machine-readable form. The barcode contains information about a product, such as a type, size, manufacturer, and Country of origin in the form of bars and spaces. The code is read using the optical scanner on your native device camera. For a richer collaborative experience, you can integrate the QR or barcode scanner capability provided in the Teams platform with your Teams app.

-Following are the advantages of integration of QR or barcode scanner capabilities:

-> [!NOTE]

-| Code 39 | Yes | Yes |

-You must ensure to handle these errors appropriately in your Teams app. The following table lists the error codes and the conditions under which the errors are generated:

-| **Microsoft Teams product issues and failures** | If you have a Premier support contract for :::image type="icon" source="assets/icons/microsoft-icon.png" border="false"::: Microsoft 365, visit the Microsoft 365 Admin Center and use the Support menu to [open a service request ](https://admin.microsoft.com/). |

-| **General questions about Microsoft Teams** | If you have general questions on Microsoft Teams, submit your questions on :::image type="icon" source="assets/icons/microsoft-icon.png" border="false"::: [Microsoft Teams Community](https://answers.microsoft.com/en-us/msteams/forum).|

-

-

-#### App details

-#### Tabs

-##### Team tab

-##### Personal tabs

-1. Select **Delete** next to the imported bot in the bot list. Now there are no bots left to show.

-1. Choose **Save** to exit the dialog box. App Studio registers your bot with Microsoft and displays your new bot in the bot list.

-1. Update your hosted application with the App ID and password for your bot. For the sample app, use the same App ID and password for both bot and messaging extension.

-

-**To configure the app tab**

-**To test your bot**

-**To test your messaging extension**

-|

-#### App details

-#### Tabs

-##### Team tab

-##### Personal tabs

-1. Select **Delete** next to the imported bot in the bot list. Now there are no bots left to show.

-1. Choose **Save** to exit the dialog box. App Studio registers your bot with Microsoft and displays your new bot in the bot list.

- - **Command ID**: Enter random text

- - **Title**: Enter random title

- - **Description**: Enter random description

- - **Name**: Enter the parameter name

- - **Title**: Enter the card title

- - **Description**: Enter card description

-1. Use **Test and distribute** of App Studio to install your app in Teams.

-1. Update your hosted application with the App ID and password for your bot. For the sample app, use the same App ID and password for both bot and messaging extension.

-```

- - MICROSOFT_APP_ID is ID

- - MICROSOFT_APP_PASSWORD is password

-1. In the configuration dialog, select the tab you want to display in the channel. Then, select **Save**.

-**To test your messaging extension**

-|

- "info": {

- "_postman_id": "36d695ea-3ce2-4b2d-a1ac-b1721d2d46f1",

- "name": "Test-ChatRSC",

- "description": "Collection to test RSC.",

- "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"

- },

- "item": [

- {

- "name": "Teams client app installation flow",

- "item": [

- {

- "name": "Chat - Create App Context Token",

- "event": [

- {

- "listen": "test",

- "script": {

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "\r",

- " // Set the app_context access token\r",

- " const { access_token } = pm.response.json();\r",

- " pm.environment.set(\"appContextToken\", access_token);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "POST",

- "header": [

- {

- "key": "Content-Type",

- "type": "text",

- "value": "application/x-www-form-urlencoded",

- "disabled": true

- }

- ],

- "body": {

- "mode": "urlencoded",

- "urlencoded": [

- {

- "key": "grant_type",

- "value": "client_credentials",

- "type": "text"

- },

- {

- "key": "client_id",

- "value": "{{azureADAppId}}",

- "type": "text"

- },

- {

- "key": "client_secret",

- "value": "{{azureADAppSecret}}",

- "type": "text"

- },

- {

- "key": "scope",

- "value": "{{token_scope}}",

- "type": "text"

- }

- ]

- },

- "url": {

- "raw": "https://login.microsoftonline.com/{{tenantId}}/oauth2/v2.0/token",

- "protocol": "https",

- "host": [

- "login",

- "microsoftonline",

- "com"

- ],

- "path": [

- "{{tenantId}}",

- "oauth2",

- "v2.0",

- "token"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get Chat",

- "event": [

- {

- "listen": "test",

- "script": {

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200)\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "value": "Bearer {{appContextToken}}",

- "type": "text"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/chats/{{chatId}}",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "chats",

- "{{chatId}}"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get Chat Members",

- "event": [

- {

- "listen": "test",

- "script": {

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200)\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "value": "Bearer {{appContextToken}}",

- "type": "text"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/chats/{{chatId}}/members",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "chats",

- "{{chatId}}",

- "members"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get Chat Messages",

- "event": [

- {

- "listen": "test",

- "script": {

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200)\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "value": "Bearer {{appContextToken}}",

- "type": "text"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/chats/{{chatId}}/messages",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "chats",

- "{{chatId}}",

- "messages"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get Tabs",

- "event": [

- {

- "listen": "test",

- "script": {

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "\r",

- " const { internalId } = pm.response.json();\r",

- " pm.environment.set(\"generalChannelId\", internalId);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "value": "Bearer {{appContextToken}}",

- "type": "text"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/chats/{{chatId}}/tabs",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "chats",

- "{{chatId}}",

- "tabs"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get PermissionGrants",

- "event": [

- {

- "listen": "test",

- "script": {

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200)\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "value": "Bearer {{appContextToken}}",

- "type": "text"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/chats/{{chatId}}/permissionGrants",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "chats",

- "{{chatId}}",

- "permissionGrants"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get InstalledApps",

- "event": [

- {

- "listen": "test",

- "script": {

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "\r",

- " const { internalId } = pm.response.json();\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "value": "Bearer {{appContextToken}}",

- "type": "text"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/chats/{{chatId}}/installedApps?$expand=teamsApp",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "chats",

- "{{chatId}}",

- "installedApps"

- ],

- "query": [

- {

- "key": "$expand",

- "value": "teamsApp"

- }

- ]

- }

- },

- "response": []

- }

- ]

- }

- ]

-

-

- 4. Select **Get link to team**.

-3. Select the **Collections** tab.

-2. Follow the steps for either chat or team:

- "info": {

- "_postman_id": "57dc5f09-d719-4d48-a50d-6b09053cc7a7",

- "name": "Test-RSC",

- "description": "Collection to test RSC.",

- "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"

- },

- "item": [

- {

- "name": "Create App Context Token",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "1e0d2bb5-8d0d-47a1-a42e-fcd8d58bb8a3",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "\r",

- " // Set the app_context access token\r",

- " const { access_token } = pm.response.json();\r",

- " pm.environment.set(\"appContextToken\", access_token);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "POST",

- "header": [

- {

- "key": "Content-Type",

- "type": "text",

- "value": "application/x-www-form-urlencoded",

- "disabled": true

- }

- ],

- "body": {

- "mode": "urlencoded",

- "urlencoded": [

- {

- "key": "grant_type",

- "value": "client_credentials",

- "type": "text"

- },

- {

- "key": "client_id",

- "value": "{{azureADAppId}}",

- "type": "text"

- },

- {

- "key": "client_secret",

- "value": "{{azureADAppSecret}}",

- "type": "text"

- },

- {

- "key": "scope",

- "value": "{{token_scope}}",

- "type": "text"

- }

- ]

- },

- "url": {

- "raw": "https://login.microsoftonline.com/{{tenantId}}/oauth2/v2.0/token",

- "protocol": "https",

- "host": [

- "login",

- "microsoftonline",

- "com"

- ],

- "path": [

- "{{tenantId}}",

- "oauth2",

- "v2.0",

- "token"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get Team",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "92ae0b6b-859c-4210-b9ee-d7e76b1bb523",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "\r",

- " const { internalId } = pm.response.json();\r",

- " pm.environment.set(\"generalChannelId\", internalId);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "value": "{{appContextToken}}",

- "type": "text"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/teams/{{teamGroupId}}",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "teams",

- "{{teamGroupId}}"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Edit Team",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "f4fcb689-366e-4d28-9113-45adf84495a5",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(204);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "PATCH",

- "header": [

- {

- "key": "Authorization",

- "value": "{{appContextToken}}",

- "type": "text"

- },

- {

- "key": "Content-Type",

- "value": "application/json",

- "type": "text"

- }

- ],

- "body": {

- "mode": "raw",

- "raw": "{ \r\n \"funSettings\": {\r\n \"allowGiphy\": true,\r\n \"giphyContentRating\": \"strict\"\r\n },\r\n}"

- },

- "url": {

- "raw": "https://graph.microsoft.com/beta/teams/{{teamGroupId}}",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "teams",

- "{{teamGroupId}}"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get Channels",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "5acf1e2a-e4bb-4146-a4a7-d8677a3356be",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "value": "{{appContextToken}}",

- "type": "text"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/teams/{{teamGroupId}}/channels",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "teams",

- "{{teamGroupId}}",

- "channels"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get Specific Channel",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "da816d2b-97d6-4cd6-b243-2eb5257cce7c",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "type": "text",

- "value": "{{appContextToken}}"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/teams/{{teamGroupId}}/channels/{{generalChannelId}}",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "teams",

- "{{teamGroupId}}",

- "channels",

- "{{generalChannelId}}"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get Channel Messages",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "c511c14f-a193-4387-84d1-94d05f12ee67",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "type": "text",

- "value": "{{appContextToken}}"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/teams/{{teamGroupId}}/channels/{{generalChannelId}}/messages",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "teams",

- "{{teamGroupId}}",

- "channels",

- "{{generalChannelId}}",

- "messages"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Create Channel",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "6e58c6b2-7dd5-4746-b9cb-3b0b1d3b80e7",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "\r",

- "pm.test(\"Status Code 201 or 400\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.expect(pm.response.code).to.be.oneOf([201, 400]); //400 means that at least the permission check \r",

- "});\r",

- "\r",

- "// pm.test(\"Status Code 201\", () => {\r",

- "// // Need to validate the request succeeded. \r",

- "// pm.response.to.have.status(201);\r",

- "// });\r",

- "\r",

- "\r",

- "// pm.test(\"Successful POST request\", function () {\r",

- "// pm.expect(pm.response.code).to.be.oneOf([201, 400]); //400 means that at least the permission check passed\r",

- "// });"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "POST",

- "header": [

- {

- "key": "Authorization",

- "value": "{{appContextToken}}",

- "type": "text"

- },

- {

- "key": "Content-Type",

- "value": "application/json",

- "type": "text"

- }

- ],

- "body": {

- "mode": "raw",

- "raw": "{\r\n \"displayName\": \"ChannelCreatedThruRsc\",\r\n \"description\": \"This channel was created using RSC\",\r\n \"membershipType\": \"standard\"\r\n}",

- "options": {

- "raw": {

- "language": "json"

- }

- }

- },

- "url": {

- "raw": "https://graph.microsoft.com/beta/teams/{{teamGroupId}}/channels",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "teams",

- "{{teamGroupId}}",

- "channels"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get Tabs",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "aeafd689-f2b5-48b7-8f44-4d53f070b46e",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "value": "{{appContextToken}}",

- "type": "text"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/teams/{{teamGroupId}}/channels/{{generalChannelId}}/tabs",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "teams",

- "{{teamGroupId}}",

- "channels",

- "{{generalChannelId}}",

- "tabs"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Add Tab",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "0a7cae52-c103-403f-a016-d22c9fe1a477",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 201\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(201);\r",

- "\r",

- " const { id } = pm.response.json();\r",

- " pm.environment.set(\"createdTabId\", id);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "POST",

- "header": [

- {

- "key": "Authorization",

- "value": "{{appContextToken}}",

- "type": "text"

- },

- {

- "key": "Content-Type",

- "value": "application/json",

- "type": "text"

- }

- ],

- "body": {

- "mode": "raw",

- "raw": "{\n\t\"teamsApp@odata.bind\":\"https://graph.microsoft.com/beta/appCatalogs/teamsApps/com.microsoft.teamspace.tab.powerbi\",\n\t\"displayName\":\"TabCreatedThroughRsc\"\n}"

- },

- "url": {

- "raw": "https://graph.microsoft.com/beta/teams/{{teamGroupId}}/channels/{{generalChannelId}}/tabs",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "teams",

- "{{teamGroupId}}",

- "channels",

- "{{generalChannelId}}",

- "tabs"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Edit Tab",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "70276fd7-6d40-4305-9628-735170a6e749",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "PATCH",

- "header": [

- {

- "key": "Authorization",

- "value": "{{appContextToken}}",

- "type": "text"

- },

- {

- "key": "Content-Type",

- "value": "application/json",

- "type": "text"

- }

- ],

- "body": {

- "mode": "raw",

- "raw": "{\n\"displayName\":\"UpdatedTabName\"\n}"

- },

- "url": {

- "raw": "https://graph.microsoft.com/beta/teams/{{teamGroupId}}/channels/{{generalChannelId}}/tabs/{{createdTabId}}",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "teams",

- "{{teamGroupId}}",

- "channels",

- "{{generalChannelId}}",

- "tabs",

- "{{createdTabId}}"

- ]

- }

- },

- "response": []

- },

- {

- "name": "Get InstalledApps",

- "event": [

- {

- "listen": "test",

- "script": {

- "id": "14554c18-68b8-45ec-b1fb-33049b72ff95",

- "exec": [

- "console.log(\"responseHeaders: \" + JSON.stringify(pm.response.headers));\r",

- "console.log(\"responseBody: \" + JSON.stringify(pm.response.text()));\r",

- "\r",

- "pm.test(\"Status Code 200\", () => {\r",

- " // Need to validate the request succeeded. \r",

- " pm.response.to.have.status(200);\r",

- "});"

- ],

- "type": "text/javascript"

- }

- }

- ],

- "request": {

- "method": "GET",

- "header": [

- {

- "key": "Authorization",

- "value": "{{appContextToken}}",

- "type": "text"

- }

- ],

- "url": {

- "raw": "https://graph.microsoft.com/beta/teams/{{teamGroupId}}/installedApps?$expand=teamsApp",

- "protocol": "https",

- "host": [

- "graph",

- "microsoft",

- "com"

- ],

- "path": [

- "beta",

- "teams",

- "{{teamGroupId}}",

- "installedApps"

- ],

- "query": [

- {

- "key": "$expand",

- "value": "teamsApp"

- }

- ]

- }

- },

- "response": []

- }

- ],

- "protocolProfileBehavior": {}

-As a Teams admin, you can upload and pre-install the app package for your organization's tenant from https://admin.teams.microsoft.com/. See [Upload your custom apps in the Microsoft Teams admin center](/MicrosoftTeams/upload-custom-apps) for details.

-As a global admin, you can upload and pre-install the app package from https://admin.microsoft.com/. See [Test and deploy Microsoft 365 Apps by partners in the Integrated apps portal](/microsoft-365/admin/manage/test-and-deploy-microsoft-365-apps) for details.

-> * Update your TeamsJS SDK references

-1. Select the name of your personal tab application to open its app registration.

-1. Click on your app icon to launch your app in Outlook.

-1. Navigate to https://outlook.office.com and sign in using your dev tenant account.

-As a Teams admin, you can upload and pre-install the app package for your organization's tenant from https://admin.teams.microsoft.com/. See [Upload your custom apps in the Microsoft Teams admin center](/MicrosoftTeams/upload-custom-apps) for details.

-As a global admin, you can upload and pre-install the app package from https://admin.microsoft.com/. See [Test and deploy Microsoft 365 Apps by partners in the Integrated apps portal](/microsoft-365/admin/manage/test-and-deploy-microsoft-365-apps) for details.

-

-

-

-You can create the task module using an Adaptive Card or an embedded web view. To create a task module, you must perform the process called the initial invoke request. This document covers

-the initial invoke request, payload activity properties when a task module is invoked from 1:1 chat, group chat, channel (new post), channel (reply to thread), and command box.

-## Payload activity properties when a task module is invoked from 1:1 chat

-## Payload activity properties when a task module is invoked from a group chat

-## Payload activity properties when a task module is invoked from a channel (new post)

-## Payload activity properties when a task module is invoked from a channel (reply to thread)

-## Payload activity properties when a task module is invoked from a command box

-### Example

-When your bot is invoked from a message, the `value` object in the initial invoke request must contain the details of the message that your messaging extension is invoked from. The `reactions` and `mentions` arrays are optional, and they are not present if there are no reactions or mentions in the original message.

-When using an embedded web view, you must respond with a `task` object with the `value` object containing the URL to the web form that you want to load. The domains of any URL you want to load must be included in the `validDomains` array in your app's manifest. For more information on building your embedded web view, see the [task module documentation](~/task-modules-and-cards/what-are-task-modules.md).

-#### Example

-#### Example

-#### Example

-The following code section is an example of just-in time installation of app with Adaptive card:

-| Sample Name | Description | .NET | Node.js |

-|Teams messaging extension action| Describes how to define action commands, create task module, and respond to task module submit action. |[View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/csharp_dotnetcore/51.teams-messaging-extensions-action)|[View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/javascript_nodejs/51.teams-messaging-extensions-action) |

-> [!div class="nextstepaction"]

-For authentication or configuration, after the user completes the process, the original invoke is resent to your web service. The following table shows which types of responses are available based on the invoke location `commandContext` of the messaging extension:

-* Validate the information submitted by the user and resend the form with an error message if something is wrong.

-

-You can also respond to the `submitAction` by inserting a message with an Adaptive Card into the channel with a bot. The user can preview the message before submitting it. This is useful in scenarios where you gather information from the users before creating an Adaptive Card response, or when you update the card after someone interacts with it.

-**To configure the poll**

- > [!NOTE]

- > * The users can also select to `Edit` the message, which returns them to the original task module.

-### User attribution for bots messages

-| Sample Name | Description | .NET | Node.js |

-|Teams messaging extension action| Describes how to define action commands, create task module, and respond to task module submit action. |[View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/csharp_dotnetcore/51.teams-messaging-extensions-action)|[View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/javascript_nodejs/51.teams-messaging-extensions-action) |

-|Messaging extensions - auth and config | A Messaging Extension that has a configuration page, accepts search requests, and returns results after the user has signed in. |[View](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/52.teams-messaging-extensions-search-auth-config)|[View](https://github.com/microsoft/BotBuilder-Samples/blob/main/samples/javascript_nodejs/52.teams-messaging-extensions-search-auth-config)|

-

-**To enable SSO**

-

-

- ```

-

-To enable your messaging extension to interact with links, first you must add the `messageHandlers` array to your app manifest. The following example explains how to add link unfurling manually:

-## See also

-**To create a search command**

-1. If you already created your app package in **App Studio**, select from the list. If you have not created an app package, import an existing one.

-1. Select **Set up** in the window to include the messaging extension in your app experience. The following image displays the messaging extension set up page:

-1. Select **Add** in the **Command section** of the messaging extensions page to include the commands which decides the behaviour of messaging extension.

-| Sample Name | Description | .NET | Node.js |

-|Teams messaging extension action| Describes how to define action commands, create task module, and respond to task module submit action. |[View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/csharp_dotnetcore/51.teams-messaging-extensions-action)|[View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/javascript_nodejs/51.teams-messaging-extensions-action) |

- * **IMPORTANT**: The bot stores the token it receives from the identity provider and associates it with a specific user, but it is marked as "pending validation". The provisional token cannot be used yet: it must be further validated:

- 1. **Validate what's received from the identity provider.** The value of the `state` parameter must be confirmed against what was saved earlier.

-Because bots in a group or channel respond only when they are mentioned ("@_botname_") in a message, every message received by a bot in a group channel contains its own name, and you must ensure your message parsing handles that. In addition, bots can parse out other users mentioned and mention users as part of their messages.

-[Bot Framework samples](https://github.com/Microsoft/BotBuilder-Samples/blob/master/README.md).

-1. Create the bot using this link: https://dev.botframework.com/bots/new. **Be sure to add Microsoft Teams as a channel from the featured channels list after creating your bot.** Feel free to re-use any Microsoft App ID you generated if you've already created your app package/manifest.

-> If you do not wish to create your bot in Azure, you **must** use this link to create a new bot: https://dev.botframework.com/bots/new. If you click on the **Create a bot** in the Bot Framework portal instead, you will [create your bot in Microsoft Azure](#bots-and-microsoft-azure) instead.

-> * While it's possible to [create a new Bot Framework bot](https://dev.botframework.com/bots/new) without using Azure, you must use that URL (https://dev.botframework.com/bots/new), which is no longer exposed in the Bot Framework portal.

-[Bot Framework samples](https://github.com/Microsoft/BotBuilder-Samples/blob/master/README.md).

-> [!NOTE]

-The `conversationUpdate` event with the `membersAdded` object in the payload is sent when a user is added to a private scheduled meeting. The event details will be sent even when anonymous users join the meeting.

-The `conversationUpdate` event with the `membersRemoved` object in the payload is sent when a user is removed from a private scheduled meeting. The event details will be sent even when anonymous users join the meeting.

-[Bot Framework samples](https://github.com/Microsoft/BotBuilder-Samples/blob/master/README.md).

-### Action type message extensions

-#### Complete app manifest example

-### Search type message extensions

-#### Complete app manifest example

-### Test via uploading

-### Handle onQuery events

-### Handle onQuerySettingsUrl and onSettingsUpdate events

-Moodle is the worldΓÇÖs largest open source learning management system.

-This app helps educators create and organize their courses through valuable features, that include:

-* Robust quizzing tool

-* Graded discussions

-* Various assignment types for students to engage with content

-

-Moodle integrates with Microsoft Teams. Teams is the hub for real-time collaboration, teamwork, and productivity. With seamless integration with Office 365, hundreds of apps, chat, and live meeting capabilities of up to 300 participants. Teams gives faculty and students the ability to work together more efficiently no matter where they are.

-

-Microsoft 365 Moodle plugins complement Moodle by providing a comprehensive experience for faculty and students. With the Microsoft 365 Moodle plugins, site administrators can sync users with:

-* Office 365 and Moodle

-* Automate user matching

-* Sync courses to Microsoft Teams and file repositories

-* Connect OneNote assignments

-* Embed Office documents

-

-Microsoft Teams apps such as mConnect by Skooler and the Microsoft 365 Moodle Plugins, integrates Moodle into Teams.

-Faculty and students can take advantage of Moodle's unique features in real-time communication and collaboration.

-## mConnect app by Skooler

-The mConnect app by Skooler allows you to deliver virtual learnings through Teams with ease.

-### Why mConnect and Teams

-Watch the following video to understand how mConnect and Teams work better together:

-> [!VIDEO https://www.youtube-nocookie.com/embed/nM56R_woMdE]

-From inside mConnect, course participants access the full Moodle course experience inside the real-time collaboration and communication provided by Microsoft Teams.

-### Get started with mConnect and Teams

-Watch the following video to understand how to get started with mConnect and Teams:

-> [!VIDEO https://www.youtube-nocookie.com/embed/KOVpQ2s7iA8]

-For more information, see [mConnect by Skooler](https://skooler.com/mconnect/how-to/).

-## Microsoft 365 Moodle Plugins

-Moodle plugins for Teams makes it easy to schedule, deliver, and collaborate on course content. Install the plugins that seamlessly bring the Moodle learning management system into Teams. For more information, see [Install Moodle LMS](moodleInstructions.md).

-> This feature is not applicable to mobile clients, as the tabs viewed in the mobile clients don't have margins.

-> * The tab margin removal change applies to all tabs. There is no way to opt-in or opt-out of the change.

-

-**Required**

-**Optional**

-**Required**

-**Required**

-**Required**

-**Optional**

-**Optional**

-**Optional**

-**Optional**

-**Optional**

-**Optional**

-**Optional**

-

- "userRole": "anonymous"

- "userRole": "user"

- "userRole": "user"

-The contributors guide provides direction to create, publish, and update technical content on the **Microsoft Docs** platform.

-

-> &emsp;&#x2714; Do not include the file extension. <br>

-> Microsoft is not actively managing the source code. The complete source code is open source and you can explore, fork, and modify the source code to meet your specific requirements.

-**Open shifts view in Teams**

-Microsoft has published a [Microsoft Visual Studio template](https://marketplace.visualstudio.com/items?itemName=BotBuilder.VirtualAssistantTemplate) for building Virtual Assistants and skills. With the Visual Studio template, you can create a Virtual Assistant, powered by a text based experience with support for limited rich cards with actions. We have enhanced the Visual Studio base template to include Microsoft Teams platform capabilities and power great Teams app experiences. A few of the capabilities include support for rich Adaptive Cards, task modules, teams or group chats, and messaging extensions. For more information on extending Virtual Assistant to Microsoft Teams, see [Tutorial: Extend Your Virtual Assistant to Microsoft Teams](https://microsoft.github.io/botframework-solutions/clients-and-channels/tutorials/enable-teams/1-intro/).

-To add task module capabilities to a Virtual Assistant, two additional methods are included in the Virtual Assistant activity handler: `OnTeamsTaskModuleFetchAsync` and `OnTeamsTaskModuleSubmitAsync`. These methods listen to task module-related activities from Virtual Assistant, identify the skill associated with the request, and forward the request to the identified skill.

-A similar approach is followed for card action dispatching and task module responses. Task module fetch and submit action data is updated to include `skillId`.

-Book-a-room is a Microsoft Teams that allows users quickly to find and reserve a meeting room for 30, 60, or 90 minutes starting from the current time. The default time is 30 minutes. The Book-a-room bot scopes to personal or 1:1 conversations.

-### Limitation of card refresh

-`Book-a-room` bot card action, task module fetch and submit action payloads are modified to contain `skillId` as a parameter.

-## Limitations of Virtual Assistant

-* [Form completion feedback](~/bots/how-to/conversations/conversation-messages.md#form-completion-feedback)

-|Create Conversational tab| Microsoft Teams tab sample app for demonstrating create conversation tab. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/tab-conversations/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/tab-conversations/nodejs) |

-> * After you invoke the `registerOnRemoveHandler` event handler, you'll have 15 seconds to respond to the method. By default, Teams enables the **Remove** button after five seconds even if you don't call `setValidityState(true)`.

-

-[](~/assets/images/tab-images/open-stage-from-adaptive-card2.png#lightbox)

-> * `invoke` workflow is similar to the current `appLinking` workflow.

-Following is the deeplink syntax:

-

-

-* [Form completion feedback](~/bots/how-to/conversations/conversation-messages.md#form-completion-feedback)

-**To send the asset approval request**

-* [Form completion feedback](~/bots/how-to/conversations/conversation-messages.md#form-completion-feedback)

-**To send Adaptive Cards, refresh User Specific Views, and invoke requests to the bot**

-* [Form completion feedback](~/bots/how-to/conversations/conversation-messages.md#form-completion-feedback)

-| type | Data.Query | Yes | Specifies that it's a Data.Query object.|

-| value | String | No | Populates for the invoke request to the bot with the input that the user provided to the `ChoiceSet`. |

-| count | Number | No | Populates for the invoke request to the bot to specify the number of elements that must be returned. The bot ignores it, if the users want to send a different amount. |

- var packages = new[] {

- new { title = "A very extensive set of extension methods", value = "FluentAssertions" },

- new { title = "Fluent UI Library", value = "FluentUI" }};

- var searchResponseData = new

- {

- type = "application/vnd.microsoft.search.searchResponse",

- value = new

- {

- results = packages

- }

- };

- var jsonString = JsonConvert.SerializeObject(searchResponseData);

- JObject jsonData = JObject.Parse(jsonString);

- return new InvokeResponse()

- {

- Status = 200,

- Body = jsonData

- };

-

-#### [JSON](#tab/json)

-People Picker helps users to search and select users in Adaptive Card. You can add People Picker as input control to Adaptive Card, which works across chats, channels, task modules, and tabs. People Picker supports the following features:

-* Selects single or multiple users.

-* Reassigns to single or multiple users.

-## Popular scenarios

-|Incident management| To track incidents and notify, assign, and reassign to the intended user for immediate action.|

-User A (Robert) receives a ticket for a task in a channel and realizes incorrect assignee. User A reassigns the task that sends the information back to the bot.

-**To reassign any task**

-1. Remove the incorrect user's name.

-1. Select intended users as per the image scenario, user B (Mona), and user C (Robin) for the task.

-1. Select **Assign**. After assigning, the information is sent to the bot.

- The bot updates Adaptive Card and notifies the intended users.

-

-The following image shows the reassignment scenario:

-User A (Robert) receives a ticket for a task in a channel and realizes incorrect assignee. User A reassigns the task that sends the information back to the bot.

-**To reassign any task**

-1. Select **Assign**. After assigning, the information is sent to the bot.

- The bot updates Adaptive Card and notifies the intended users.

-The following image shows the reassignment scenario:

-People Picker is implemented as an extension of the [Input.ChoiceSet](https://adaptivecards.io/explorer/Input.ChoiceSet.html) control. The input control includes the following selections:

-|**dataset** |String |Yes |The type of data that must be fetched dynamically.|

-The following table provides predefined values as **dataset** for people picker:

-|**graph.microsoft.com/users?scope=currentContext** |Search within the members of the current conversation, such as chat or channel in which the particular card is sent.|

-```json

- "type": "AdaptiveCard",

- "body": [

- {

- "type": "TextBlock",

- "size": "Medium",

- "weight": "Bolder",

- "text": "People Picker with Org search enabled"

- },

- {

- "type": "Input.ChoiceSet",

- "choices": [],

- "choices.data": {

- "type": "Data.Query",

- "dataset": "graph.microsoft.com/users"

- },

- "id": "people-picker",

- "isMultiSelect": true

- }

- ],

- "actions": [

- {

- "type": "Action.Submit",

- "title": "Submit"

- }

- ],

- "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",

- "version": "1.2"

-With the `Azure AD ID`, People Picker preselects the corresponding user.

-* For single user in the control, specify the `Azure AD ID` of the user as the `value`.

- "type": "AdaptiveCard",

- "body": [

- {

- "type": "TextBlock",

- "size": "Medium",

- "weight": "Bolder",

- "text": "People Picker with Org search enabled"

- },

- {

- "type": "Input.ChoiceSet",

- "choices": [],

- "choices.data": {

- "type": "Data.Query",

- "dataset": "graph.microsoft.com/users"

- },

- "id": "people-picker",

- "value": "<Azure AD ID 1>"

- }

- ],

- "actions": [

- {

- "type": "Action.Submit",

- "title": "Submit"

- }

- ],

- "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",

- "version": "1.2"

- "type": "AdaptiveCard",

- "body": [

- {

- "type": "TextBlock",

- "size": "Medium",

- "weight": "Bolder",

- "text": "People Picker with Org search enabled"

- },

- {

- "type": "Input.ChoiceSet",

- "choices": [],

- "choices.data": {

- "type": "Data.Query",

- "dataset": "graph.microsoft.com/users"

- },

- "id": "people-picker",

- "isMultiSelect": true,

- "value": "<Azure AD ID 1>,<Azure AD ID 2>,<Azure AD ID 3>"

- }

- ],

- "actions": [

- {

- "type": "Action.Submit",

- "title": "Submit"

- }

- ],

- "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",

- "version": "1.2"

-

-> Static `choices` are used with dynamic datasets.

-The choice consists of `title` and `value`. When used along with People Picker, these choices are translated to user profiles that have the `title` as the name and the `value` as the identifier. These custom profiles are also part of the search results when the search query matches the given `title`.

-The following example describes static choices:

- "type": "AdaptiveCard",

- "body": [

- {

- "type": "TextBlock",

- "size": "Medium",

- "weight": "Bolder",

- "text": "People Picker with Org search enabled"

- },

- {

- "type": "Input.ChoiceSet",

- "choices": [

- {

- "title": "Custom Profile 1",

- "value": "Profile1"

- },

- {

- "title": "Custom Profile 2",

- "value": "Profile2"

- }

- ],

- "choices.data": {

- "type": "Data.Query",

- "dataset": "graph.microsoft.com/users"

- },

- "id": "people-picker",

- "isMultiSelect": true

- }

- ],

- "actions": [

- {

- "type": "Action.Submit",

- "title": "Submit"

- }

- ],

- "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",

- "version": "1.2"

-| Sample Name | Description | C# | Node.js |

-|People picker control in Adaptive Cards| This sample demonstrates how to use the people picker control in Adaptive Cards.|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-people-picker-adaptive-card/csharp)|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-people-picker-adaptive-card/nodejs) |

-|Task module sample tabs and bots-V3 | Samples for creating task modules. |[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/app-task-module/csharp)|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/app-task-module/nodejs)|

-* [Source code](https://github.com/OfficeDev/TeamsFx/tree/dev/packages/cli)

-* [.NET SDK installation guide](https://github.com/OfficeDev/TeamsFx/blob/dev/docs/vscode-extension/envchecker-help.md#how-to-install-net-sdk)

-

-* [Source code](https://github.com/OfficeDev/TeamsFx/tree/main/packages/sdk)

-* [Package (NPM)](https://www.npmjs.com/package/@microsoft/teamsfx)

-* [API reference documentation](https://aka.ms/teamsfx-sdk-help)

-[Microsoft TeamsFx sample gallery](https://github.com/OfficeDev/TeamsFx-Samples)

- - You can add a customized parameter as follows:

- - Add a placeholder in manifest.remote.template.json with pattern: `{{config.manifest.xx}}`

- - Add a config value in config.{env}.json

-1. Select **Update to Teams platform** at the top left corner of `manifest.{env}.json`

-## Select target environment

-## Project folder structure

- - `config.<envName>.json`: per-environment configuration file.

- - `azure.parameters.<envName>.json`: per-environment parameters file for Azure bicep provision.

- - `projectSettings.json`: global project settings , which apply to all environments.

- - `localSettings.json`: local debug configuration file.

- - `state.<envName>.json`: per-environment provision output file.

- - `<env>.userdata`: per-environment sensitive user data for the provision output.

- - `appPackage`: app manifest template files.

- - `azure`: Bicep template files.

-## Customize the provision

-## Join Microsoft 365 developer program

-5. Select **Save**.

- You can also open the command palette and enter **Teams: Add Capabilities**:

-

-Apart from the capabilities your Teams app already have, you can choose to add different capabilities to your Teams app. The following table provides the different Teams app capabilities:

- - The ID of your bot.

- - The scopes of your bot.

- - The commands that hello world bot application can respond to.

- - The configurable and static tabs.

- - The scopes of the tabs.

-

- * Microsoft 365 account with valid subscription

- * Azure with valid subscription

-Teams Toolkit enables you to use an infrastructure as code approach to define what Azure resources you want to provision, and how you want to configure. The tool uses ARM template to define Azure resources. The ARM template is a set of bicep files that defines the infrastructure and configuration for your project. You can customize Azure resources by modifying the ARM template. For more information, see [bicep document](/azure/azure-resource-manager/bicep.md).

-### Scenerio

-**To add other Azure resource or storage to the application**

-## Publish to your organization

-* [Collaborate with other developers on Teams project](TeamsFx-collaboration.md)

-If you would like to learn more about how your Azure app registration will be provisioned, please _see_ our [single sign-on (SSO) support for tabs](../tabs/how-to/authentication/auth-aad-sso.md) documentation.

-1. If you are using a tunneling service like [ngrok](https://ngrok.com/), run it and make sure the URL matches with what you entered in the project creation wizard. If it doesn't, you will need to update your _API URI_ and _redirect URL_ in the app registration that was created in Azure.