Skip to main content


General Licensing Inquiries - Some general licensing Q&A's



  • ArdeviaForum

    Original Post by Vitaliy Zadorozhnyy (Imported from Ardevia Forum)

    Hi Paul,
    Thanks for the question.

    1. Yes, Editing of forms will be restricted to not licensed users, they will be able to edit using only free features, and only licensed users will be able to edit/design form. But the usage of form is not licensed at all. So any user which has access to form can use it.

    2. Ardevia Rich Forms uses standard office 365 store licensing approach, actually application only validates stored license, but license itself is provided by SharePoint store and is stored on SharePoint farm/tenancy using Sharepoint 2013 OOB functionality and office 365 licensing framework. But it looks possible to configure several farms(In case of on premises) to use same license according to this documentation:

    App license scope and the deployment ID for apps for SharePoint

    For apps for SharePoint, each app license applies to a specific app for a specific SharePoint deployment. A user with a license for an app can use that app on any site for that particular SharePoint deployment. In general, for the purpose of app licenses,deployment is defined as the SharePoint farm for on-premises SharePoint installations, and the tenancy for SharePoint Online in Office 365.

    Deployment scope can vary, however, based on the configuration of the on-premises SharePoint installation. App license tokens are stored in the App Management Shared Service; therefore, the actual scope of an app license is determined by the configuration of the App Management Shared Service. A given SharePoint installation could contain multiple web applications using different instances of the App Management Shared Service, and possibly using a federated service. In addition, an on-premises SharePoint installation might be configured for multitenancy, is which case a single instance of the App Management Shared Service might have multiple deployment IDs.

    The deployment ID of the SharePoint installation to which an app license applies is included in each app license. The deployment ID is a GUID generated by SharePoint and recorded by the Office Store the first time anyone from a specific SharePoint installation visits the Office Store site.

    For on-premises SharePoint installations, you can set the deployment ID via Windows PowerShell, for disaster recovery or test/production environment scenarios.


    Relaying on above topic from MSDN, On Premises can be configured to use same deployment ID.

    How to set deployment ID using power shell commands can be found here:


  • ArdeviaForum

    Original Post by Paul Wentink (Imported from Ardevia Forum)

    Thank you very much Vitaliy, this was very useful. What this means to us is that we can go ahead and procure licenses for our existing production environment and then copy the licensing to the development farm by using the deployment ID instructions you provided. Then when we actually finalize the infrastructure move that will replace these two farms with two new farms, we can simply "move" the licenses at that point with the same trick of syncing the deployment ID's.


    I'll review these articles you provided further as well.


Please sign in to leave a comment.