问题
I developed an Office Word add-in that I'd like to make available to organizations as well as single users. I understand that the AppSource will only grant licenses to single users, and that if I want to distribute to organizations I must create my own licensing and accounting backend[1] and have an IT professional at the purchasing organization run a centralized deployment of the add-in.
My question deals with finding the best practice to offer the app on AppSource such that both an single user and an enterprise client can deploy the app straight from AppSource.
The rub is that I'm not willing to make my app free, which is a requirement for Centralized Deployment[3]:
You may only add free add-ins from AppSource; adding paid add-ins isn't currently supported.
So, I'm thinking that I can't multipurpose my add-in on the AppSource and instead either:
- Provide two add-in products in app source. One that does token checks only, and another that does user identity checks only. The second one being "free" on AppSource and Centralized Deployment friendly.
- Only provide a token-based app in AppSource, and create a secondary manifest that I provide to organizational purchasers.
Both solutions are clunky and my aim to simplify the code base. I'm basically wondering what is the standard(best) practice(s) to provide an AppSource add-in that can serve both individual and organizational users?
回答1:
Personally I'd make the add-in free and use your own licensing backend to allow users to activate the functionality. This is common practice for other addins
Thanks Phil
来源：https://stackoverflow.com/questions/49743745/how-are-office-add-ins-in-appsource-distributed-to-organizations-and-single-user