Dynamics 365 Business Central Dual Use Rights: New Six-Month License Key Renewal Requirement

Microsoft has introduced an important operational change for Cloud Solution Provider (CSP) partners supporting customers who use Dynamics 365 Business Central online together with on-premises deployments under Dual Use Rights. Beginning June 5, 2026, customers running Business Central on-premises through Dual Use Rights must refresh their license keys on a six-month cycle.

For partners, this is more than a licensing footnote. It creates a recurring compliance and continuity task that needs to be built into customer lifecycle management, renewal processes, and support runbooks. Customers that rely on on-premises Business Central environments for production, integrations, reporting, warehouse operations, or business continuity scenarios should understand that license key replacement is now a regular requirement, not a one-time setup activity.

What changed

Dynamics 365 Business Central online customers may have rights to run an on-premises Business Central environment through Dual Use Rights, often abbreviated as DUR. This model is commonly used when an organization subscribes to Business Central online but still needs an on-premises deployment for a specific business reason, such as a phased cloud migration, local integrations, regulatory constraints, or operational dependencies that have not yet moved fully to the cloud.

Microsoft’s June 5 announcement states that these on-premises deployments must now use license keys that are downloaded and replaced every six months. In practical terms, partners and customers should expect the license key associated with the on-premises Business Central deployment to have a time-bound validity period. The key is intended to align usage of the on-premises environment with the active Business Central online subscription term.

This means the license key should no longer be treated as a static artifact that is installed once and then forgotten. It becomes part of ongoing subscription administration.

Why this matters for CSP partners

The key point for CSP partners is that responsibility does not stop at selling or renewing the Business Central online subscription. Partners must make sure customers remain properly licensed and that the technical environment reflects that licensing status.

If a customer’s on-premises Business Central deployment depends on a Dual Use Rights key, an expired or outdated key can become a service continuity risk. Even where a buffer period exists after the subscription term associated with the downloaded key, Microsoft is clear that customers are not permitted to keep using the DUR license after the underlying Business Central online subscription has expired. The buffer is not a grace period for unlicensed use; it is a technical safeguard intended to prevent abrupt disruption while subscriptions and keys are administered correctly.

For partners managing multiple Business Central customers, this creates a need for tracking. A customer may be current on their online subscription but still experience problems if the on-premises license key is not refreshed in time. Conversely, a customer whose subscription has lapsed must not continue operating under a Dual Use Rights key simply because the on-premises system still appears to function.

Default behavior and customer impact

The announcement does not describe a change to Business Central functionality itself. The impact is on licensing operations for on-premises deployments that are tied to Business Central online subscriptions through Dual Use Rights.

Customers most likely to be affected include organizations that:

- subscribe to Dynamics 365 Business Central online through CSP;
- also maintain a Business Central on-premises deployment under Dual Use Rights;
- use that on-premises deployment for production workloads, integrations, testing, reporting, or transitional migration scenarios;
- rely on a partner to manage subscription renewals, licensing, or Business Central administration.

The expected operational impact is straightforward: every six months, a replacement license key must be downloaded and applied to the on-premises environment. If the process is missed, the customer may face avoidable disruption or licensing non-compliance. The exact technical symptoms will depend on the customer’s Business Central deployment and timing, so partners should not wait until a system warning or failure appears before taking action.

Where to get replacement keys

Microsoft directs customers to download new and replacement Dual Use Rights license keys from the Microsoft 365 Admin Center. In many CSP scenarios, the partner will either guide the customer through that process or perform the administrative work where delegated administration and customer agreements allow it.

Partners should confirm who owns the task for each customer: the customer’s internal administrator, the CSP partner, a Business Central implementation partner, or a managed services team. Ambiguity here can easily lead to missed renewals.

Recommended partner actions

Partners should treat this update as a prompt to review their Business Central customer base and establish a repeatable control. Recommended actions include:

1. Identify affected customers

Review customers with Dynamics 365 Business Central online subscriptions and determine whether any are running Business Central on-premises under Dual Use Rights. Do not assume that all customers are cloud-only simply because they hold online licenses. Migration, integration, and hybrid scenarios are common.

2. Record current key dates

For each affected customer, document when the current DUR license key was downloaded or applied, the associated subscription term, and the next replacement deadline. If this information is not centrally available, coordinate with the customer’s Business Central administrator or implementation team to verify it.

3. Add a recurring renewal process

Create a six-monthly operational task to download and replace keys. Ideally, schedule reminders well ahead of the deadline, with enough time for testing and customer change windows. Treat this like a certificate renewal or domain renewal: simple when planned, painful when missed.

4. Align with subscription renewal checks

When reviewing Business Central subscription renewals, include a specific DUR license key check. Confirm that the customer’s online subscription remains active and that the on-premises key has been refreshed appropriately. This helps avoid a gap between commercial renewal and technical licensing.

5. Communicate the compliance boundary

Customers should understand that Dual Use Rights depend on an active Business Central online subscription. A technical buffer after the subscription term associated with a downloaded key does not authorize continued use after the subscription has expired. Partners should make this explicit in customer communications and managed service procedures.

6. Update support runbooks

Support teams should know that license key age and subscription status are relevant troubleshooting data points for affected on-premises Business Central environments. Adding this to intake checklists can reduce escalation time if a customer reports access or licensing issues.

Bottom line

Microsoft’s update makes Dual Use Rights license key management for Dynamics 365 Business Central a recurring responsibility. CSP partners should identify affected customers, establish a six-month replacement cadence, and align key management with subscription renewal and compliance processes.

The change is manageable, but it should not be ignored. Partners that build the renewal task into standard operations can help customers avoid disruption while ensuring that on-premises Business Central use remains tied to valid online subscription rights.

Source: https://learn.microsoft.com/en-us/partner-center/announcements/2026-june#dynamics-365-business-central-dual-use-rights-license-keys-update