This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 83%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIN%3C/text%3E%3C/svg%3E)
I have seen there are really three options for publishing an Office Add-In:
I'm attempting to develop an Add-In for Word that is for employees of my company only. Additionally, I would like to support MacOS and Windows clients. Our company doesn't use Office 365 and unfortunately is not able to due to security policies. As the add-in is for employees of the company, publishing to App Source likely would not be approved by Microsoft, although if it were I would not be opposed. Our company does have sharepoint sites (on premise), but this leaves out MacOS users and doesn't allow for Commands.
A few questions:
Is there precedent for the Add-In to be added to App Source even though it would offer no functionality to anyone outside of my company?
Is it possible to distribute the manifest.xml via an installer? It seems to me that simply having the manifest file is not sufficient.
https://learn.microsoft.com/en-us/office/dev/add-ins/publish/publish
