Congratulations! You’ve made the smart decision to use VisualSP to provide in-context support to your users. The next thing to consider is how you should deploy VisualSP to your environment. The following are some common scenarios with their recommended deployment strategies. Your options are to deploy a custom action to SharePoint Online, or deploy a browser extension via GPO. Depending upon your environment, one or both deployment strategies may work for you.
- Your environment includes SharePoint Online. Best practice is to deploy VisualSP via custom action using our Installation Wizard or PowerShell script. The benefit of deploying as a custom action is your users will see the VisualSP Help tab without the need for a browser extension.
- Your environment includes other Office 365 apps such as OneDrive or Outlook. Deploy our browser extension via GPO. The only way to see the VisualSP Help tab in Office 365 is with a browser extension. The browser extension works seamlessly with SharePoint Online site collections that have our application deployed via a custom action so it is okay to use both methods.
- You need to make the VisualSP install part of an existing build process. Automatically deploy VisualSP to new site collections by adding our PowerShell script to your build process.
- Your SharePoint Online environment uses multi-factor authentication. Deploy VisualSP via PowerShell. If you aren’t using MFA, our Installation Wizard is the recommended deployment tool.
- You have more users than licenses. You can deploy either the custom action or the browser extension. As part of your activation, our support team will configure your subscription to Block New Users. Next, upload a list of users to your Subscription list. Only those users will see your licensed content.