Forum Discussion
ISV Offering SaaS vs On-Prem
Hi all, We are a partner and have some apps on the marketplace (appsource) for customers to download. We would like to offer the same apps for on-premise deplyments as well. How would we go about...
JillArmourMicrosoft
Community Manager
Community ManagerI have forwarded this to the team and will post their response when I receive it. Thanks for being part of the community.
JillArmourMicrosoftCommunity Manager
Community ManagerThis is what the team came back to me with:
The commercial marketplace is designed for cloud licensing only. It doesn’t support On-Prem licensing and doesn’t recognize such licenses in a buy-flow process. Additional details below explain that answer, also references areas of “On Prem” being mentioned in AppSource ISV offers.
Transact: Designed for products in the cloud.
- A 3P solution built upon a first-party D365 or Power product, the first-party license is part of the fulfillment of a transacted offer. In this case, the customer must either: 1. Currently possess the appropriate cloud license, which buy-flow detects. 2. Acquire the cloud product license through the buy-flow, when one isn’t found.
- LM: License Management in the buy-flow only recognizes cloud licenses, it will not know a customer may have any type of On-Prem license.
Non-transact: Designed to allow ISVs to advertise/merchandise, generate interest, and potentially fulfill through their own channels.
- When you move from transact offer to a Free/Get Now, Contact Me, or Free Trial there are a number of examples that are marketed as On-Prem, that stretches that definition into different ways, such as a product that allows BC customers to connect to devices that are On-Prem, yet the BC license is itself cloud.
- In everyone of these use cases, whatever the use of “On-Prem” is specifically about, the client must discuss those details directly with the ISV, they are not supported by LM in the commercial marketplace.