Microsoft Dynamics 365 | Integration, Dataverse...

Secure deployed solution from being exported and shared

(0) Share

Report

Posted on by l.oliver

Hi,

I'm not sure if this is the right forum to ask this question but here it goes:

I have a preconfigured Dynamics 365 CE solution that I want to deploy in a customer's environment.

After deploying, how would I secure or prevent the customer from being able to just export the solution and share it with others?

Also, the customer is going to pay a subscription for using this solution, how would I manage if the customer just stops paying - can I then block my custom entities and features?

I have the same question (0)

All responses (2)

Answers (0)

l.oliver 6 on at

Like (0)

Report
Copy link

Link copied!

Hi Adrian Begovich,

Thanks a lot for your reply.

It will definitely be deployed as a managed solution. But I'm pretty sure it's quite easy (with a little knowledge for D365 CE) to just create a new solution and import all the default entities and stuff and then export that new solution, right? Or maybe I'm wrong?

I was thinking that some custom logic for checking for active licensing was the way and I will have to look into that. But let's say a customer is not paying for the license, will it then be possible to block anything in the solution, like logic, entities, or something like that? Do you have any experience with this or do you know where I can look for more information about this?

Was this reply helpful? Yes No
Suggested answer

Adrian Begovich 1,027 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi l.oliver,

The best approach is to create your solution as a managed solution since it is not possible to export a managed solution. You will need to create logic in your managed solution to call an API and check that the customer's solution is licensed.

Was this reply helpful? Yes No