EphraimF on Wed, 26 Apr 2017 14:00:01

One of the requirements of addins is that the application must verify that the user has a valid license.

I can't find any documentation on how to access Microsoft's license server via JavaScript.

Please point me to documentation on this.

The only documentation I could find was here: and this page only has code written in C#.  I understand that addins consists only of html, JavaScript, and an xml manifest.

Thank you.

-- Ephraim



Deepak Saradkumar Panchal on Thu, 27 Apr 2017 09:39:23

Hi EphraimF,

From your description , I assume that you got the error "Paid Outlook add-ins must support a site license."

Below are some details regarding license provided by Microsoft Documentation.

Acquiring an add-in license for an Outlook add-in:-

The following figure shows the add-in license acquisition process for Outlook add-ins when the add-in is acquired directly from the Office Store. When the user acquires the add-in, the Office Store generates an add-in license, which it retains, and downloads a corresponding add-in license token to the user's Exchange deployment. For Outlook add-ins with a per-user license, the token is downloaded to the personal mailbox of the person acquiring the add-in. For Outlook add-ins with a site license, the token is downloaded to the organization mailbox of the Exchange deployment. For Outlook add-ins offered for free or as unlimited trials, no license is generated or stored by the Office Store, and so no license token is downloaded to Exchange. The user can then use the add-in.


How licenses work for Office and SharePoint Add-ins

License your Office and SharePoint Add-ins

Add license checks to Office and SharePoint Add-ins

in link below check Validation policy no 10.5 but no any detail description is available for that.

Validation policies for apps and add-ins submitted to the Office Store

only these documentation are available on licensing. I will try to find the further documentation and if I find anything useful I will try to provide you.



EphraimF on Fri, 28 Apr 2017 18:38:24

I've been using the following document to create my licensing verification code:

The document states that , for Outlook add-ins,


  • Create your test token.
  • Create a URL-encoded version of the add-in license token.
  • In the add-in manifest file, manually edit the appropriate SourceLocation element. Add the URL-encoded version of the license token to the source location URL as a query parameter named et ."

I can't find any reference to a SourceLocation element that the string could go into. Please give me an example.

Also, I understand that the license is passed to the JavaScript application via a Get URL variable named "et",  The application is to extract the variable and send it to the  VerificationSvc.VerifyEntitlementTokenRequest service.  The service then returns a VerificationSvc.VerifyEntitlementTokenResponse.  Where in the processing does the SourceLocation in the manifest come in?

Thank you,


Deepak Saradkumar Panchal on Tue, 02 May 2017 08:13:22

Hi EphraimF,

please try to refer the suggestion I gave on other thread created by you.

SEC7120: Origin https://localhost:44384 not found in Access-Control-Allow-Origin header.



MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact