VisualSP deployment best practices

Applies to: VisualSP
Print Friendly, PDF & Email
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. Depending upon your environment, one or more deployment strategies may work for you.

  1. 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.
  2. Your environment includes other Office 365 apps such as OneDrive, Outlook, Office Online, etc. Deploy our browser extension via GPO. The only way to see the VisualSP Help tab in all Office 365 apps is with a browser extension. The browser extension also works seamlessly with SharePoint Online sites that have our application deployed via a custom action so it is okay to use both methods.
  3. You need to make the VisualSP install part of an existing build process. Automatically deploy VisualSP to new sites by adding our PowerShell script to your build process.
  4. Your SharePoint Online environment uses Multi-Factor Authentication (MFA). MFA requires deployment of VisualSP via PowerShell. If you aren't using MFA, our Installation Wizard works great and is the recommended deployment tool.
  5. You want to deploy VisualSP to a subset of your users. 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 and upload a list of your chosen users to your Subscription list. Only those users will then see the VisualSP licensed content.
Updated on May 17, 2020

Related Articles