-* [Calls and meetings bots](~/bots/calls-and-meetings/calls-meetings-bots-overview.md)

-* [Bot conversations](~/bots/how-to/conversations/conversation-basics.md)

-* [Bot command menus](~/bots/how-to/create-a-bot-commands-menu.md)

-* [Authentication flow for bots in Microsoft Teams](~/bots/how-to/authentication/auth-flow-bot.md)

-* [Use task modules from bots](~/task-modules-and-cards/task-modules/task-modules-bots.md)

-* [Publish your bot to Azure](/azure/bot-service/bot-builder-deploy-az-cli)

-description: In this module, learn how your Microsoft Teams apps can interact with users using voice and video using Microsoft Graph APIs for calls and online meetings and learn about real-time media streams

-The Teams app manifest with two additional settings `supportsCalling` and `supportsVideo`, Graph permissions for your bot's Microsoft App ID, and tenant admin consent enable you to register the bot. In registering a calls and meetings bot for Teams, the Webhook URL is mentioned, which is the webhook endpoint for all incoming calls to your bot. An application-hosted media bot requires the Microsoft.Graph.Communications.Calls.Media .NET library to access the audio and video media streams, and the bot must be deployed on a Windows Server machine or Windows Server guest Operating System (OS) in Azure. Bots on Teams supports only a specific set of media formats for audio and video content.

-The following core concepts, terminology, and conventions guide you through the use of calls and online meetings bots:

-* 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.

-* 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.

-From a Teams user's perspective, there are two kinds of online meetings, ad hoc and scheduled. From a bot's perspective, both online meetings are the same. To a bot, an online meeting is a multiparty call between a set of participants and includes meeting coordinates. Meeting coordinates are the metadata for the meeting including `botId`, `chatId` associated with the meeting, `joinUrl`, `startTime` or `endTime`, and so on.

-When a bot is participating in a call or online meeting, it must deal with audio and video streams. When users talk on a call, show themselves on a webcam, or present their screens in a meeting, to a bot it is shown as audio and video streams. If a bot wants to say something as simple as, **press 0 to reach the operator** in an interactive voice response (IVR) scenario, it requires playing a .WAV file. Collectively, this is referred to as media or real-time media.

-Real-time media refers to scenarios where media must be processed in real-time, as opposed to playback of previously recorded audio or video. Dealing with media streams, particularly real-time media streams, is extremely complex. Microsoft has created the Real-time Media Platform to handle these scenarios and to offload as much of the traditional heavy lifting of real-time media processing as possible. When the bot answers an incoming call or joins a new or existing call, it needs to tell the Real-time Media Platform how media is handled. If you are building an IVR application, you can offload the expensive audio processing to Microsoft. Alternately, if your bot requires direct access to media streams, that scenario is also supported. There are two types of media processing:

-* **Service-hosted media**: Bots focus on managing application workflow, such as routing calls and offload audio processing to the Microsoft Real-time Media Platform. With service-hosted media, you have several options to implement and host your bot. A service-hosted media bot can be implemented as a stateless service as it does not process media locally. Service-hosted media bots can use the following APIs:

-* [Graph API reference](/graph/api/resources/communications-api-overview?view=graph-rest-beta&preserve-view=true)

