Related Read: Original blog post: Say Bye Bye to Developer License!
In 2018, I published a blog post titled “Say Bye Bye to Developer License!” that unexpectedly stirred up quite a bit of conversation in the Microsoft Dynamics 365 Business Central community. It was one of our most commented-on pieces, leading to discussions across Yammer, blog pingbacks, and even some internal policy reviews. At one point, it even led to a temporary restriction for me on Microsoft’s Collaborate portal. Thankfully, a constructive discussion with Microsoft followed, and I was reinstated.
The blog was sparked by my experiments with Business Central’s then-preview on-premise version. I demonstrated how AL development didn’t seem to require the traditional partner developer license anymore. I even added a cheeky message inside a codeunit: “Bye Bye Developer License.” The line resonated widely, and not just because it was a bit provocative.
Today, in 2025, I want to revisit this topic and offer a more current, clarified perspective – especially for those still navigating the on-prem vs. cloud divide.
Then: The Great Developer License Debate
Back in 2018, Microsoft was aggressively shifting from C/SIDE and C/AL to AL-based extension development. This transition created a lot of confusion about what licensing developers actually needed.
Some key voices from the community weighed in:
- Arndt pointed out that customers still needed object licenses for page and table extensions in on-prem installations.
- Erik P. Ernst highlighted the deeper licensing changes – from concurrent users to named users – and how this would impact customers financially.
- Andrei G. asked the million-dollar question: *”Do we still need a developer license for on-prem development or not?”
I responded with live tests and experimentation, which led me to believe that at least in AL-based development, the traditional developer license was no longer necessary – especially on cloud or sandbox environments.
Now: What’s Changed in 2025?
Let’s get the answer straight:
✅ For Business Central Cloud
No developer license, no Object [in the range of 50000 .. 99999] license is required to develop AL extensions. You can:
- Use VS Code and the AL extension.
- Deploy to a sandbox environment.
- Package and publish via AppSource or PTE (Per Tenant Extension) deployment.
This makes Dynamics 365 Business Central Cloud ideal for agile AL development without worrying about separate dev licensing.
⚠️ For Business Central On-Premise
The situation is different:
- You do not need a separate “developer license” to use VS Code and AL.
- However, you still need to license the object ranges (e.g., 50,000-99,999) for creating new tables, pages, reports, etc.
- These object permissions are now embedded in the customer’s license, but the requirement to purchase object ranges remains.
So the short answer is:
The traditional developer license as a standalone item is gone, but development rights for on-prem still require licensing specific object ranges.
This nuance is essential for partners working on Business Central on-prem development, especially those building tenant-specific solutions.
Lessons Learned
Looking back, the controversy wasn’t a bad thing. It revealed how many of us were confused – not due to lack of knowledge, but due to evolving policies and unclear documentation.
I appreciate everyone who joined the discussion, disagreed respectfully, and pushed the conversation forward. It made Microsoft listen. It made us all better.
Final Thoughts: Advice for Today
- If you’re working only with Business Central Cloud, development is easier than ever – no dev license, no object range purchase.
- If you’re developing on-prem, talk to your licensing partner or CSP. Object range licensing is still critical.
- When in doubt, ask. Engage with the community or with experts like us.
At DynaExperts, we help partners and customers not just with development and training, but also with navigating these licensing intricacies. Whether you’re building your own app, going to AppSource, or just customizing for your tenant, we can help you do it right.
Still have questions about developer licensing in Business Central? Let’s talk. [snehanshu@dynaexperts.com]
Frequently Asked Questions (FAQ)
Q1: Do I need a developer license for Business Central in 2025?
A: For cloud environments, no developer, no object [in 50000..99999 range] license is required. For on-prem, you still need to license object ranges for custom development.
Q2: Can I develop AL extensions in Business Central without a license?
A: Yes, for cloud-based environments. In on-prem setups, object range licensing is required to create new tables, pages, or reports.
Q3: What is object range licensing in Business Central?
A: It’s a requirement for on-premise installations where customers must purchase a block of object IDs (e.g., 50,000- 99,999) to perform AL-based custom development. Check here for more details
Q4: Is there a difference in licensing between cloud and on-prem versions of Business Central?
A: Yes. Cloud versions don’t require object range licensing for development, while on-prem installations still do.