Hi,
Lets assume I am a Microsoft certified Gold partner and I have create an ISV names PowerSales 1.0 .(PowerSales as an example can have any sort of customization)
I would like to understand how I can sell this ISV to the customers via the Microsoft marketplace as an SAAS where clients can directly go and subscribe to it and on expiration can again activate it.
In this case how will the licensing structure work.
Also since this is D365 FO how will the packages deploy because lets say I am updating my ISV PowerSales every month to version 1.2,.1.3 and so on. So how will the client update his envt . Will he have to everytime upload the package provided by me in and run it via the lcs or there is some better approach.
Also can we provide an ISV in D365 FO based on users , eg I would like to enable the powerSales functionality only for 10 users then client will have to purchase 10 licenses.
In case client wants to update the license users to 16 in that case they will only update the license or there is no such thing in license for number of users.
Thanks,
VK
Hi Vicky,
Scenario 1: Yes, it can give issues, depending on the features and how it has been developed. E.g. batch jobs might still run or end in an error. Also, code extensions might still continue to run if there is no proper evaluation if the license is still enabled or not.
Scenario 2: You will be in control for providing a new license. The customer is not able to renew the license himself. Even when you sell the solution via partners, the partner would not be able to renew the license.
If you need some automation, you can create an own solution where the license generation will be created upon request and after the payment.
Hi Andre,
Many thanks for providing as always detailed explanation of the ISV for SAAS marketplace.
I have been going through the documents and have some more queries and below is my understanding.
A company ABC publishes his app PowerSales in marketplace with videos and demos. Customer will check in marketplace and contact.
Company might give demo and then the user will pay based on fee and the license will be provided by the company lets say for 1 year.
After 1 year there are 2 scenarios .
scenaribo 1 ) customer will not opt to go for the functionality and will not renew the license . In this case what will happen to the existing functionality of PowerSales . I guess the objects will remain in the envt but it might not be visible because the config/license has expired. Can this solution give any error while Microsoft releases further updates in the future.
scenario 2) Customer continues fro PowerSales so he will again purchase the license and will update in his envt via LCS . In this case company is involved to renew/share license and get feedback from customer for upgrade and so on.
Now for this scenario I have a major query which is like can it happen that the Customer can directly go to the appsource and renew the license and he will get the license directly without involving the company.
Its like Amazon prime/youtube subscription of a service which will autorenew on payment and in this case it should also consider the number of users.
Thanks,
VM
Hi Vicky,
A lot of great questions. I'm working for a global ISV and will answer your questions. First of all, you can read the documentation about the requirements for getting an app on the AppSource: Requirements for publishing apps on AppSource - Finance & Operations | Dynamics 365 | Microsoft Docs
Once your app is on the AppSource, there is an option for interested customers to contact you via AppSource. Then the contact information will be send to e.g. CRM. Once the customer wants to buy your solution, it would be you who will provide access to deployable packages and the license.
On LCS you can create a solution page which would have the deployable package. There are more requirements for the solution page as you can read in the documentation. The solution page can be published and you can give access to the customers who acquired your solution. The customer will then see the solution in their own LCS project and can get the deployable package. For every update, you will upload the new deployable package to the solution and the moment you publish the new version, the customers will be notified about the availability of a new update.
About the licensing, you can read the documentation: Independent software vendor (ISV) licensing - Finance & Operations | Dynamics 365 | Microsoft Docs. The license file includes an optional user count parameter. This can be used for users, but also e.g. number of records or transactions. Out of the box, the customer will not be limited by the user count in the license. If you need a license enforcement, you would need to add logic to your own solution which could read the user count and restrict adding more users via to e.g. security roles or a user table in your solution. When the customer need an increase in number of users, you can provide a new license with a higher user count.
The licenses can have an expiry date, which can be used for renewal dates. You can use this to provide e.g. licenses per year based on a subscription or yearly enhancement fee. Once the customer did not terminate the agreement, you can provide a new license with a next expiry date.
André Arnaud de Cal...
292,160
Super User 2025 Season 1
Martin Dráb
230,962
Most Valuable Professional
nmaenpaa
101,156