Skip to content

Commit 4d8675a

Browse files
authored
Update deployment-spfx-teams-solutions.md
Added to important section the clear guidance that this doesn't work cross-___domain after confirming with the PG.
1 parent 876ad94 commit 4d8675a

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/spfx/deployment-spfx-teams-solutions.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ To use your own Microsoft Teams app manifest & app package instead of letting Sh
6767
- [Microsoft Teams: Create an app package for your Microsoft Teams app](/microsoftteams/platform/concepts/build-and-test/apps-package)
6868
- [Microsoft Teams: Manifest schema for Microsoft Teams](/microsoftteams/platform/resources/schema/manifest-schema)
6969

70-
> [!IMPORTANT]
70+
> [!IMPORTANT]
7171
> in the Teams app manifest ensure you add the following entry:
7272
> ```json
7373
> "webApplicationInfo": {
@@ -76,6 +76,7 @@ To use your own Microsoft Teams app manifest & app package instead of letting Sh
7676
> }
7777
> ```
7878
> That is required to ensure any API call in the component will succeed from Microsoft Teams rich clients.
79+
> **teamSiteDomain** will be the same tenant that the Teams client is using, this will not work cross-tenant/cross-___domain so you cannot hardcode another ___domain in.
7980
8081
1. Create the Microsoft Teams app package named **TeamsSPFxApp.zip** by compressing the contents of the **./teams** folder.
8182

0 commit comments

Comments
 (0)