Argus Consulting Group, USA info@arguscg.com 800-274-8791

Dynamics GP on Windows Server 2016? The Platform Dates That Arrive Before 2029

Last updated: November 17, 2026

Windows Server 2016 reaches end of support on January 12, 2027, and SQL Server 2016 already has. Dynamics GP is supported until December 31, 2029, so the platform under your financial system runs out of support first.

TL;DR: The software under Dynamics GP runs out of support before GP does. SQL Server 2016 support ended July 14, 2026, and Windows Server 2016 follows on January 12, 2027. List your versions, match them to your GP build, and ask whoever runs your servers for a written plan.

Microsoft’s date for GP itself is the one everybody knows. December 31, 2029. The dates under it get far less attention, and two of them have already arrived or are about to.

SQL Server 2016 lost extended support on July 14, 2026. Windows Server 2016 follows on January 12, 2027. Nothing shuts off on those days. Your books keep posting. What stops is Microsoft publishing security updates for the server and the database, while GP still has more than three years of support left.

This post is a calendar and a question list for a finance lead without an IT department. It covers the server side only. Moving to a newer GP release is a separate job, and Argus keeps a GP version history page if you need to place your build.

Argus Consulting Group is a Dynamics GP partner in Pasadena, founded in 1989, with GP experience since 1993. We host GP in the cloud, so this topic sits close to our work.

What Dates Sit Under Dynamics GP’s 2029 End of Support?

Seven dates matter for a GP environment, and four of them land before GP’s own December 31, 2029. Here they are, with where each one comes from.

Date What happens Source
July 14, 2026 SQL Server 2016 extended support ends. Paid ESU years begin July 15. Microsoft lifecycle
January 12, 2027 Windows Server 2016 extended support ends Microsoft Windows Server blog
October 2027 SQL Server 2017 security support ends itechtics tracker
January 9, 2029 Windows Server 2019 end of support Microsoft, 2029 end-of-support list
December 31, 2029 Dynamics GP support ends Microsoft, 2029 end-of-support list
January 2030 SQL Server 2019 extended support ends Microsoft lifecycle
April 30, 2031 GP security-only patches end Dynamics Communities, Sept. 18, 2026

Read the table sideways and a pattern shows up. Windows Server 2019 ends nearly a year before GP’s last supported day. SQL Server 2019 ends a few days after it. GP’s security-only patches then run to April 30, 2031, and the first versions that outlast that date are Windows Server 2022 and SQL Server 2022, going by third-party trackers that list October 2031 and January 2033. The SQL Server 2017 date and both 2022 dates come from a third-party tracker, so confirm them on Microsoft’s lifecycle pages.

A 2019-era platform isn’t wrong. It’s a stop on the road, and a destination only if your plan ends before 2029. Staying on GP past that is a legitimate plan. The servers just have to be able to carry it.

Blank wall calendar with a brass pin in a bright office, representing the platform end-of-support dates that arrive before Dynamics GP's 2029 date

Which SQL Server and Windows Server Versions Does Each GP Release Support?

Microsoft’s system requirements page answers this release by release, and SQL Server support narrows with each one. A company on SQL Server 2016 can’t run GP 18.7 or later.

GP release SQL Server versions supported
18.5 and later 2022, 2019, 2017, 2016
18.7 and later 2022, 2019, 2017
18.8 (build 18.8.1941, January 2026 hotfix) and later 2025, 2022, 2019, 2017
18.9 and later 2025, 2022, 2019

The 18.8 row carries a build number because SQL Server 2025 support arrived with that January 2026 hotfix. And 18.9 drops SQL Server 2017, going by the page’s summary lines. The detailed tables on the same page stop at 18.8.1941, so confirm it with your partner before you plan around it.

Windows Server works differently on that page. It gives minimum GP builds instead of release ranges.

  • Windows Server 2022 needs GP 18.5.1556 or later.
  • Windows Server 2025 needs GP 18.7.1756 or later.

Two notes on the same page matter if you’re choosing where to land. Since GP 18.8 and its move to TLS 1.3, Microsoft says some Web Client issues may occur on Windows Server 2016, and it strongly recommends a newer version. Another note says VBA isn’t supported on Windows Server 2019. If your company runs customizations written in VBA, ask whether that applies to you before you pick 2019 as the landing spot. The page states the VBA note for 2019 only, so ask your partner about 2022 and 2025 too.

Is Windows Server 2016 a Problem for Dynamics GP Today?

It depends on how your team signs in. Microsoft’s wording is “some Web Client issues may occur,” which isn’t the same as every shop having them. If your remote workers use the Web Client and nobody has reported trouble, that’s good news worth writing down. It isn’t a plan.

The plan starts on January 12, 2027. After that date Microsoft stops publishing security updates for Windows Server 2016 unless you buy extended security updates, which are covered below. The software keeps running. It just stops getting patched, on a server that likely holds your financial data.

What Are Your Options if You’re Still on SQL Server 2016 or Windows Server 2016?

There are four, and none of them requires a decision this week.

Option What it is What to confirm
Move to a newer version Build or restore onto Windows Server 2022 or 2025 and SQL Server 2022 or 2025, keeping GP as it is when your build meets the minimums Your GP build against the tables above
Buy extended security updates (ESU) SQL Server 2016 has three yearly ESU periods, July 15, 2026 through July 2029. Windows Server 2016 ESU was announced and is delivered through Azure Arc. Price, who buys it, and how long it covers
Move to a hosted environment A hosting partner runs the servers and keeps them current Which versions they run today, in writing
Decide later, on purpose Stay on 2016 for a defined stretch, with a named person who accepted the risk The date you’ll decide, and who owns it

