Your vSphere 8 extension ends on whatever date your subscription says. Broadcom's own sentence spells it out: Extended Support runs until "the earlier of the applicable subscription end date or October 31, 2028". It is written inside a portfolio update published on 4 November 2026 — among announcements covering VCF 9.1.1, disaster recovery, native object storage and the new vSphere Express — and it only applies if your company is in the European Economic Area. In that case, vSphere Standard 8 and vSphere Enterprise Plus 8 stay on sale until 31 October 2027.
The paragraph, verbatim
It is worth reading as published, because each clause does a different job: "For customers in countries in the European Economic Area, vSphere Standard version 8 and vSphere Enterprise Plus version 8 will remain available for sale until October 31, 2027, and will have Extended Support included in any active subscriptions to those offerings until the earlier of the applicable subscription end date or October 31, 2028."
Four things, and each one carries weight. It applies by geography. It applies to version 8 and to no other. Sales stay open past that version's end of general support. And Extended Support stops at the earlier of two dates, one of which is yours.
A correction of ours, from four days ago
On 4 November we wrote here that vSphere Express existed without anyone announcing it: distributor listings, channel pricing and public Broadcom technical documentation explaining how to license a product that had neither an announcement nor a blog post. The portfolio update does exist, and it is dated that same 4 November. Correction noted.
The Register, which surfaced the European paragraph on 5 November, pins down one detail worth keeping: the advance copy Broadcom handed to the press did not contain it. It appeared only in the published version.
The three dates, and yours
| Date | What happens | Where it is written |
|---|---|---|
| 11-10-2027 | End of General Support for vSphere 8.0: ESX 8.x, vCenter Server 8.0 and vSAN 8.x | Product lifecycle |
| 31-10-2027 | Last day to buy Standard 8 and Enterprise Plus 8 in the EEA | Blog post, 2026-11-04 |
| 31-10-2028 | Ceiling for Extended Support… or your subscription end date, whichever comes first | Blog post, 2026-11-04 |
| Yours | The end date of the subscription you have signed today | Your contract |
Two pieces of arithmetic of ours on that table. There are 357 days between today and the last day of sale. And end of general support and last day of sale are twenty days apart, in that order. For three weeks in October 2027 it will be possible to buy in Europe, legitimately and with Extended Support included, a version that has already stopped receiving general support. That is not a typo; it is what happens when one date is set by a product lifecycle and the other by a negotiation.
"Whichever comes first"
Three cases, worked out by us from the clause itself. Find yours:
- 1.Your subscription expires in March 2028. Your support ends in March 2028. Seven months less than the headline said, and nobody is going to write to you about the gap.
- 2.Your subscription expires in June 2027. The extension on its own gives you nothing: it ends before it starts. What it gives you is the right to buy again, and that right expires on 31 October 2027.
- 3.You want to reach the October 2028 ceiling. Then you need an active subscription that runs that far, bought inside the sales window. Put another way: 2028 is only reached by buying late and on purpose, inside that window.
Which leaves exactly one figure worth looking up today, and it is in no news story: the end date of the subscription you have signed. It is in your contract or in your reseller portal, it takes ten minutes to find, and it determines the next twelve months of your planning.
What Extended Support actually buys you
You buy time on a version whose general support has already closed. It adds no features, it does not move you towards vSphere 9 or VCF 9, and it changes nothing inside your environment. Meanwhile, the replacement in the catalogue for the small tier is vSphere Express, with its limits written down: 128 cores across all of your environments combined, a one-year subscription and one single order per end customer.
We have run the 128-core arithmetic before and it is worth repeating, because it catches people out: an ordinary cluster of three dual-socket nodes with 24 cores each adds up to 144 and is already over the line. If that is your case, the catalogue replacement falls short for you, and what the European extension gives you is time to find something else.
The European Economic Area is not "Europe"
The paragraph says "countries in the European Economic Area": the twenty-seven EU member states plus Iceland, Liechtenstein and Norway. It does not include the United Kingdom or Switzerland. A group with its parent company in Barcelona and a subsidiary in London or Zurich has, for the same family of clusters and the same vendor, two different calendars, and the subsidiary gets the short one.
What the paragraph does not say is how a split customer's country gets determined: whether it is the registered seat of the signing entity, the country of delivery, or the distributor issuing the invoice. We do not know either. If your group has companies on both sides of that border, that question goes to your distributor in writing before you sign anything, and you keep the answer.
Why this paragraph exists
Broadcom has not explained why. The reading of this as a concession to European regulatory pressure belongs to the analysts quoted in the trade press — The Register and Network World carry several along those lines — not to Broadcom and not to us, and we pass it on as such: it is the catalogue's only geographic exception, and it lands precisely in the jurisdiction where the company has faced the most pressure over its licensing changes. Michael Warrilow, an independent analyst quoted by The Register, sums up the practical effect: the extension "could provide them up to an extra 12 months to transition vSphere 8 to VCF 9 and/or migrate workloads to another platform".
What actually fits into 357 days
A year sounds like a lot until you divide it into real maintenance windows. This is how we divide it when we sit down with a management team to plan it:
- ·Week 1. Two numbers: physical cores across all your environments, and the exact subscription end date. Without those two numbers nothing can be decided.
- ·Month 1. Pick one of three exits, all three legitimate: renew in the EEA while the window is open, move into the new catalogue if you fit its limits, or change hypervisor. The fourth — reaching October 2027 without having chosen — is also a decision, but the calendar makes it for you.
- ·Months 2 to 4. If the exit is changing hypervisor, start with whatever hurts least, and with the way back written down before you touch anything: the rollback plan is the step almost nobody prepares.
- ·Months 5 to 10. The rest in layers, machine by machine, in windows you already have. The calendar of a VMware to Proxmox migration is set by the outages the business will give you and the testing you do before each one.
What does not fit into 357 days is starting in September 2027. Nobody is around in August, nobody touches production in December, and in our experience a trading company gets four or five maintenance windows a year.
When renewing is the right call
This is not a reason to migrate in a hurry. If you are under 128 cores, if vSphere works for you and if the number in your contract leaves you comfortable, renewing in the EEA while the window is open is a perfectly defensible decision, and we have found ourselves making that case more than once: we have migrated companies and we have also recommended staying on VMware when it made sense. We are not Proxmox resellers and we are not VMware resellers, and we sell licences for neither: what you pay us for is judgement and work.
Sources (verified on 2026-11-08): verbatim text of the European Economic Area paragraph, the 31 October 2027 and 31 October 2028 dates, the "the earlier of" clause, and the description of vSphere Express (128 cores and availability in all regions; the one-order-per-customer limit and the one-year subscription come from the distributor listings we documented in our 4 November post, not from this blog entry) — VMware Cloud Foundation blog post, 2026-11-04; End of General Support for vSphere 8.0 on 11 October 2027 covering vCenter Server 8.0, ESX 8.x and vSAN 8.x — Broadcom knowledge base article 459135; the discovery of the paragraph, the fact that the provision was missing from the materials shared with the press, and the quote from analyst Michael Warrilow — The Register, 2026-11-05; coverage of the same change and the regulatory reading — Network World, 2026-11-05. The 357 days, the 20-day gap between end of general support and the last day of sale, the three worked cases of the "whichever comes first" clause, the 144-core arithmetic and the month-by-month breakdown are our own work. The composition of the European Economic Area (the 27 EU member states plus Iceland, Liechtenstein and Norway) is public record. Broadcom has not published a reason for the European exception: the regulatory reading belongs to the outlets cited. Photograph: "388 King - server room", CC BY-SA 2.0 via Wikimedia Commons, cropped and brightened by us.
Do you know the date your vSphere subscription ends?
We count your cores, find that date in your contract and put the three exits on the table with what each one costs. If the best one is to renew, we will say so: we sell nobody's licences.
Talk to everyWAN
Microsoft 365
ES 
CAT 
EN