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/deployment-spfx-teams-solutions.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,9 @@ SharePoint Online supports two options for deploying SPFx solutions to the Micro
20
20
21
21
This capability is ideal when you have a simple implementation to expose automatically in Microsoft Teams.
22
22
23
-
In this scenario, when an SPFx solution is uploaded to the SharePoint Online tenant app catalog, if the solution contains components for Microsoft Teams, the **Sync to Teams** button in the ribbon is enabled.
23
+
In this scenario, when an SPFx solution is uploaded to the SharePoint Online tenant app catalog, if the solution contains components for Microsoft Teams, the **Add to Teams** button in the ribbon is enabled.
24
24
25
-
:::image type="content" source="../images/sp-teams-sync-to-teams-button.png" alt-text="Sync to Teams":::
25
+
:::image type="content" source="../images/spfx-add-to-teams.png" alt-text="Add to Teams":::
26
26
27
27
This button will start the following process in SharePoint Online:
Copy file name to clipboardExpand all lines: docs/spfx/tenant-scoped-deployment.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -70,14 +70,14 @@ In following example configuration, `skipFeatureDeployment` is set to `true`, wh
70
70
71
71
When the solution with the `skipFeatureDeployment` attribute set to `true` is deployed to the tenant app catalog, the administrator is given an option to configure the solution to be deployed centrally across the tenant.
72
72
73
-
By default, the **Make this solution available to all sites in the organization** check box isn't selected. If the check box is selected by the administrator, components in the solutions are automatically visible and available across the tenant.
73
+
By default, the **Enable this app and add it to all sites** check box is selected and components in the solutions are automatically visible and available across the tenant.
74
74
75
-

75
+

76
76
77
77
Notice that because the solution and site-specific upgrade actions are only available when you use the feature framework, there's no specific upgrade option for the centrally deployed solutions. These solutions can be updated by updating the solution-specific assets in the CDN and by updating and deploying the package in the app catalog. This automatically updates all existing component instances across the tenant to use the latest component assets, such as JavaScript files and updated CSS files.
78
78
79
79
> [!WARNING]
80
-
> For solution packages containing site extension(s), selecting the **Make this solution available to all sites in the organization** check box is only required to activate the site extension(s) initially. When updating existing solution packages, selecting the check box during deployment may create duplicate entries in the **Tenant Wide Extension** list.
80
+
> For solution packages containing site extension(s), selecting the **Enable this app and add it to all sites** check box is only required to activate the site extension(s) initially. When updating existing solution packages, selecting the check box during deployment may create duplicate entries in the **Tenant Wide Extension** list.
81
81
82
82
## Client-side web part visibility on SharePoint sites
83
83
@@ -87,7 +87,7 @@ Web parts included in solutions that have been centrally deployed are immediatel
87
87
88
88
[SharePoint Framework Extensions](./extensions/overview-extensions.md) are immediately available to be used on SharePoint sites. This means that they can be associated with `ClientSideComponentId` properties in the specific SharePoint elements, such as **fields** and **user custom actions**.
89
89
90
-
Additionally, if an administrator selects the **Make this solution available to all sites in the organization** checkbox during deployment, automations in the solution package may create entries in the **Tenant Wide Extensions** list on the app catalog. Entries in this list manage tenant-wide activation of site extensions. The automations are described by the **ClientSideInstance.xml** file as referenced in **./config/package-solution.json**.
90
+
Additionally, if an administrator selects the **Enable this app and add it to all sites** checkbox during deployment, automations in the solution package may create entries in the **Tenant Wide Extensions** list on the app catalog. Entries in this list manage tenant-wide activation of site extensions. The automations are described by the **ClientSideInstance.xml** file as referenced in **./config/package-solution.json**.
91
91
92
92
For more information, see [Tenant Wide Deployment of SharePoint Framework Extensions](./extensions/basics/tenant-wide-deployment-extensions.md).
0 commit comments