ESU buys time. It doesn’t change the version underneath. Microsoft’s SQL Server 2016 lifecycle page lists the ESU dates but not prices. One blogger reports year-one pricing at 75% of the license price, rising to 150% and 300% in years two and three, though commenters on another post couldn’t find those figures on Microsoft’s pages. The source for those percentages is a personal blog, so confirm SQL Server 2016 ESU pricing with Microsoft or your licensing partner.

Microsoft announced Windows Server 2016 ESU in a post dated February 25, 2026. It names Azure Arc as the delivery route and doesn’t state prices, so ask your licensing partner for pricing, eligibility, and term.

What Does a Platform Move Ask of Dynamics GP?

Less than people expect, if your GP build already meets the minimums. A Dynamics Communities post from September 18, 2026 describes the database engine and the operating system as moves that can be done as a rehost leaving GP itself untouched. It also says to keep GP current, because newer builds keep newer platform options open.

On the database side, Microsoft’s SQL Server 2022 upgrade page lists SQL Server 2016 SP3 or later among the versions you can upgrade from, and GP supports SQL Server 2022 starting with release 18.5. Whether an in-place upgrade or a move to a new server fits your environment is a question for whoever does the work.

The move still touches everything that sits on the platform, including add-on products, integrations, modified dictionaries, VBA customizations, and Web Client. Run the kind of finance test you’d run for any change. Post a journal entry and reverse it. Take a payables batch through to a printed check. Compare Management Reporter totals to production.

What the move doesn’t ask of you is a decision about Business Central. The platform and the stay-or-move question run on separate clocks, and Business Central migration can wait for its own timeline.

What Should You Ask Your Hosting Provider or IT Contact?

Send these in one email and ask for written answers with names and dates.

  • Which Windows Server and SQL Server versions run GP today, in every environment, including test?
  • What’s the end-of-support date for each, and when do you plan to move?
  • Is anyone paying for extended security updates, and for how long?
  • What GP build are we on, and does it meet the minimum for the version you’re moving to?
  • Who tests after the move, and what does finance sign off on?
  • What’s the rollback if the move goes wrong?

A provider who can answer the first question in one reply is a good sign. Slow answers are information too.

Finance lead taking notes in a navy notebook during a call with a hosting provider about Dynamics GP server versions

When Do You Not Need Anything From Argus?

If your servers already run Windows Server 2022 or 2025 and SQL Server 2022 or 2025, your GP build meets the minimums in the tables above, and whoever runs them has said so in writing, you’re done. Put the dates on a calendar.

Argus hosts GP in the cloud, so we’d say cloud hosting is one option for everyone else. It sits beside the other rows in the table, and the best fit depends on who runs your servers today.

Argus has also committed to supporting Dynamics GP through 2036, seven years past Microsoft’s date, so a platform fix on GP isn’t a dead end. Read more on the Argus 10-Year Commitment. We lay out options and you decide.

What Does a One-Page Platform Inventory Look Like?

The Dynamics Communities post recommends a single document that lists every layer under GP with its end-of-support date and an owner, reviewed a few times a year. Here’s a starting version. Fill in the second column this week.

Layer Version in use End of support Owner
Dynamics GP build   December 31, 2029 (security-only patches to April 30, 2031)  
SQL Server   Look up for your version  
Windows Server   Look up for your version  
.NET runtimes   Look up for your version  
Add-on products   Ask each vendor  

Two rows, the SQL Server version and the Windows Server version, will answer the bulk of your questions on their own.

If you’d like a second set of eyes on the inventory before you pick a path, start with a free assessment, or call (626) 403-9744. It covers your whole GP setup, and the options include staying exactly where you are.

Questions About GP and Server Support Dates

Does GP stop working on Windows Server 2016 in January 2027?

No. January 12, 2027 is the date Microsoft stops publishing security updates for Windows Server 2016 unless you buy extended security updates, and nothing about that date switches a server off. Separately, Microsoft warns that some Web Client issues may occur on 2016 since GP 18.8, so a newer version is the better landing spot either way.

Can we keep running SQL Server 2016 with extended security updates?

For a while. Microsoft’s lifecycle page lists three yearly ESU periods, from July 15, 2026 through July 2029, but it doesn’t list prices or eligibility. Get a quote from your licensing partner before you count on it, and remember that GP 18.7 and later don’t support SQL Server 2016 at all, so ESU also keeps you off newer GP releases.

Which SQL Server version should we move to?

Pick from what your GP build supports. SQL Server 2022 works from GP 18.5 on, and SQL Server 2025 from build 18.8.1941, and both are listed for 18.9. Since GP’s security-only patches run to April 30, 2031, it’s worth choosing a version that outlasts that date. Third-party trackers put SQL Server 2022 at January 2033, which clears it, but check Microsoft’s own page before you commit. Your partner or IT contact can also tell you whether edition and licensing change anything on your side.

Do we have to upgrade GP to change servers?

Not always. If your build already meets the minimums, Windows Server 2022 at 18.5.1556 or later, Windows Server 2025 at 18.7.1756 or later, the server can change without a GP upgrade. If it doesn’t, the upgrade comes first or alongside.

If a hosting provider runs our servers, whose job is this?

Theirs to track and yours to ask about. The provider owns the versions and the patching, but you own the risk to your financial data, so ask for the dates and a plan in writing.

Does moving the platform change GP’s 2029 date?

No. Microsoft lists December 31, 2029 as the end of GP support no matter what SQL Server and Windows Server sit underneath.

Back to all articles

Let’s Start With a Free Assessment.
$1,500 Value. No Cost.