Learn how to create a simple license management system to manage Add-ins sold in Microsoft AppSource.
Office Add-in SAAS monetization sample
Installation and configuration
Follow the instructions in the deployment guides to install and configure the sample.
Teams Add-in deployment guide:
Additional Add-ins deployment guides:
Follow the instructions in the test guide to test the different use cases.
This section links to the various README files associated with the projects included in the sample. Read the README files for more information about each project.
- Teams Tab App
- Teams Bot (C#) App
UX / API Mapping
This matrix describes the UI actions and how they correlate to different API calls.
|UI where the API is invoked||API call||Able to test the production API without the offer being published to the public?|
|Resolve a subscription in purchase process:
|Activate a subscription in purchase process:
SharePoint Add-ins Note
A Provider-Hosted SharePoint Add-in cannot target a .NETCORE web project. In this sample, the Provider-Hosted SharePoint Add-in web project targets a .NET Framework project.
To work around this technical limitation, the OfferID is hardcoded in the AzureADAuthController.cs class in the Provider-Hosted Add-in, and it is hardcoded in the app.js file in the SharePoint-Hosted Add-in.
Copyright (c) 2020 Microsoft Corporation. All rights reserved.