You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/spfx/integrate-with-teams-introduction.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,9 @@ Starting with SharePoint Framework v1.7, you can build your Microsoft Team tabs
11
11
12
12
There are following benefits on using SharePoint Framework as the platform for your Microsoft Teams tabs:
13
13
14
-
- Development model is similar as for SharePoint Framework web parts
15
-
- Technically any web part can be exposed as a tab in the Microsoft
16
-
- You have difference scoping options on exposing your custom tab as a web part and tab in your tenant
14
+
- Development model is similar as for SharePoint Framework web parts.
15
+
- Technically any web part can be exposed as a tab in Microsoft Teams.
16
+
- You have different scoping options on exposing your custom tab as a web part and tab in your tenant.
17
17
- Your tab will be executed in the context of the underlaying SharePoint site behind of the specific team. This means that you can take advantage of any SharePoint specific APIs or functionalities in your web part.
18
18
19
19
> [!IMPORTANT]
@@ -32,10 +32,10 @@ You can start developing Microsoft Teams tabs simply by using the `with beta` ve
32
32
yo @microsoft/sharepoint --plusbeta
33
33
```
34
34
35
-
1. Create a solution with a client-side web part
36
-
1. Deploy web part using tenant-scoped deployment option to your SharePoint app catalog
37
-
1. Package `manifest.json` located in the `/teams` folder in your solution as a zip file . This file was automatically configured with default settings when your solution was created
38
-
1. Deploy your zip file (application) to the Microsoft Teams and start add a new tab in the preferred channel
35
+
1. Create a solution with a client-side web part.
36
+
1. Deploy web part using tenant-scoped deployment option to your SharePoint app catalog.
37
+
1. Package `manifest.json` located in the `/teams` folder in your solution as a zip file . This file was automatically configured with default settings when your solution was created.
38
+
1. Deploy your zip file (application) to the Microsoft Teams and start add a new tab in the preferred channel.
39
39
40
40
> [!NOTE]
41
41
> You can also follow the detailed steps to get started from the [Building Microsoft Teams tab using SharePoint Framework](web-parts/get-started/using-web-part-as-ms-teams-tab.md) tutorial.
@@ -70,4 +70,4 @@ Page context in a web part has by default a reference to the Teams JavaScript SD
70
70
71
71
## See also
72
72
73
-
-[Building Microsoft Teams tab using SharePoint Framework - Tutorial](web-parts/get-started/using-web-part-as-ms-teams-tab.md)
73
+
-[Building Microsoft Teams tab using SharePoint Framework - Tutorial](web-parts/get-started/using-web-part-as-ms-teams-tab.md)
0 commit comments