Two ways to sell, one clear limit
Microsoft’s documentation describes the main route: you submit your service in Partner Center as a software-as-a-service offer, and your add-in “is free for your customers to download but requires a license to your service”. The add-in authenticates against Microsoft’s SaaS service to confirm the subscription. Microsoft handles billing and transactions, the publisher FAQ states “a 3% standard store service fee” and “no cost to publish”. You can have Microsoft manage licenses, which needs a Graph API integration, or run your own license management site.
The limit is in the same page: “Transactable SaaS apps are only purchasable using a work or school account.” For buyers with personal Microsoft accounts, the docs say to consider your own billing model, and they add that “you’re also free to monetize using your own payment model”.
That gives a simple rule of thumb:
| Your buyers | Better route |
|---|---|
| Companies buying with work accounts, who like to buy through Microsoft | AppSource transactable offer |
| Freelancers, consultants and individuals on personal accounts | Stripe and Clavem |
| Both | List on AppSource and also sell direct, as separate channels |
| You want invoices and terms you set yourself, or no marketplace review | Stripe and Clavem |
Whichever you choose, tax on a direct sale is yours to handle through Stripe. This is general information, not tax advice.
Web add-ins and VSTO behave differently
An Office add-in made with Office.js has “two basic components”: an app package with a manifest, and “your own web application” hosted on a web server. The add-in’s pages run in a webview. Older VSTO, COM and XLL add-ins are Windows desktop code installed on the machine.
| Office.js web add-in | VSTO, COM or XLL add-in | |
|---|---|---|
| Runs | In a webview, on Windows, Mac, the web and iPad | On Windows desktop Excel |
| Where the code lives | Your web server, loaded at each start | An installer on the machine |
| License check from | A fetch in your JavaScript |
.NET or C++ code |
| Failure if your server is down | The add-in does not load | None |
| Guide | Node.js guide | C# guide |
The fourth row matters. A web add-in is only as available as your hosting, for every Excel launch, before a license check even runs. Host it on a service you trust, and cache aggressively.
What is specific to Office.js
Same-origin policy. Microsoft’s docs say that, because add-ins are hosted in a webview, “the same-origin policy applies to script running in their web pages”. The License API allows cross-origin POSTs from any origin, with a preflight that accepts the content-type header, so the task pane can call it directly. Use a form-encoded body to skip the preflight entirely.
Storage. There is no hardware id. Keep a random id and the license in OfficeRuntime.storage or localStorage, and send the random id as fingerprint. Excel for the web, on a Mac and on Windows are separate clients, each likely to hold its own storage, so a user who works in all three may take three device slots. A limit of 5 allows for that.
Per user or per device. Office add-ins are often thought of per user. Clavem counts devices, so a “device” here is an Excel client. If you prefer per-user licensing, set a higher device limit and sell one key per user.
Custom functions. Functions that cells call, such as =YOURADDIN.PRICE(A1), run many times in a single sheet recalculation. Check the license once when the add-in loads and keep a flag. A call to the License API from each cell would be slow and would exceed the License API’s limit of 60 requests a minute per key.
Corporate rollout. IT departments deploy add-ins to all users from an admin center, and many corporate networks use proxies. Keep the stored token and verify it offline when a call fails.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| License type | Annual subscription per user | A yearly invoice per user is easy for a company to approve and renew |
| Device limit | 5 | Windows, Mac, web, plus a second computer |
| Trial | 14 to 30 days, started on first use | Long enough to test on real workbooks |
| Updates | Your web host, for web add-ins | Deploy once and every user gets it at the next load |
For a web add-in there is nothing to download, so Clavem’s file hosting is not part of the flow. A VSTO add-in ships as an installer, which you can host as a release file and offer on the order page.
Doing this with Clavem
Create a product, connect Stripe and map the price. A buyer gets a key by email. The task pane has a field for the key, calls activate once and validate on load. Teams buying 10 seats set a quantity of 10, and Clavem issues 10 keys. See software for businesses for invoices and VAT ids.
Guides to follow
- License key validation in Node.js
- Offline license verification in Node.js
- License key validation in C#
- Device activation in C#
Questions
Can I sell an Office add-in through Microsoft Marketplace?
Yes, as a transactable SaaS offer. Microsoft's docs say your app is free to download and requires a license to your service, and the publisher FAQ states a 3% standard store service fee. Transactable offers can only be bought with work or school accounts, so sales to personal Microsoft accounts need your own billing.
Does the License API work from inside an Office add-in?
Yes. Office add-ins run in a webview where the same-origin policy applies, and the License API answers cross-origin requests from any origin, so a fetch from the task pane works without a proxy.
Sources
- Microsoft Learn, monetize your Microsoft 365 add-in through Microsoft Marketplace (checked November 2026)
- Microsoft Marketplace publisher FAQ, 3% store service fee (checked November 2026)
- Microsoft Learn, same-origin policy in Office Add-ins (checked November 2026)
- Microsoft Learn, Office Add-ins platform overview (checked November 2026)