Dynamics 365 Business Central Dual Use Rights: License Key Renewal Requirements for CSP Partners

Microsoft has introduced a critical update for partners managing Dynamics 365 Business Central Dual Use Rights (DUR) licenses. Starting immediately, customers using Business Central on-premises under DUR must download and replace their license keys every six months from the Microsoft 365 Admin Center. Failure to do so risks service disruption—something no CSP partner can afford for their customers.

This change directly impacts how partners manage hybrid cloud/on-premises deployments and requires immediate adjustments to internal processes. If your practice supports Business Central, you need to understand the mechanics of this update and communicate proactively with affected customers.

What Changed with Dual Use Rights License Keys?

Dual Use Rights allows Business Central online subscribers to also run the solution on-premises—for example, in scenarios requiring offline capabilities, custom host integrations, or regulatory data residency requirements. Previously, DUR license keys had more flexible renewal terms. Under the new policy, each DUR license key is valid for the subscription term plus a short buffer period, requiring active renewal every six months.

The license keys are retrieved from the Microsoft 365 Admin Center, and the enforcement is now stricter. When a key expires, the on-premises instance will stop functioning. This is not a soft limit—it is a hard technical enforcement of the subscription boundary.

Key Facts Partners Must Know

- DUR customers must download new license keys every 6 months from the Microsoft 365 Admin Center
- Keys are tied to the underlying subscription term and include a limited buffer period
- Expired keys cause the on-premises Business Central environment to stop functioning
- Only CSP partners with active DUR subscriptions are affected—standalone on-premises customers using perpetual licenses are not impacted
- The change applies to both new and existing DUR configurations

Why Microsoft Made This Change

Microsoft is tightening license enforcement to prevent subscription abuse and ambiguity between online and on-premises usage. DUR was originally designed as a transitional bridge for partners moving customers to the cloud, but it has increasingly been used as a permanent hybrid deployment model. By enforcing six-month key rotation, Microsoft is ensuring that:

1. On-premises usage remains tightly coupled to active subscription status
2. Partners cannot grandfather perpetual on-premises rights through online subscriptions
3. Customer compliance and audit trails are maintained automatically

What Should Partners Do Now?

1. Audit Your DUR Customer Base

Run a report of all customers with active Business Central subscriptions that include Dual Use Rights. For each:
- Confirm whether they are actively using the on-premises component
- Identify who manages the on-premises environment (partner, customer IT, or third party)
- Record the current license key expiration date and set calendar reminders 30 and 7 days before renewal

2. Update Internal Service Processes

If your managed services team supports Business Central on-premises instances:
- Add DUR key renewal to your quarterly service checklist - Assign a specific technician or account manager to monitor key expiration
- Document the exact steps for downloading keys from M365 Admin Center
- Create a standard operating procedure for communicating changes to customers

3. Communicate Proactively with Customers

Send a notice to all affected DUR customers advising them of:
- The new six-month key renewal requirement
- Who is responsible for downloading and applying the key ( ideally the partner, with customer approval)
- What happens if the key expires (service stops)
- The next renewal date specific to their subscription

4. Evaluate Whether Cloud Migration Makes Sense

For customers running on-premises Business Central solely because of legacy inertia, this is an opportunity to discuss full cloud migration. Online Business Central eliminates the key management burden entirely and provides:
- Automatic updates and feature delivery
- Reduced infrastructure management overhead
- Simplified licensing with no on-premises key dependencies
- Better integration with Microsoft 365 and Power Platform

Customers with genuine on-premises requirements—such as custom hardware integrations or strict data residency—should remain on DUR, but with tighter renewal discipline.

How to Download and Apply DUR License Keys

The process is managed through the Microsoft 365 Admin Center:

1. Log in to admin.microsoft.com as a Global Admin or License Admin
2. Navigate to Billing → Licenses
3. Locate the Dynamics 365 Business Central subscription with DUR
4. Select Download license key
5. The key file is provided in the standard Business Central license format (.flf)
6. Import the key into the on-premises Business Central administration console under Deployment → License
7. Restart the Business Central Server instance to apply the key

Commercial Implications for CSP Partners

This change adds operational overhead to DUR-managed customers. Partners should consider:

- Adjusting managed service pricing for DUR customers to account for the additional quarterly license key management
- Reviewing DUR margin economics—if the customer overhead increases, ensure your CSP margin justifies the service model
- Opportunity to upsell full cloud Business Central to customers uncomfortable with the new key management burden
- Risk mitigation: Unmanaged DUR customers who let keys expire may blame the partner. Proactive communication protects your reputation and builds trust

Compliance and Audit Considerations

Microsoft's license compliance audits now explicitly check DUR key currency. Partners surveyed in Microsoft License Advisor (MLA) or audit processes should be prepared to demonstrate:

- Active subscription status for each DUR instance
- Current license key files with matching subscription terms
- Documentation of key download and application dates

Non-compliance can result in true-up costs or subscription suspension. The six-month renewal cycle helps keep compliance current, but only if partners execute it reliably.

Key Takeaways for Partners

- Dual Use Rights license keys must now be renewed every 6 months via Microsoft 365 Admin Center
- On-premises Business Central stops functioning if the key expires
- Partners should audit their DUR customer base and build renewal processes immediately
- Proactive customer communication is essential to avoid surprise service disruptions
- Full cloud migration remains the simplest path to eliminate key management overhead
- Include DUR key management in your managed service scope and pricing

The six-month renewal cycle is straightforward in theory but operationally significant at scale. For partners managing dozens or hundreds of Business Central customers, this is a process that must be automated in your PSA or service desk platform. Treat DUR key expiration with the same urgency as domain renewal or SSL certificate expiry—because the business impact is identical.

Source: Microsoft Partner Center Announcements

Ready to grow your Microsoft practice? Explore Cloud Factory's partner program →