Teams JS Version to use (SharePoint#8381)

* Teams JS Version to use

* remove en-us in the url

* relative url without view param

* Remove crucial; add statement about all SPFx components.

* Teams JS SDK info in considerations

Author: AJIXuMuK

docs/spfx/build-for-teams-considerations.md

@@ -32,6 +32,12 @@ SharePoint Framework is meant to extend UI of the services it’s being used wit
 
 SharePoint Framework solutions consist only of client-side code. If your solution requires server-side code for example to run long-running operations, scheduled processes or connecting to other systems that don’t support the OAuth implicit flow, you would need to build this functionality separately and expose it through an API secured with Azure Active Directory. Your SharePoint Framework solution would then [securely connect to this API on behalf of the current user](use-aadhttpclient.md).
 
+## Teams JS SDK
+
+SharePoint Framework provides access to Teams JS SDK via `sdks.microsoftTeams` property in the [context's API](/javascript/api/sp-webpart-base/webpartcontext#@microsoft-sp-webpart-base-webpartcontext-sdks-member).
+> [!IMPORTANT]
+> Installing and initializing custom versions of Teams JS SDK is **unsupported**. This is applicable to any SPFx component, including web parts, extensions, adaptive cards, and libraries.
+
 ## Deployment
 
 SharePoint Online can automatically create the Microsoft Teams app manifest and app package for SharePoint Framework solutions deployed to the tenant's app catalog, or they can use a developer-provided Microsoft Teams app package. Refer to [Deployment options for SharePoint Framework solutions for Microsoft Teams](deployment-spfx-teams-solutions.md) for detail on these options.

docs/spfx/integrate-with-teams-introduction.md

@@ -114,6 +114,15 @@ this.context.sdks.microsoftTeams
 >
 > You should use `this.context.sdks.microsoftTeams` for all solutions created with the SharePoint Framework v1.10 and later.
 
+## What Teams JS SDK version to use?
+
+The SharePoint Framework provides access to the Teams JS SDK instance and context using `sdks.microsoftTeams` property in the [context's API](/javascript/api/sp-webpart-base/webpartcontext#@microsoft-sp-webpart-base-webpartcontext-sdks-member).
+Using this API assures the supported version of Teams JS is loaded and initialized.
+
+Few details to keep in mind:
+- Installing and initializing custom versions of Teams JS SDK is **unsupported**. This is applicable to any SPFx component, including web parts, extensions, adaptive cards, and libraries.
+- Although Teams JS SDK types are tied to the SPFx version used in the solution, the actual version loaded to the tenant may differ. We guarantee backward compatibility on our end. For example, a solution built with SPFx 1.14 will have types from Teams JS 1.10.0, and SPFx 1.15.2 will have types from Teams JS 1.12.1, but the actual loaded version can be 2.1.0. 
+
 ## See also
 
 - [Building Microsoft Teams tab using SharePoint Framework - Tutorial](web-parts/get-started/using-web-part-as-ms-teams-tab.md)