Skype for Business end of life: the clock stops in October 2026.

At a glance

Skype for Business lifecycle dates

Four different products have carried the Skype name, and quotes, tickets, and internal wikis mix them up constantly. These are the dates that actually govern each one.

Primary sources: the Microsoft Skype for Business blog posts announcing ESU Period 2 and the reminder that the ESU program ends in October 2026; Skype for Business Server Subscription Edition availability; and Microsoft's consumer Skype retirement notice. Entitlements and ESU pricing vary by agreement — confirm yours with your Microsoft account team.

Naming decoder

Which Skype for Business do you actually have?

Before anything else, establish which product is in your building. The migration conversation is completely different for each, and a surprising number of organizations discover mid-project that they were talking about the wrong one.

The distinction that matters most: Subscription Edition is a real on-premises option, not a rebrand of Teams. If your reason for running Skype for Business on premises was regulatory, sovereignty, or a hard dependency on local call control, SE keeps that architecture available rather than forcing a cloud move. It is also not a free pass — it requires current licensing with active Software Assurance or subscription licences, and it expects you to stay current rather than freeze on a version for six years.

Read the fine print

What the ESU program does and does not buy

The Extended Security Update program is the most misunderstood part of this lifecycle, and misreading it is how an estate ends up genuinely exposed while believing it is covered.

• It is security updates only. No bug fixes, no feature work, and no ability to open technical support cases. The servers are out of support; you are buying patches, not a support contract.
• Period 2 must be purchased separately. Buying Period 1 did not roll you into Period 2, and you did not need Period 1 to buy Period 2. It is a fresh purchase through your Microsoft account team covering May 2026 through October 2026.
• There is no Period 3. Microsoft has stated the program ends with Period 2 — after October 2026 there are no further updates, including for customers who paid.
• Coverage is not automatic. If nobody actively bought Period 2, your servers have been receiving no security updates since April 2026, regardless of what the deployment looks like from the inside.

That last point deserves a direct check rather than an assumption. Several months of monthly bulletins have already passed with no updates issued for unenrolled servers. The practical action this week is to confirm with whoever owns the Microsoft agreement whether Period 2 was actually purchased — and if it was not, to treat the estate as unpatched and prioritise accordingly.

The part that complicates everything

If a contact center sits on top of it

Skype for Business never shipped a real contact center. What it shipped was Response Groups — basic hunt groups with queues and simple routing — and for a great many organizations that was genuinely enough for a help desk or a small service line. Everyone who needed more bought a third-party platform that plugged into Skype for Business for call control, from vendors such as Enghouse, Luware, ComputerTalk, and Competella.

Both situations create work that the server migration plan usually underestimates:

• Response Groups do not migrate. There is no export that lands them in a new platform. Queues, agent groups, business hours, and announcements get rebuilt by hand — which is an opportunity to fix routing that grew organically, but it is a project task, not a checkbox.
• Your third-party contact center has its own lifecycle. The vendors in this space have moved their products to Teams, and the Skype for Business versions are on their own end-of-support tracks. Ask your vendor for their dates in writing before you plan around them — a Teams migration may be bundled into an upgrade you are entitled to, or it may be a new purchase.
• Recording, wallboards, and CRM integration are separate again. Anything hooked into Skype for Business call control through the UCMA or Trusted Application model needs an equivalent on the destination platform, and the equivalents are rarely one-to-one.
• Enterprise Voice and the PSTN edge come too. Mediation servers, SBCs, gateways, and analog endpoints all belong to this project. If your SBC is also aging, the two refreshes are worth scoping together.

This is the moment where the contact center should stop being a footnote in a server migration. The queues are customer-facing revenue and reputation; the servers are infrastructure. Scoping them as one project reliably underweights the harder half.

Decision point

Three realistic paths off Skype for Business Server

The third option is worth more attention than it usually gets. Employee calling and customer-service routing have different requirements, different buyers, and different upgrade economics, and there is no technical rule that they land on the same platform. Splitting them also preserves negotiating leverage: a vendor bidding for half your estate competes harder than one that assumes it keeps all of it.

