Skip to content

Commit 8659644

Browse files
authored
Remove crucial; add statement about all SPFx components.
1 parent 5be7056 commit 8659644

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -119,8 +119,8 @@ this.context.sdks.microsoftTeams
119119
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).
120120
Using this API assures the supported version of Teams JS is loaded and initialized.
121121

122-
Few crucial details to keep in mind:
123-
- Installing and initializing custom versions of Teams JS SDK is **unsupported**.
122+
Few details to keep in mind:
123+
- 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.
124124
- 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.
125125

126126
## See also

0 commit comments

Comments
 (0)