title: Office Web-Addin Deployment via Installer
body: <p>I am developing a web add-in for Microsoft Word and wondering about distribution.</p>
  <p>I have found that there are a few options for publishing them as detailed <a href="https://docs.microsoft.com/en-us/office/dev/add-ins/publish/publish#outlook-add-in-deployment" rel="nofollow noreferrer">here</a>.</p>
  <p>For my company, I do not believe we use Microsoft 365 so Centralized Deployment is not an option. Sharepoint catalogs most likely could work, but have a significant limitation that commands cannot be used. This reduces the functionality available in the add-in significantly. This add-in is targeted at internal employee's only (it would load content accessible only on our network), so it seems to me that publishing to AppSource would not be accepted by Microsoft, although if they would accept it I would be happy to do so.</p>
  <p>Ideally, I would be able to package the add-in with an installer. It looks like this could be done simply for Outlook Add-ins using the Exchange PowerShell command <a href="https://docs.microsoft.com/en-us/powershell/module/exchange/new-app?view=exchange-ps" rel="nofollow noreferrer">New-App</a> after copying the manifest file to some location or letting it be available on a server.</p>
  <p>Some questions:</p>
  <ol>
  <li>Has anyone had success distributing non-Outlook Web Add-Ins via an installer? What was the mechanism to do so?</li>
  <li>It seems to me that based on the content of the manifest file, a web add-in could be distributed for any Office Product via the Exchange PowerShell command, but I could be wrong. Has anyone had success in doing so? It's not easy for me to test.</li>
  <li>Has anyone had success getting add-ins published to App Source for add-ins that are intended for a specific company and offers no functionality outside of that?</li>
  </ol>