If Teams is the destination, the real question is which contact-center model you attach to it — Microsoft's native offering, an Extend partner that runs inside Teams, or a full CCaaS platform connected to it. Those three models price and behave very differently, and our Microsoft Teams contact center guide breaks down which fits which kind of operation.

Work backward from the date

Planning backward from October 2026

Be honest about the runway. A full Skype for Business Server migration with a contact center attached typically runs nine to eighteen months for a multi-site estate, and three to six months for a small single-site deployment. From August 2026, most organizations cannot finish before the ESU program closes — and that is a scheduling fact, not a reason to rush the platform decision.

• Now: confirm ESU Period 2 status. Either you are covered to the end of October 2026 or you have been unpatched since April. This single question changes how urgent everything else is.
• Now: inventory the edge. Which servers are internet-facing, what they terminate, and what compensating controls you can put in front of them if the migration lands after October.
• Next 1–2 months: decide the destination. Subscription Edition, Teams Phone, or a split. Discovery and shortlisting, with demos against your real call flows rather than the vendor's.
• Months 2–5: contracts and build. Procurement and security review reliably consume a quarter on their own. Then design sign-off, call-flow rebuild, and pilot groups.
• Months 5–9+: migrate in waves. Number porting is the least compressible step; large DID inventories move in waves and rejections reset the clock. Keep the old platform live until every wave confirms.

If the project will clearly land past October 2026, plan the gap deliberately: buy the Period 2 cover you are entitled to, isolate or front the edge servers, document the accepted risk for your security team, and put a date on the far side. Running past the end of updates is a defensible decision with a funded plan and a defined window. It is only a problem when it happens by default.

Budget lines

Cost factors beyond the licence

Whichever direction you choose, the licence is rarely the largest line. The items that move a budget:

• Contact-center rebuild. Response Groups, queues, announcements, and reporting do not port. Budget it as a project.
• Third-party contact-center licensing. The Teams version of your existing platform may be an entitled upgrade or a new purchase — the difference is material, and only your vendor can tell you which.
• PSTN and carrier work. Porting DIDs and toll-free numbers, replacing SIP trunks or moving to Operator Connect or Direct Routing, and unwinding legacy contracts; check early-termination clauses before you set a date.
• SBC and gateway refresh. Often due at the same time, and cheaper to scope alongside the migration than as a separate project a year later.
• Analog and life-safety. Elevators, alarms, paging, and fax hanging off the old voice estate. Every one needs a documented replacement, and E911 dispatchable-location requirements need re-establishing on the new platform.
• Parallel operation. Weeks or months of running both platforms — double licensing, double administration — while users and queues move in waves.
• Training and change management. Rarely itemized in a quote, always paid for in lost productivity if skipped.

For the customer-facing side, contact-center seats cluster between $65 and $200 per agent per month depending on channels and AI; our CCaaS pricing guide breaks down the tiers, and the contact center AI guide covers the line item growing fastest on 2026 quotes. Employee calling seats price well below agent seats, which is part of why splitting the two decisions usually saves money. Start with a quick estimate of your seat mix.

Two shortlists

The Microsoft-aligned path vs a vendor-neutral shortlist

The Microsoft-aligned path. If the organization already runs Microsoft 365, Teams Phone is the shortest line: licensing you partly own, an identity and compliance story your security team has already approved, and admin teams who do not start from zero. Attach a contact center using one of the three models in our Teams contact center guide and price the stacked licences honestly — Teams Phone plus a PSTN option plus a contact-center layer is three lines, not one.

The vendor-neutral shortlist. A forced migration is the cheapest moment you will ever have to test the market, because the switching cost is being paid either way. Dedicated CCaaS platforms such as Five9, Genesys Cloud, NICE CXone, and Talkdesk generally out-feature UC-attached routing, and several integrate with Teams so employee calling can stay Microsoft. Healthcare estates should start with the Epic integration guide; public sector buyers with the FedRAMP guide. If Skype for Business is only part of an aging estate, the PBX end-of-life hub covers the rest. New to the category? Start with what CCaaS is.

FAQ

Quick answers

Related guides