web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

ISV Licensing Strategy to Control Sales, Purchase, and Production Modules in Business Central

(5) ShareShare
ReportReport
Posted on by 41

Hi everyone,

I am developing an app in Microsoft Dynamics 365 Business Central as an ISV, mainly covering the Sales, Purchase, and Production modules.

My customers fall into two categories:

  • Distribution customers – require only Sales and Purchase functionality
  • Manufacturing customers – require Sales, Purchase, and Production functionality

Based on this, I want to implement an In-App licensing mechanism that allows me to enable or disable specific modules (Sales, Purchase, Production) depending on the license a customer has purchased.

My questions are:

  1. What is the recommended approach to implement ISV licensing in Business Central?
  2. Is it possible to create module-based licensing (Sales-only, Sales + Purchase, Full Manufacturing)?
  3. Should licensing be handled using:
    • Internal license tables with feature flags?
    • External license validation service (API)?
  4. Are there any Microsoft guidelines or best practices for ISV licensing (especially for AppSource vs private extensions)?
  5. What are the limitations I should be aware of when enforcing licensing inside Business Central?

I am particularly interested in best practices used by ISVs to control functionality securely and in a way that is compliant with Microsoft’s rules.

Any guidance, references, or real-world examples would be greatly appreciated.

Thanks in advance.

I have the same question (0)
  • Suggested answer
    OussamaSabbouh Profile Picture
    6,871 on at
    Hello ,
     
    Best practice is feature-based licensing enforced in AL. Use a central License Management codeunit with internal feature flags (Sales, Purchase, Production) and block functionality at business logic points (posting/processes), not just pages. Module-based licensing is fully supported. Many ISVs add an optional external license validation API with caching and a grace period. This approach is AppSource-compliant, upgrade-safe, and the most common real-world ISV pattern.
     
    Regards,
    Oussama Sabbouh
  • Suggested answer
    YUN ZHU Profile Picture
    95,987 Super User 2025 Season 2 on at
    We previously created our own activation module.
    It used a fixed algorithm to generate activation codes based on the customer's name and activation date. Users could only use the features after verifying the activation code.
     
    Hope this can give you some hints.
    Thanks.
    ZHU
  • Chaitanya kumar Muppuri Profile Picture
    41 on at
     
    Thank you for the reply 
     
    Could you share any references for the process you have implemented? That would be very helpful for me.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 1,810

#2
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 810 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 676 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans