title: Word add-in multiple production environments
body: <p>In order to support multiple production environments for our Word add-in, we need to be able to redirect the user to another server on login.</p>
  
  <p>This is so that the version of the add-in in environment X would always be compatible with our other services (API, etc.) in the same environment.</p>
  
  <p>A sample setup would be:</p>
  
  <ul>
  <li><strong>Default Word Add-in</strong> (e.g. located at [domain].com - this is the URL in SourceLocation on the manifest)</li>
  <li><strong>Production 1 Word Add-in</strong> (e.g. on Version 1.0.0, located at subdomain1.[domain].com)</li>
  <li><strong>Production 2 Word Add-in</strong> (e.g. on Version 2.0.0, located at subdomain2.[domain].com)</li>
  </ul>
  
  <p>The intention is for the user to login via the <strong>Default Add-in</strong> and then be redirected within the taskpane to <strong>Production 1</strong> or <strong>Production 2</strong>.</p>
  
  <p>Is it possible to redirect the user to another instance on the Word add-in within the taskpane?</p>
  
  <p>In Word online, when redirecting with <code>window.location.href</code>, the following error occurs:<br>
  "Something went wrong and we couldn't start this add-in. Please try again later or contact your system administrator."</p>
  
  <p>On desktop Word on Mac, <code>window.location.href</code> simply opens a browser window on the new location instead of loading it in the taskpane.</p>
  
  <p>Thanks,</p>
  
  <p>Morgan</p>