Skip to content

Commit 473716c

Browse files
authored
Teams JS SDK info in considerations
1 parent 8659644 commit 473716c

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,12 @@ SharePoint Framework is meant to extend UI of the services it’s being used wit
3232

3333
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).
3434

35+
## Teams JS SDK
36+
37+
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).
38+
> [!IMPORTANT]
39+
> 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.
40+
3541
## Deployment
3642

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

0 commit comments

Comments
 (0)