Table of contents
Generally there are four different possibilities to install a SharePoint solution created with the skybow Solution Studio on a SharePoint site.
Direct Deployment
This the easiest and fastest option to deploy a solution on another site. It is possible to use it in two different scenarios:
- The solution should be deployed on the same tenant where it was built, just to another site
- The solution should be deployed to a site on another tenant, where Solution Studio is already trusted as well (as described in the article skybow Solution Studio: Installation)
App Deployment
The app deployment can be used, if the solution needs to be deployed on a site on another tenant, where Solution Studio is not trusted and the security department does not approve Solution Studio to get full read and write to all sites.
To make use of the app deployment there is still the need for a global admin for the first installation. The main difference to the direct deployment is, that it is using a separate Azure App registration (skybow App Deployment Connector) which has limited access to specified sites only.
A full documentation on how to set it up can be found here: How to: skybow App Deployment
API Deployment
The skybow API deployment can be used to deploy a solution from outside of Solution Studio e.g. having a projects list which should create a site for each project added to that list and deploy a project template (skybow Solution) into that project site.
To be able to use the API deployment, target environments (tenants) have to be registered and trusted by a global administrator.
This will add the Enterprise application “skybow Solution Studio” with full read and write to all sites to the Entra ID of that environment.
A full documentation on how to set it up can be found here: How to: skybow API deployment