Microsoft volume licensing partners can no longer create, modify, or renew commercial packages in the classic VLCM or eAgreements portals for seven non-Enterprise Agreement programs. The legacy systems became read-only on July 10, 2026—not in August, when the interfaces themselves are expected to finally retire.

The distinction is more than a calendar nuance. July 10 was the functional cutoff for new agreement, renewal, extension, and Change of Channel Partner (CICP) transactions. The remaining window for launching the old tool is now strictly archival: you can look up history, download documents, and verify package details, but you cannot push a single new deal through it.

For licensing operations teams, the message is clear: the migration to VL Central Contracts is not something that can wait until the servers switch off. It has already moved from project planning to production reality.

What Actually Changed, and When

Microsoft made VL Central Contracts generally available for non-EA programs on April 7, 2026. That launch covered Open Value, Open Value Subscription, SPLA, ISV Royalty, Campus/EES, Select, and Select Plus—the seven commercial programs that sit outside the Enterprise Agreement family.

For a few months, both the old and new tools ran in parallel. Partners could create packages in either system and, according to Microsoft’s guidance, those packages were visible in both. But the company explicitly warned against splitting work on the same agreement across the two portals.

Then, on July 10, 2026, the old door closed. VLCM (both its Smart Client and web-based eAgreements) shifted to read-only status for those seven programs. Read-only means exactly what it says: agreement lookup, document review, and historical-data downloads remain available, but no new package—whether a fresh enrollment, a renewal, an extension, or a CICP—can be created or advanced in the legacy interfaces.

The final retirement of the VLCM Smart Client and eAgreements web interface is penciled in for August 2026, though Microsoft’s own timelines describe the window as “TBD in August 2026” in one place and “August/September 2026” in another. That lingering ambiguity matters for contingency planning and for anyone who hasn’t yet pulled critical historical records, but it shouldn’t be read as a business-process deadline. The tools that mattered for making money stopped accepting new work on July 10.

Who Feels This Now

Partners carrying non-EA commercial business

Any Microsoft partner that still manages Open Value, Open Value Subscription, SPLA, ISV Royalty, Campus/EES, Select, or Select Plus agreements needed to be fully operational in VL Central by July 10. If a team tried to initiate a renewal or extension in the old portal after that date, the attempt simply failed—no mysterious policy error, just a tool that no longer does the one thing you need it to do.

That has an immediate customer-facing impact. The partner can’t generate a quote, can’t compose the license order, and can’t move the package forward until the right people pick up the work in the new system. Delays that used to be explained as “the portal is slow” now have a more fundamental root cause: the portal no longer supports the transaction.

Organizations that consume licensing through a partner

End customers rarely care which licensing portal their partner uses. What they notice is a quote that doesn’t arrive on time, a renewal that needs an unexpected extension discussion, or documents that appear inconsistent. A partner’s failure to complete the operational cutover turns a backend tooling change into a customer experience problem.

IT and procurement teams that self-manage agreements

Some organizations interact directly with Microsoft’s volume licensing interfaces or rely on internal license-administration staff who are accustomed to the legacy VLCM workflows. Those teams need to know that the old path no longer works for the named programs and that any active agreement paperwork must be created exclusively through VL Central, even if the final shutdown date of the classic client hasn’t been announced.

The Timeline That Actually Matters

Three milestones define the transition—and two of them already carry more weight than the final one:

  • April 7, 2026 — VL Central Contracts became generally available for the seven non-EA programs.
  • July 10, 2026 — VLCM/eAgreements made read-only for those same programs. New transaction creation stopped.
  • August/September 2026 (unconfirmed) — Expected retirement of the VLCM Smart Client and eAgreements web interface.

For a licensing operations manager, the August window is an access-risk deadline, not a business-process deadline. The ability to transact already moved. The unresolved end date is about how long you can still retrieve your old paperwork without opening a support ticket.

How We Got Here

Volume Licensing Central—often shortened to VL Central or simply VLC—is Microsoft’s modern replacement for the Volume Licensing Service Center (VLSC) and the older Volume Licensing Management Center (VLCM) tools that partners and some customers have used for decades. The original interfaces were built for a licensing ecosystem that relied heavily on manual package assembly, faxed signatures, and offline agreement management.

Over several years, Microsoft has been migrating agreement types to the newer platform. Enterprise Agreements moved earlier, and the April/July milestones completed the shift for the remaining non-EA commercial programs. Throughout the transition, Microsoft’s enablement materials underscored a simple logic: when the old system goes read-only, that’s the transaction cutover. The final decommissioning date is a cleanup event.

What changed in mid-2026 is more than a URL. The new workspace combines agreement search, order creation, and document management into a single interface that assumes a partner has the correct roles assigned at the start—not something to configure once a package is already behind schedule.

What You Should Be Doing Now

If your organization or your partner touches any of the seven non-EA programs, the following steps turn the official transition timeline into an operational reality check.

1. Sort every active package by program and urgency

Separate your Open Value, Open Value Subscription, SPLA, ISV Royalty, Campus/EES, Select, and Select Plus agreements from everything else. For each, flag whether any commercial action is still needed: a new order, a renewal, an extension, a channel change. If the answer is yes, that package already belongs in VL Central. The old system can’t help you.

A package that only requires historical look-up or document retrieval can stay on the VLCM reference list. But be honest: if the “research” is actually a precursor to a new transaction, redirect it now rather than starting a half-finished package in the wrong tool.

2. Test real user access, not just sign-in

The most common cutover failure is discovering that the employee who actually builds and moves the paperwork hasn’t been assigned the correct role in VL Central. A successful sign-in proves nothing about whether that person can open the right agreement, compose an order, or submit it. Run an end-to-end dry run with a non-critical workflow—ideally for each high-volume agreement type—and verify that internal hand-offs between sales, operations, and licensing specialists still function.

3. Designate one system of record for each package

During the parallel-production weeks before July 10, a package created in VL Central might appear in VLCM, and vice versa. That visibility was never an invitation to divide work. Pick a system—for any package that needs a new transaction, that system is now VL Central—and record that ownership internally. Stop using the old portal as a parallel workspace. If someone on the team opens the legacy tool to “help” complete a VL Central package, they risk creating conflicting versions or, worse, assuming a step has been done in the new interface when it hasn’t.

4. Grab the history while you can

Read-only access is a window to download agreement documents, package histories, and other evidence you may need for audits, customer entitlement verification, or renewals. Don’t assume those records will remain available indefinitely after the final retirement date. Prioritize downloads for agreements that are active, recently renewed, or frequently questioned by customers.

5. Build an exception route today

There will be packages where the migration status isn’t clear, where a permission issue blocks a transaction, or where a customer’s unique agreement structure doesn’t fit the new tool’s default workflow. Assign a named operational owner for those edge cases now, before a customer deadline turns a manageable portal question into a commercial incident. That owner should know the approved support path and should be empowered to escalate inside Microsoft if the normal automated route doesn’t cover the scenario.

6. Don’t over-apply the seven-program rule

The July 10 read-only milestone applies to Open Value, Open Value Subscription, SPLA, ISV Royalty, Campus/EES, Select, and Select Plus. It does not apply to Enterprise Agreements, nor to any other agreement families that may follow their own transition schedules. Treating “VL Central” as the universal answer without confirming your agreement type’s specific status risks giving customers the wrong timeline or, worse, trying to force a non-matching package through the wrong portal.

A Practical Reality Check for Partners

None of this is glamorous, but it’s the work that keeps renewals orderly. A partner that waited for the August decommissioning announcement would have already spent weeks unable to create new business in the old tool. During that time, customer opportunities don’t pause.

Consider a Select Plus renewal that would have landed in August. If the partner had not completed its VL Central readiness by July 10, the operations team would discover the problem on the first attempt to build the package—likely with a customer wanting a quote the same week. The fix isn’t a few clicks; it’s role assignments, agreement-location training, and possibly a scramble to retrieve the enrollment details that were never transferred.

What Comes Next

The final retirement of the VLCM Smart Client and eAgreements web interface—whenever it lands in August or September—will close the book on a toolset that served the channel for decades. For most partners, that event will feel like a formality: the real work of migration will be behind them.

Microsoft has not published a precise shutdown date, but the company’s messaging has been consistent that the legacy systems are no longer places to conduct business. The prudent assumption is that the old portal can disappear on a timetable that is no longer relevant to transaction creation but very relevant to the historical evidence you may still need to preserve.

If your team has inventory, access, and exception handling sorted, the final retirement notice will be a calendar item, not a crisis.