Microsoft is changing how license keys work for on-premises Dynamics 365 Business Central releases starting October 1, 2026. For Business Central version 28 and later, partners and customers will move from version-specific license keys to a forward-compatible “28+” license key model.
At first glance, this sounds like simplification. In practice, it creates a new operational requirement: customers must download a refreshed 28+ license key before upgrading to newer Business Central versions if they want the latest objects unlocked.
What is changing
New Business Central releases on or after October 1, 2026 will no longer use separate version-specific license keys for version 28 and later. Instead, “28+” becomes the relevant license key version. Older releases before version 28 continue to use their existing version-specific keys.
The important nuance is that a 28+ key is not a one-time key that automatically unlocks every future version forever. The download date matters. The key file reflects which objects are available at the time it is downloaded.
For example, a customer preparing to move to a later release such as version 30 may need to download a refreshed 28+ key before the upgrade. If they try to run the newer deployment with an older 28+ key, they may see a version compatibility warning.
Why partners should care
Business Central upgrades already involve application code, extensions, integrations, testing, user acceptance, and downtime coordination. License key handling can seem administrative, but this change makes it a real upgrade dependency.
Partners supporting on-premises Business Central environments should add license key freshness to every upgrade checklist. The correct question is not only “does the customer have a 28+ key?” It is also “was the 28+ key downloaded after the target version’s objects became available?”
If this check is missed until the production upgrade window, the project can face avoidable delays and customer frustration.
Dual Use Rights impact
Business Central online customers using Dual Use Rights for on-premises deployments are also affected. Those customers can download their Dual Use Rights license keys from the Microsoft 365 Admin Center.
Microsoft notes that, at initial release, the version number for those keys may appear as “28” rather than “28+” in the admin center, with the format expected to be corrected by the second week of October. Partners should brief support teams so this temporary display issue does not trigger unnecessary escalations.
The safest practice is to document the key download date, the source of the key, and the target Business Central version in the upgrade record.
Partner next steps
First, update upgrade runbooks. Add a required step to verify the 28+ license key download date before scheduling production cutover.
Second, brief consultants, project managers, and support teams. Everyone involved in Business Central upgrades should understand that the new naming model does not remove the need to refresh keys.
Third, notify customers with on-premises deployments or Dual Use Rights usage. A short advisory can prevent confusion when customers see the new key format.
Fourth, repeat the check for each major upgrade. Every new Business Central version may require a refreshed 28+ key to unlock the latest objects.
Bottom line
The 28+ license key model simplifies naming, but not upgrade discipline. Partners should treat refreshed 28+ keys as a required pre-upgrade dependency for Business Central version 28 and later, especially in on-premises and Dual Use Rights scenarios.