-* [Sample apps](https://github.com/microsoftgraph/microsoft-graph-comms-samples)

-* [Registering a bot that supports calls and online meetings](./registering-calling-bot.md)

-* [Graph permissions for calls and online meetings bots](./registering-calling-bot.md#add-graph-permissions)

-* [How to develop calling and online meeting bots on your computer](./debugging-local-testing-calling-meeting-bots.md)

-* [Technical information on handling incoming call notifications](./call-notifications.md)

-* [Teams recording policy](/MicrosoftTeams/teams-recording-policy)

-* [Work with communications API in Microsoft Graph](/graph/api/resources/communications-api-overview?view=graph-rest-beta&preserve-view=true)

-* [Enable an event as online meeting in Outlook calendar](/graph/outlook-calendar-online-meetings?tabs=http)

-> [Register a calling bot](~/bots/calls-and-meetings/registering-calling-bot.md)

-[Supported media formats for bots](~/resources/media-formats.md)

-* [Incoming call notifications](~/bots/calls-and-meetings/call-notifications.md)

-* [Working with the cloud communications API in Microsoft Graph](/graph/api/resources/communications-api-overview)

-> [Supported media formats](~/resources/media-formats.md)

-The next section provides samples that illustrate different local media scenarios.

-## Samples and additional resources

-* [Sample applications](https://github.com/microsoftgraph/microsoft-graph-comms-samples/tree/master/Samples/V1.0Samples/LocalMediaSamples)

-* [Graph calling SDK documentation](https://microsoftgraph.github.io/microsoft-graph-comms-samples/docs/)

-[Protected APIs in Microsoft Teams](/graph/teams-protected-apis)

-> [Subscribe to conversation events](~/bots/how-to/conversations/subscribe-to-conversation-events.md)

-* [Get Teams context](~/bots/how-to/get-teams-context.md)

-* [Bot conversations](/microsoftteams/platform/bots/how-to/conversations/conversation-basics)

-* [Test resource-specific consent](/microsoftteams/platform/graph-api/rsc/test-resource-specific-consent)

-> [Bot command menus](~/bots/how-to/create-a-bot-commands-menu.md)

-* [Send proactive messages](~/bots/how-to/conversations/send-proactive-messages.md)

-* [Send tenant ID and conversation ID to the request headers of the bot](~/bots/how-to/conversations/request-headers-of-the-bot.md)

-The current outgoing requests to the bot don't contain in the header or URL any information that helps bots route the traffic without unpacking the entire payload. The activities are sent to the bot through a URL similar to https://<your_domain>/api/messages. Requests are received to show the conversation ID and tenant ID in the headers.

-* [**Teams proactive messaging code samples**](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-proactive-messaging/csharp)

-* [Channel and group chat conversations with a bot](~/bots/how-to/conversations/channel-and-group-conversations.md)

-* [Respond to the task module submit action](~/messaging-extensions/how-to/action-commands/respond-to-task-module-submit.md)

-* [Build your first bot app using JavaScript](../../../sbs-gs-bot.yml)

-* [Build notification bot with JavaScript to send a proactive message](../../../sbs-gs-notificationbot.yml)

-> When you upgrade an application, and then add or remove a bot, the action also triggers the `installationUpdate` event. The **action** field is set to *add-upgrade* if you add a bot or *remove-upgrade* if you remove a bot.

-> [Channel and group conversations](~/bots/how-to/conversations/channel-and-group-conversations.md)

-> [Update and delete bot messages](~/bots/how-to/update-and-delete-bot-messages.md)

-> [Send and receive files through the bot](~/bots/how-to/bots-filesv4.md)

-> [Calls and meetings bots](~/bots/calls-and-meetings/calls-meetings-bots-overview.md)

-[Manage a long-running operation](/azure/bot-service/bot-builder-howto-long-operations-guidance?view=azure-bot-service-4.0&preserve-view=true)

-# Update and delete messages sent from bot

-> [Get Teams context](~/bots/how-to/get-teams-context.md)

-* [Create a bot for Teams](../resources/bot-v3/bots-create.md)

-* [Register calls and meetings bot for Microsoft Teams](~/bots/calls-and-meetings/registering-calling-bot.md)

-* [Add authentication to your Teams bot](~/bots/how-to/authentication/add-authentication.md)

-* [Bot activity handlers](~/bots/bot-basics.md)

-* [Conversation events in your Teams bot](~/bots/how-to/conversations/subscribe-to-conversation-events.md)

-* [Build notification bot with JavaScript](../sbs-gs-notificationbot.yml)

-At its heart, Teams is a collaboration platform. It's also a social platform, is natively cross-platform, sits at the heart of Office 365, and offers a personal canvas for you to create apps.

-* **Create and Build app project**: With Teams, you can choose the build environment that best suits your app requirement. Use Teams Toolkit or other SDKs, such as C#, Blazor, Node.js, and more to get started.

- :::image type="content" source="../assets/images/overview/teams-solution.png" alt-text="Conceptual representation of the Teams solution.":::

-| Teams owned apps as in internally developed apps | ✔️ App is enabled if it has GCC | ✔️ App is enabled if it has GCC-High | ✔️ App is enabled if it has DOD |

-| Microsoft apps | ✔️ Microsoft apps compliant with GCC | ✔️ Microsoft apps compliant with GCC-High | ✔️ Microsoft apps compliant with DOD |

-| Bots | ✔️ | ❌ | ❌ |

-| Sideloading apps | ✔️ | ❌ | ❌ |

-| Custom or Lob bots | ✔️ | ❌ | ❌ |

-| Custom messaging extensions | ❌ | ❌ | ❌ |

-| Custom connectors | ❌ | ❌ | ❌ |

-**Compliance UI**: By enabling third-party communications, customers accept that such communication is being processed through the third party and not Microsoft. The customer is solely responsible for mitigating risks associated with connecting with third party bots in their services. Microsoft doesn't endorse and makes no warranties, express, or implied concerning the security of third parties the customer allows to connect with their service. Enabling bots will extend your system boundary beyond this tenant based on the bot you choose to leverage. It is your responsibility to ensure that this meets your compliance requirements including FedRAMP, DFARS, ITAR, etc. It is your responsibility to evaluate the risk and compliance of any endpoint and URL that you connect to.

-## Manage license for third party apps in Teams

-Teams allows independent software vendors (ISVs) admins or users to manage SaaS licenses for third party apps purchased from Teams storefront. ISV admins or users can easily assign, unassign, use, and track SaaS licenses.

-To enable license management for an app in Teams, follow the steps:

-1. [Create an offer in Partner Center](#create-an-offer-in-partner-center)

-1. [Update your Teams app](#update-your-teams-app)

-1. [Post purchase](#post-purchase)

-1. [Integrate with Graph Usage Right API](#integrate-with-graph-usage-right-api)

-### Create an offer in Partner Center

-1. Sign in to [Partner Center](https://partner.microsoft.com/) and select **Partner Center**.

- :::image type="content" source="~/assets/images/first-party-license-mgt/partner-center-home-page.png" alt-text="The screenshots shows how to login to the Partner Center account.":::

-1. In the **Home** page, select **Marketplace offers** tab to define commercial marketplace offers.

- :::image type="content" source="~/assets/images/first-party-license-mgt/home-page.png" alt-text="The screenshots shows the home page and Marketplace offer tab in the Partner Center.":::

-1. Select **Overview** from the left pane.

-1. Select **New Offer** > **Software as a Service**.

- :::image type="content" source="~/assets/images/first-party-license-mgt/commercial-marketplace.png" alt-text="The screenshots shows the marketplace offer page where you can select new offer.":::

-1. Enter **Offer ID** and **Offer alias** and select **Create**.

- > [!NOTE]

- > If you're creating an offer for testing purpose, add the text **-ISVPILOT** to the end of your offer alias. This indicates the certification team that the offer is for testing purposes. Microsoft delete offers with **-ISVPILOT** periodically. So, don't use this tag for reasons other than testing the license management capability.

- :::image type="content" source="~/assets/images/first-party-license-mgt/saas.png" alt-text="The screenshots shows how to enter Offer ID and Offer alias in the Partner Center.":::

-1. In Offer setup page, under setup details, select the checkbox **Yes, I would like Microsoft to manage customer licenses on my behalf**.

- :::image type="content" source="~/assets/images/first-party-license-mgt/saas-isvpilot.png" alt-text="The screenshots shows the offer setup page to setup license to manage for your app within Teams.":::

- > [!NOTE]

- >

- > * This is a one-time setting and you can't change it once your offer is published. This allows the customer to manage licenses for your app within Teams.

- > * The App manifest supports only one offer for an app. Choose an appropriate license management solution for all the plans available in your offer and you can't change this option after the offer is pushed to live.

-1. Select **Save draft**.

-1. Select **Plan overview** from the left pane, and then select **Create new plan**.

- > [!NOTE]

- > You need to add at least one plan.

- :::image type="content" source="~/assets/images/first-party-license-mgt/plan-overview.png" alt-text="The screenshots shows plan overview to create a new plan for your apps in the Partner Center.":::

-1. Enter Plan ID and Plan name, and then select **Create**.

-1. Enter the **Plan name** and **Plan description**.

- > [!NOTE]

- > The plan information displays on Teams marketplace and [Appsource](https://appsource.microsoft.com/) under offer listing (plans section).

- :::image type="content" source="~/assets/images/first-party-license-mgt/plan-listing.png" alt-text="The screenshots shows plan page to add plan name and plan description for your app.":::

-1. Select **Save draft**.

-1. Select **Pricing and availability** from the left pane.

-1. Add pricing and availability details.

- :::image type="content" source="~/assets/images/first-party-license-mgt/pricing-availability.png" alt-text="The screenshots shows pricing and availability page to add SaaS offer for your app.":::

-1. Select **Save draft**.

-1. Select **Plan overview** at the top of the page to go to the listing page that shows all the plans you've created for this offer.

- :::image type="content" source="~/assets/images/first-party-license-mgt/list-of-plans-created.png" alt-text="The screenshots shows plan listing page with service ID, pricing model, availability, status and action.":::

-1. Copy the service ID of the plan you created to integrate with Microsoft Graph Usage Rights API.

-### Update your Teams app

-Update your Teams app to map to the paid functionality and [Map your Teams app](https://aka.ms/TMTG) to your offer and publish.

-### Post purchase

-1. After activation, customer is redirected from landing page to Teams License Management.

-1. Upon successful completion of subscription purchase, the customer is redirected to the app landing page for subscription activation. This is the existing experience for user purchasing [monetized apps in Teams](https://aka.ms/TMTG).

-1. After the customer activates the subscription purchase on landing page, customer is redirected to subscriptions page in Teams via a [redirect URL](https://teams.microsoft.com/_#/subscriptionManagement) link or button that the customer selects on the publisher landing page.

-### Integrate with Graph Usage Right API

-Integrate with Graph Usage Right API to manage user permissions at the time of app launch by a customer who has a purchase license. You're required to determine the userΓÇÖs permissions for the app with a Graph call to the Usage Rights API.

-You can call Graph APIs to determine if the currently logged in user with a valid subscription of the plan has access to your app. To call Graph UsageRight API to check user permissions, follow the steps:

-1. Get user OBO token: [Get access on behalf of a user - Microsoft Graph | Microsoft Docs](/graph/auth-v2-user).

-1. Call Graph to get userΓÇÖs object ID: [Use the Microsoft Graph API - Microsoft Graph | Microsoft Docs](/graph/use-the-api).

-1. Call UsageRights API to determine the user has License to the plan [List user usageRights - Microsoft Graph beta | Microsoft Docs](/graph/api/user-list-usagerights?view=graph-rest-beta&tabs=http&preserve-view=true).

- > [!NOTE]

- > You need to have minimum `User.Read` permissions to call UsageRights.

- > The UsageRights API is currently in beta version. After the version is updated to V1, ISV users should upgrade from beta to V1 version.

-### Check license usage in Partner Center analytics

-1. Sign in to [Partner Center](https://partner.microsoft.com/).

-1. In the left pane, go to **Commercial Marketplace > Analyze > Licensing**.

-1. Select **Plan and Tenant** in the reporting widget to see the month wise usage.

-Select **No, I would prefer to manage customer licenses myself** in such cases.

-When someone finishes buying a subscription plan for your app and wants to stay in the Teams, without directing them to your landing page, select **Yes, I would like Microsoft to manage customer licenses on my behalf**.

-For more information, see [manage license for third party apps in Teams](#manage-license-for-third-party-apps-in-teams).

-**Manage license for third party apps in Teams**

-Using Microsoft license management, independent software vendors (ISVs) can manage SaaS license purchased in Teams to easily assign, unassign, use, and track SaaS licenses. For more information, see [Manage license for third party apps in Teams](include-saas-offer.md#manage-license-for-third-party-apps-in-teams).

-description: Learn how to use Teams JavaScript client SDK to leverage location capabilities using Code snippets and samples.

-You can integrate the location capabilities of native device with your Teams app.

-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/location.locationprops) and [showLocation](/javascript/api/@microsoft/teams-js/location.locationprops?) to integrate the capabilities within your app.

-## Advantages of integrating location capabilities

-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.

-Following examples show how the integration of location capabilities is used in different scenarios:

-* In a factory, the supervisor can track the attendance of workers by asking them to take a selfie in the vicinity of the factory and share it through the specified app. The location data also gets captured and sent along with the image.

-* The location capabilities enable the maintenance staff of a service provider to share authentic health data of cellular towers with the management. The management can compare any mismatch between captured location information and the data submitted by maintenance staff.

-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.

-It's important to familiarize yourself with the [API response errors](#error-handling) to handle the errors in your Teams app.

-> [!NOTE]

-> Currently, Microsoft Teams supports for location capabilities is available for mobile clients only.

-Update your Teams app [manifest.json](../../resources/schem#devicepermissions) file by adding the `devicePermissions` property and specifying `geolocation`. It allows your app to ask for requisite permissions from users before they start using the location capabilities. The update for app manifest is as follows:

-You must use the following set of APIs to enable your device's location capabilities:

-| API | Description |

-| | |

-|[getLocation](/javascript/api/@microsoft/teams-js/location.locationprops) | Gives userΓÇÖs current device location or opens native location picker and returns the location chosen by the user. |

-|[showLocation](/javascript/api/@microsoft/teams-js/location.locationprops?) | Shows location on map. |

-> The `getLocation()` API comes along with following [input configurations](/javascript/api/@microsoft/teams-js/microsoftteams.location.locationprops), `allowChooseLocation` and `showMap`. <br/> If the value of `allowChooseLocation` is *true*, then the users can choose any location of their choice.<br/> If the value is *false*, then the users cannot change their current location.<br/> If the value of `showMap` is *false*, the current location is fetched without displaying the map. `showMap` is ignored if `allowChooseLocation` is set to *true*.

-The following image depicts web app experience of location capabilities:

-

-**Calling `getLocation` API to retrieve the location:**

-**Calling `showLocation` API to display the location:**

-**Calling `getLocation` API to retrieve the location:**

-**Calling `showLocation` API to display the location:**

-* [Integrate People Picker in Teams](people-picker-capability.md)

-> * To integrate media capabilities within your Microsoft Teams web client, desktop, and mobile, see [Integrate media capabilities](media-capabilities.md).

-You must request the device permissions to access native device capabilities. The device permissions work similarly for all app constructs, such as tabs, task modules, or messaging extensions. The user must go to the permissions page in Teams settings to manage device permissions. You can build richer experiences on the Teams platform with the help of device capabilities, such as:

- <!--  -->

- :::image type="content" source="~/assets/images/tabs/MobilePermissions.png" alt-text="Mobile Permissions.":::

- <!--  -->

-* Notifications prompt the user when you call `requestPermission()`:

- # [TeamsJS v2](#tab/teamsjs-v2)

- ```JavaScript

- ```

- # [TeamsJS v1](#tab/teamsjs-v1)

- ```JavaScript

- ```

- ***

-# [Mobile](#tab/mobile)

- <!--  -->

- :::image type="content" source="~/assets/images/tabs/MobileLocationPermission.png" alt-text="Mobile location permission.":::

-# [Desktop](#tab/desktop)

-| Vorbis | http://www.vorbis.com/ |

-| PCM_U8, PCM_S16LE, PCM_S32LE, PCM_F32LE, PCM_S16BE, PCM_S24BE, PCM_MULAW | https://wiki.multimedia.cx/?title=PCM |

-| Ogg | http://www.vorbis.com/ |

-| Matroska | https://matroska.org/ |

-| WAV | https://en.wikipedia.org/wiki/WAV |

-| AAC | https://en.wikipedia.org/wiki/Advanced_Audio_Coding |

-| H264 | https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC |

-| MP3 | https://en.wikipedia.org/wiki/MP3 |

-| Opus | http://opus-codec.org/ |

-| MP4 | https://en.wikipedia.org/wiki/MPEG-4 |

-> [Changes to Teams bot APIs for fetching Team or chat members](~/resources/team-chat-member-api-changes.md)

-## Troubleshooting tabs

-### Accessing the DevTools

-Be sure to call `microsoftTeams.settings.setValidityState(true)` once the user has input or selected all required data on your settings page to enable the save button.

-For more information about authentication, see [Authenticate a user](~/concepts/authentication/authentication.md).

-## Troubleshooting bots

-Apps must be enabled by the Office 365 tenant admin for them to be loaded by end users. In some cases, the Office 365 tenant might have multiple SKUs associated with it, and for bots to work in any, they must be enabled in all SKUs. For more information, see [Prepare your Office 365 tenant](~/concepts/build-and-test/prepare-your-o365-tenant.md).

-Bots must first be uploaded in a team before it's accessible within any channel of that team. For more information on this process, see [Uploading your app in a team](~/concepts/deploy-and-publish/apps-upload.md).

-| Bot card button | 1. Bot card buttons, depending on the type of button, can invoke task modules in two ways, a deep link URL or by sending a `task/fetch` message. <br/><br/> 2. If the button's action `type` is `task/fetch` that is `Action.Submit` button type for Adaptive Cards, a `task/fetch invoke` event that is an HTTP POST is sent to the bot. The bot responds to the POST with HTTP 200 and the response body containing a wrapper around the [TaskInfo object](#the-taskinfo-object). For more information, see [invoking a task module using `task/fetch`](~/task-modules-and-cards/task-modules/task-modules-bots.md#invoke-a-task-module-using-taskfetch). Teams displays the task module. <br/><br/> 3. After the user has performed the actions, call the Teams SDK function `tasks.submitTask()` with a `result` object as a parameter. The bot receives a `task/submit invoke` message that contains the `result` object. <br/><br/> 4. You have three different ways to respond to the `task/submit` message, by doing nothing that is the task completed successfully, by displaying a message to the user in a pop-up window, or by invoking another task module window. For more information, see [detailed discussion on `task/submit`](~/task-modules-and-cards/task-modules/task-modules-bots.md#the-flexibility-of-tasksubmit). | <ul><li> Like buttons on Bot Framework cards, buttons on Adaptive Cards support two ways of invoking task modules, deep link URLs with `Action.openUrl` buttons, and `task/fetch` using `Action.Submit` buttons. </li></ul> <br/><br/> <ul><li> Task modules with Adaptive Cards work similarly to the HTML or JavaScript case. The major difference is that since there's no JavaScript when you're using Adaptive Cards, there's no way to call `tasks.submitTask()`. Instead, Teams takes the `data` object from `Action.Submit` and returns it as the payload of the `task/submit` event. For more information, see [flexibility of `task/submit`](~/task-modules-and-cards/task-modules/task-modules-bots.md#the-flexibility-of-tasksubmit). </li></ul> |

-* A new invoke message `task/fetch`: Using the `invoke` [card action](~/task-modules-and-cards/cards/cards-actions.md#action-type-invoke) for Bot Framework cards, or the `Action.Submit` [card action](~/task-modules-and-cards/cards/cards-actions.md#adaptive-cards-actions) for Adaptive cards, with `task/fetch`, task module either a URL or an Adaptive Card, is fetched dynamically from your bot.

-## Invoke a task module using task/fetch

-The following steps provide the invoke task module using task/fetch:

-1. The bot creates a response object and returns it in the body of the POST response with an HTTP 200 response code. For more information on schema for responses, see [the discussion on task/submit](#the-flexibility-of-tasksubmit). The following code provides an example of body of the HTTP response that contains a [TaskInfo object](~/task-modules-and-cards/task-modules/invoking-task-modules.md#the-taskinfo-object) embedded in a wrapper object:

-* HTML or JavaScript that is `TaskInfo.url`: Once you've validated what the user has entered, you call the `microsoftTeams.tasks.submitTask()` SDK function referred to hereafter as `submitTask()` for readability purposes. You can call `submitTask()` without any parameters if you want Teams to close the task module, but you must pass an object or a string to your `submitHandler`. Pass it as the first parameter, `result`. Teams invokes `submitHandler`, `err` is `null`, and `result` is the object or string you passed to `submitTask()`. If you call `submitTask()` with a `result` parameter, you must pass an `appId` or an array of `appId` strings. This allows Teams to validate that the app sending the result is the same one, which invoked the task module. Your bot receives a `task/submit` message including `result`. For more information, see [payload of `task/fetch` and `task/submit` messages](#payload-of-taskfetch-and-tasksubmit-messages).

-The next section provides details on the flexibility of `task/submit`.

-## The flexibility of task/submit

-## Payload of task/fetch and task/submit messages

-## Example of task/fetch and task/submit invoke messages in Node.js and C#

-description: Create Incoming Webhook to Teams app and post external requests to Teams. Remove Incoming Webhook. Sample code(C#,Node.js) to send card using Incoming Webhook.

-An Incoming Webhook lets external applications to share content in Microsoft Teams channels. The webhooks are used as tools to track and notify. The webhooks provide a unique URL, to send a JSON payload with a message in card format. Cards are user interface containers that include content and actions related to a single topic. You can use cards in the following capabilities:

-> You can choose to build notification bot Teams app other than incoming webhooks. They perform similarly but notification bot has more functionalities. For more information, see [Build notification bot with JavaScript](../../sbs-gs-notificationbot.yml) or [incoming webhook notification sample](https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/incoming-webhook-notification). To get started, download [Teams Toolkit](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension) now and explore. For more information, see [Teams Toolkit documents](../../toolkit/teams-toolkit-fundamentals.md).

-See the following video to learn how to create an Incoming Webhooks:

-## Key features of an Incoming Webhook

-|Markdown support|All text fields in actionable messaging cards support basic Markdown. Do not use HTML markup in your cards. HTML is ignored and treated as plain text.|

-## Create an Incoming Webhook

-## Remove an Incoming Webhook

-|Incoming Webhook|This sample code demonstrates how to send card using incoming webhook. |[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/incoming-webhook/csharp)|[View](https://github.com/OfficeDev/TeamsFx-Samples/tree/release/incoming-webhook-notification) |

-* [Create an Outgoing Webhook](~/webhooks-and-connectors/how-to/add-outgoing-webhook.md)

-* [Create an Office 365 Connector](~/webhooks-and-connectors/how-to/connectors-creating.md)

-* [Share to Teams from web apps](~/concepts/build-and-test/share-to-teams-from-web-apps.md)

-* [Integrate web apps](~/samples/integrate-web-apps-overview.md)

-* [Secure access and data in Azure Logic Apps](/azure/logic-apps/logic-apps-securing-a-logic-app)

-* [Build notification bot with JavaScript](../../sbs-gs-notificationbot.yml)

-* [Build your first bot app using JavaScript](../../sbs-gs-bot.yml)

-See the following video to learn how to create an Outgoing Webhooks:

-## Key features of Outgoing Webhook

- 

-* [Create an Incoming Webhook](~/webhooks-and-connectors/how-to/add-incoming-webhook.md)

-* [Create an Office 365 Connector](~/webhooks-and-connectors/how-to/connectors-creating.md)

-* [Create and send messages](~/webhooks-and-connectors/how-to/connectors-using.md)

-* [Build notification bot with JavaScript](../../sbs-gs-notificationbot.yml)

-* [Build your first bot app using JavaScript](../../sbs-gs-bot.yml)

-> [!VIDEO <https://www.microsoft.com/en-us/videoplayer/embed/RE4OIzv>]

-This event gives your service an opportunity to perform any clean up actions.

-1. [Set up an Incoming Webhook](~/webhooks-and-connectors/how-to/add-incoming-webhook.md#create-an-incoming-webhook) directly for your team.

-* [Create and send messages](~/webhooks-and-connectors/how-to/connectors-using.md)

-* [Create an Incoming Webhook](~/webhooks-and-connectors/how-to/add-incoming-webhook.md)

-* [Create an Office 365 Connector](~/webhooks-and-connectors/how-to/connectors-creating.md)

-* [Build notification bot with JavaScript](../../sbs-gs-notificationbot.yml)

-* [Build your first bot app using JavaScript](../../sbs-gs-bot.yml)

-1. Check the Teams channel associated with the webhook URL. You can see the new card posted to the channel. Before you use the connector to test or publish your app, you must do the following:

-* [Office 365 Connectors for Microsoft Teams](~/webhooks-and-connectors/how-to/connectors-creating.md)

-* [Create an Incoming Webhook](~/webhooks-and-connectors/how-to/add-incoming-webhook.md)

-* [Create an Outgoing Webhook](~/webhooks-and-connectors/how-to/add-outgoing-webhook.md)

-* [Build tabs with Adaptive Cards](~/tabs/how-to/build-adaptive-card-tabs.md)

-* [Format cards in Microsoft Teams](~/task-modules-and-cards/cards/cards-format.md)

-* [Build notification bot with JavaScript](../../sbs-gs-notificationbot.yml)

-* [Build your first bot app using JavaScript](../../sbs-gs-bot.yml)

-> You can choose to build notification bot Teams app other than incoming webhooks. They perform similarly but notification bot has more functionalities. For more information, see [Build notification bot with JavaScript](../sbs-gs-notificationbot.yml) or [incoming webhook notification sample](https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/incoming-webhook-notification). To get started, download [Teams Toolkit](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension) now and explore. For more information, see [Teams Toolkit documents](../toolkit/teams-toolkit-fundamentals.md).

-#### Notification bot or incoming webhook - choose the right one

-Before you start to learn how to build Incoming webhooks, you may also want to know that you can build Notification Bot using Teams Toolkit. Notification Bots can enable more customizable experience to meet different business scenarios.

-Learn more about the differences between Notification Bot and Incoming webhook so that you can choose correct solutions for your scenarios:

-| Tutorial | [Build notification bot with JavaScript](../sbs-gs-notificationbot.yml) | [incoming webhook notification sample](https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/incoming-webhook-notification) |

-> [Create an Outgoing Webhook](~/webhooks-and-connectors/how-to/add-outgoing-webhook.md)

-* [Create an Incoming Webhook](~/webhooks-and-connectors/how-to/add-incoming-webhook.md)

-* [Create an Office 365 Connector](~/webhooks-and-connectors/how-to/connectors-creating.md)

-* [Build notification bot with JavaScript](../sbs-gs-notificationbot.yml)

-* [Build your first bot app using JavaScript](../sbs-gs-bot.yml)

-| 09/30/2022|Manage SaaS licenses for third party apps in Teams.|Monetize your app > Include a SaaS offer with your Teams app > [Manage license for third party apps in Teams](concepts/deploy-and-publish/appsource/prepare/include-saas-offer.md#manage-license-for-third-party-apps-in-teams)|