-### Cards

-For card support, see [card formatting](~/task-modules-and-cards/cards/cards-format.md).

-description: Learn how to integrate your app from Teams Developer Portal to Teams Toolkit in Visual Studio Code and Visual Studio.

-description: Learn how to configure, distribute, and manage your apps using the Developer Portal for Microsoft Teams.

-description: In this module, learn how to get started with Teams in Microsoft 365 and create your development environment

-description: Learn how to enable the Share to Teams button on your personal app or tab, limitations, and end user experience.

-description: Learn to add the Share to Teams embedded button on your website, with a website preview, using Code samples

-description: Learn share to Teams overview and where you can create share-to-teams button in the Teams apps and tab apps.

-description: In this article, learn more about the tools and SDKs available for building your Microsoft Teams app.

-| [Fluid Framework](https://fluidframework.com/docs/) | Fluid Framework consists of client libraries that help distribute and synchronize shared state. These libraries enable multiple clients to simultaneously create and operate on shared data structures using coding patterns similar to those used to work with local data. | :::image type="icon" source="../../assets/icons/red-dot.png" border="false"::: You can pass the reference to **Live Share SDK**. </br> :::image type="icon" source="../../assets/icons/grey-dot.png" border="false"::: Based on **Azure Fluid Relay**. |

-> `defaultGroupCapability` provides the default capability that will be added to the team, groupchat, or meeting. Select a tab, bot, or connector as the default capability for your app, but you must ensure that you have provided the selected capability in your app definition.

-description: Learn to plan growth lifecycle for your Teams app.

-description: Learn what you can do during the build stage of your app to grow your app.

-description: Learn what you can do during the traction stage of your app to grow your app.

-Microsoft will evaluate coactivation opportunities in large customer accounts. Evaluation is based on customer interest, adoption opportunity (sold seat size in customer account), and so on, among other criteria.

-Connect with the [ISV Marketplace Success Rewards Program team](mailto:rewards@microsoft.com) to seek guidance and execute. You'll be able to utilize Microsoft slide templates, customer story intake form, customer interview template, and vendor video production, or copy writing services. Introduce a creative team to the customer. Help facilitate the interviews and review processes until the story is approved by all parties. Microsoft team will make sure your customer story is published to the internal Microsoft Teams Platform Resource Library and the Transformed by Teams portal.

-Microsoft will evaluate coactivation opportunities in large customer accounts based on customer interest, adoption opportunity (sold seat size in customer account), and so on, among other criteria. Get in touch with your Microsoft field, account, or engineering representatives to discuss potential joint customer pitches in large customer accounts.

-Get the power of the Microsoft executive team behind your next leadership blog or event. Review your plans for blogs or events in which you'll be participating. Develop ideas on how a Microsoft executive can help to promote your commercial marketplace offer in a blog or at an event. Reach out to the [ISV Marketplace Success Rewards Program team](mailto:rewards@microsoft.com) to request Microsoft executive endorsement. If eligible, the team will work with you to find a Microsoft executive (Director level or higher) to help endorse your Teams collaborative app available on the marketplace.

-When someone finishes buying a subscription plan for your app in the Teams Store, the commercial marketplace will direct them to your landing page where they can manage the subscription (such as assign a license to a specific user in their org).

-Once published, users will see a **Buy a subscription** option in the app details dialog when they try to add your app to Teams.

- > These accounts must be utilized only for validation requirements. The validation team will test your app fully, including first-run user experience.

- > If your app is free for all users and anyone who intends to use your app can sign up to use it, indicate the same in the test notes. The validation team will use the sign up process as described.

-```javascript

-import {location} from "@microsoft/teams-js"

-let locationProps = {"allowChooseLocation":true,"showMap":true};

-if(location.isSupported()) {

- microsoftTeams.location.getLocation(locationProps, (error, location) => {

- // If there's any error, an alert shows the error message/code

- if (error) {

- if (error.message) {

- } else {

-}

-else {/*Handle case where capability isn't supported */}

-```

-```javascript

-import {location} from "@microsoft/teams-js"

-let location = {"latitude":17,"longitude":17};

-if(location.isSupported()) {

- microsoftTeams.location.showLocation(location, (error, result) => {

- if (error) {

- if (error.message) {

- alert(" ErrorCode: " + error.errorCode + error.message);

- } else {

- alert(" ErrorCode: " + error.errorCode);

- }

- }

- });

-}

-else {/*Handle case where capability isn't supported */}

-```

-```javascript

-let locationProps = {"allowChooseLocation":true,"showMap":true};

-microsoftTeams.location.getLocation(locationProps, (err: microsoftTeams.SdkError, location: microsoftTeams.location.Location) => {

-});

-```

-```javascript

-let location = {"latitude":17,"longitude":17};

-microsoftTeams.location.showLocation(location, (err: microsoftTeams.SdkError, result: boolean) => {

-});

-```

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

-```JavaScript

- function getLocation() {

- location.getLocation({ allowChooseLocation: true, showMap: true }).then((location) => {

- let currentLocation = JSON.stringify(location);

- }).catch((error) => { /*Error getting location*/ })}

-```

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

-```JavaScript

- function getLocation() {

- microsoftTeams.location.getLocation({ allowChooseLocation: true, showMap: true }, (error: microsoftTeams.SdkError, location: microsoftTeams.location.Location) => {

- let currentLocation = JSON.stringify(location);

- });

- }

-```

-***

-> Sorting is not supported on all the attributes of the respective Graph resources. If a user tries to sort on a virtual table with an unsupported attribute, this result set will have its default order. This is the same behaviour as the Dataverse Web API on columns that don't support sorting.

-> You can set the `If-Match` header to be '*' and then you'll not need to provide any etag values, but your changes will always overwrite the task and itΓÇÖs details.

-> HostNames with `ngrok`'s free tunnels are not preserved. Each run will generate a different URL. When a new `ngrok` tunnel is created, the older container will no longer be accessible. For production scenarios, see [use AzureClient with Azure Fluid Relay](#use-azureclient-with-azure-fluid-relay).

-Live Share's media package work doesn't with DRM content. Teams doesn't support encrypted media for tab applications on desktop. Chrome, Edge, and mobile clients are supported.

-Developers will be encouraged to certify their new plugin after successfully completing validation.

-> * We recommend that you use Teams Toolkit CLI v3 to build your Teams app. TeamsFx CLI v1 and TeamsFx CLI v2 will soon be deprecated.

-1. Sign in to [Developer Portal for Teams](https://dev.teams.microsoft.com/home) using the corresponding account. Teams Toolkit opens your selected Teams app's page.

-1. Go to **Publish** > **Publish to store**.

-The tunnel you have created will be under **Dev Tunnels(MyPublicDevTunnel)** > **MyPublicDevTunnel**.

-* Prepare Teams app dependencies: Teams Toolkit prepares local debug dependencies and registers your Teams app in your tenant account. For Bot and Message Extension apps, Teams Toolkit will register and configure bot.

-If you get errors with Teams Toolkit in Visual Studio Code, you can select **Get Help** on the error notification to go to the related document. If you're using TeamsFx CLI, there will be a hyperlink at the end of error message that points to the help doc. You can also view [provision help doc](https://aka.ms/teamsfx-arm-help) directly.

-If Teams Toolkit failed to update Microsoft Entra app, there will be an error that says:

-Download the auto-generated app manifest (previously called Teams app manifest) from the Developer Portal (<https://dev.teams.microsoft.com>). Perform the following steps, before testing or publishing the app: