Microsoft has locked in the final date for retiring the eAgreements portal and VLCM Smart Client: July 24, 2026. After that, partners can no longer create, renew, or modify non-Enterprise Agreement volume licensing deals in the legacy tools. The company had originally pointed to July 10, but the two-week extension, confirmed in a July 14 adoption-call recap on Microsoft Learn, is not a grace period—it’s an operational fuse. Every open package, pending renewal, extension, or contact-information change must be completed in VL Central by that deadline, or risk getting stuck in a read-only limbo.

The new timeline: read-only first, then gone

According to the latest guidance, Microsoft is staging the shutdown:

  • July 24, 2026: eAgreements and the VLCM Smart Client become read-only for all non‑EA programs. Partners can still search and view historical agreements, but they cannot create or transact new business.
  • End of July 2026: The Smart Client and eagreements.microsoft.com are fully decommissioned. Read-only access disappears, and only VL Central retains the data.
  • August 11, 2026: The final partner adoption call. By then, the legacy systems will already be gone; the call is for refining workflows, not getting started.

The affected non‑EA programs are Open Value, Open Value Subscription, Campus/EES, SPLA, ISV Royalty, Select, and Select Plus. For distributors, SPLA resellers, ISV distributors, and LSP/SSP/EDA teams that manage these contracts, the message is blunt: the old ways end in July. Full stop.

What the cutoff really means for licensing operations

It’s easy to conflate “read-only” with “safe fallback.” The distinction, however, is about what you can still do—and what you can’t.

Once read-only hits, you can look up historical package details, check agreement numbers, or confirm which documents were uploaded. But if a package is half‑finished, you cannot push it forward. If a renewal needs a signature, you cannot send it. If a customer contact must be updated, you cannot make the change. Those actions can only happen in VL Central, and only if the responsible people have access, know the flow, and have acted before the deadline.

For the IT or licensing lead, the immediate job is to stop treating legacy-tool visibility as a records-management strategy. A viewable screen is not a recoverable workflow. Every business‑critical piece of information that lives only in eAgreements—package identifiers, signer status, internal approvals—must be extracted and stored independently before the Smart Client and web interface are turned off at the end of July.

A practical checklist for the next three weeks

Rather than a vague migration nudge, Microsoft’s adoption‑call recap pushes a package‑by‑package discipline. Here’s what hands‑on teams should tackle right now:

  1. Inventory every non‑EA package. List all open, pending, or soon‑to‑start new agreements, renewals, extensions, and contact‑info changes. Assign each to a named owner and note its state, customer organization, program, and any signing or document requirements.
  2. Classify each item as complete, transferable, or at risk. Completed work should be archived with the necessary evidence. Transferable work must be recreated or continued in VL Central. At‑risk items—those with missing access, unclear ownership, unreachable signers, or open support cases—need escalation now, not after July 24.
  3. Verify VL Central access by role. Don’t settle for “I can log in.” Make sure the people who must create, submit, administer, or review packages can see the correct customers and perform their assigned actions. Test workflows for each program your organization handles.
  4. Confirm signing choices early. Adobe Sign and DocuSign are both available for all non‑EA programs (since May 7 for DocuSign). In Greater China, DocuSign is the only in‑tool option, so affected teams must verify signer readiness before a package reaches the final step.
  5. Preserve evidence now. For every business‑critical agreement, save the package identifiers, contact details, internal approvals, and signature status in your approved records system. Don’t rely on a legacy search screen that will vanish.
  6. Open support escalations before the cutoff. If VL Central blocks you from creating, finding, assigning, or completing a package, log the issue through the established support channel while eAgreements is still accessible for comparison. After July 24, demonstrating what was in the legacy system becomes much harder.

The happy path—creating a new package in VL Central, filling in the required fields, and sending it for signature—already works. The failure cases lie in missing administrators, unrecognized package owners, inaccessible customer records, or signers who haven’t been briefed. Treat every exception as a time‑sensitive business risk.

Different partner roles, different pressure points

The cutover doesn’t hit everyone the same way.

  • Distributors must address scale and delegation. They often hold the broadest view of customer and reseller activity, making them the natural point to reconcile packages with unclear ownership or competing internal handoffs. Their July‑24 readiness review should explicitly identify who creates packages, who validates data, who handles customer contact, and who can make an escalation decision when a package is blocked.
  • SPLA resellers should treat the transition as a continuity exercise. Confirm that the people responsible for recurring operational work—new agreements, renewals, extensions, contact changes—have VL Central access and understand the new package flow. Communicate the date to customers clearly: after July 24, the old interface can be searched but cannot move a transaction forward.
  • ISV distributors need a clean record of each program package’s commercial and document state. The real safeguard is not an informal spreadsheet but an evidence set that connects the agreement, customer contact, current package state, and next required action—especially where later disputes may hinge on what was visible in the former system.
  • LSP, SSP, and EDA teams must ensure their operational model isn’t built around a handful of legacy‑tool specialists. Document VL Central access, package ownership, signing selection, support escalation, and record retrieval across the team. An access gap can become a business‑continuity issue when the only knowledgeable operator is unavailable.

How we got here: a Secure Future Initiative migration

The retirement stems from Microsoft’s Secure Future Initiative (SFI), which drives modern authentication and platform consolidation. Enterprise Agreement migration to VL Central happened earlier, and since April 7, 2026, the remaining seven non‑EA programs have been available in the Contracts workspace. A parallel production period let partners continue using eAgreements while adopting VL Central at their own pace. A monthly adoption call series—April through August—has guided the transition.

Microsoft originally set July 10 as the read‑only date. The July 14 adoption call moved it to July 24, buying two extra weeks. But those weeks aren’t for delay; they are for closing the gaps that the parallel run exposed. Partners who haven’t yet completed their migration have no more wiggle room.

What to do now, ordered by urgency

If your organization touches non‑EA volume licensing, this week’s to‑do list should already be in motion:

  • Stop creating new packages in eAgreements immediately. Use VL Central exclusively for all new, renewal, extension, and contact‑change work. The parallel run is effectively over.
  • Complete the inventory and triage described above. Every outstanding item needs a decision and an owner before July 24.
  • Run a controlled package review for each program your team handles. Enter VL Central, open the Contracts workspace, select the applicable action, locate the customer, and walk through the full flow. This exercise surfaces missing permissions or process gaps while eAgreements remains available for side‑by‑side checks.
  • Secure your historical evidence. Identify the agreements and packages critical for compliance, renewal planning, or dispute resolution. Retrieve and store the documents, status records, and contact details in a repository you control. Test that you can find them without logging into a legacy tool.
  • Push support cases now. If VL Central can’t do what you need, don’t wait until the old system is gone to prove what worked before. Log the issue, attach screenshots of the eAgreements state if necessary, and get on the path to resolution.

After July 24, use eAgreements only as a temporary historical reference—if it’s still available. By the end of the month, your team must be fully operational in VL Central, able to create, track, sign, and retrieve everything you need without ever glancing back at the retired interfaces.

The final adoption call and beyond

The August 11 adoption call arrives after the legacy tools are dust. It’s a forum for refining workflows, not for first‑time readiness. Partners who haven’t shifted by then will already be facing operational gaps. Looking ahead, Microsoft will extend Entra ID (Work or School Account) secure authentication to non‑EA programs and customers in Q2, along with AI‑powered contract assistance and further automation. Those improvements only matter if your team is comfortably working inside VL Central. The July 24 deadline is the last hard gate before that future becomes the present.