Last updated: November 16, 2026
Microsoft ends Dynamics GP support on December 31, 2029, and security updates and patches, if needed, on April 30, 2031. We found no Microsoft statement extending either date. The support date has moved once, from September 30, 2029.
TL;DR: Microsoft’s published dates for Dynamics GP are December 31, 2029 for support and April 30, 2031 for security updates, if needed. Nothing Microsoft has published extends either one. The support date has moved once before, by three months. Plan against the dates you can read today, and pick a direction by the end of 2027.
Somebody at your company has asked whether Microsoft will just extend GP again. Fair question. It’s also a shaky thing to build a finance plan on.
The honest answer comes in three parts. What Microsoft has published is short and specific. What it has changed before is documented. What it might do next is unknown, to us and to everyone else writing about this.
Argus Consulting Group is a Dynamics GP partner in Pasadena, founded in 1989, with GP experience since 1993. We support GP, host it, and migrate clients to Business Central when they’re ready. So we have a view, and we’ll say where it comes from. This post covers the dates, the one time they moved, what the end date does and doesn’t mean for payroll and year-end, and a planning sequence you can hand to a controller or president.
What Has Microsoft Actually Announced About GP Support Dates?
Microsoft’s notice on Microsoft Learn says it will “end Dynamics GP support on December 31, 2029” for “product enhancements, regulatory (tax) updates, and technical support,” and that “security updates and patches, if needed, will be available until April 30, 2031.”
Read the second date carefully. April 2031 covers security updates only. The notice doesn’t say tax or regulatory updates continue past 2029.
| Date | What happens | Where it comes from |
|---|---|---|
| April 1, 2026 | Last day for new customers to license GP subscriptions (already passed) | Microsoft Dynamics 365 blog |
| October 2029 | Final GP release, version 18.12 | Dynamics Communities, reporting Microsoft’s January 2025 update |
| December 2029 | Last year-end tax update, including payroll taxes for January 2030 in the US and Canada | Same Dynamics Communities article |
| December 31, 2029 | Enhancements, tax updates, and technical support end | Microsoft Learn |
| April 30, 2031 | Security updates and patches, if needed, end. Subscription use is expected to end around the same time | Microsoft Learn, plus the Microsoft Dynamics 365 blog |
Two rows rest on secondary sources. The 18.12 final release and the 2029 year-end tax update come from a Dynamics Communities article summarizing Microsoft’s January 15, 2025 announcement, and the Microsoft Dynamics 365 blog post on subscription use is undated. Confirm both against Microsoft’s current pages and licensing FAQ before you plan around them.
Microsoft’s lifecycle page also says GP is under the Modern Lifecycle Policy. Under that policy, customers stay current by taking at least one of the three all-inclusive updates released each year, typically in June, October, and December. Falling behind on updates is a separate risk from the 2029 date, and it starts sooner.
Has Microsoft Moved the GP End Date Before?
Yes, once. Microsoft announced September 30, 2029 on September 25, 2024. Customers and partners then met with Mike Morton, Microsoft’s VP of Dynamics 365 Business Central and SMB, at Community Summit NA 2024 in San Antonio and raised concerns about it.
On January 15, 2025, Microsoft moved the date to December 31, 2029 and left the security date alone, according to Dynamics Communities. That article doesn’t say the meetings caused the change. MSDynamicsWorld reports the reason Microsoft gave, which is that the new date lets GP customers meet their payroll and tax obligations for the full year.
Our reading, and not Microsoft’s, is that the move was three months long and tied to payroll, which looks like a fix for a specific tax-year problem and not a change of heart about GP’s future, though only Microsoft can say what it was thinking. The same January 2025 update also called its own dates potentially subject to change, so nobody should treat them as carved in stone either.
Is Microsoft Considering Support Past 2029?
Nothing we found says so.
We checked Microsoft’s notice and lifecycle pages. We checked the Product Roadmap General Session page recorded at Community Summit NA 2025, which says only that GP support continues through 2029. We checked the Summit NA 2026 program page, which has no lifecycle statement. A recap of Summit 2026 from a Dynamics partner lists the same two Microsoft dates and says outright that they aren’t new announcements.
If you’ve heard that Microsoft is weighing more time, ask where it was said. A dated Microsoft page counts. A conference hallway doesn’t.
None of this means an extension is impossible. It means you can’t schedule around one.

What Happens to GP After December 31, 2029?
The software keeps running. That part is simple.
Microsoft’s FAQ, as quoted by Dynamics Communities in September 2024, said customers with a perpetual license “may continue using their licensed solution beyond its end of support date.” For subscriptions it said continued use “will be reviewed and may change.” A later Microsoft blog post says subscription use is expected to end around April 30, 2031, and that additional perpetual users can’t be added to existing systems after that date. Check which license you hold, perpetual or subscription, with your licensing reseller.
What stops is the maintenance. Tax and regulatory updates are the one that touches finance first. Our post on payroll tax updates after Dynamics GP end of life goes deeper on payroll.
Think about a rule that changed this year. For payments made in 2026, the IRS now says to report nonemployee compensation of $2,000 or more, up from $600. Somebody had to build that into the forms, and we covered the GP side in our 1099 threshold post. After 2029, Microsoft stops building changes like that for GP. Whether a payroll provider, an add-on vendor, or a partner fills the gap depends on each of them, and Microsoft’s notice doesn’t speak to it. Ask each one, in writing.
The security promise is worded “if needed,” which we read as a backstop and not a patch schedule, and since Microsoft decides what counts as needed, nobody outside Microsoft can tell you in advance which issues would get a fix before April 2031.
What Should a Finance Lead Decide, and By When?
These checkpoints are our planning suggestions. Nothing in Microsoft’s notice requires them. They exist so that no single year holds a platform decision, a migration, and a year-end close all at once.
- By spring 2027, take inventory. Write down your GP version and build, your add-ons, your integrations, your payroll provider, where it’s hosted, and who actually knows how it works. Ask each add-on vendor and payroll provider what they support after December 2029.
- By the end of 2027, pick a direction. Stay and optimize, host in the cloud, or plan a move to Business Central. A lean is enough. It doesn’t have to be a contract.
- During 2028, schedule the work. If you’re migrating, scope it and set a date away from year-end. Microsoft’s own migration outline has four phases, from preparation through data replication and a data upgrade to Business Central online, and it says a full cloud migration takes time.
- In 2029, close it out. The final GP release is due in October and the last tax update in December. Settle how January 2030 payroll and the 2030 filings get handled.
- In 2030 and 2031, if you’re staying, you’re running without Microsoft enhancements, tax updates, or technical support. Security updates arrive only if Microsoft decides they’re needed, and only until April 30, 2031.
Starting in 2027 leaves room to wait for the right quarter. Starting in 2029 usually doesn’t.

What Are Your Options Before 2029?
Three, and they aren’t exclusive.
Stay and optimize. Keep taking the yearly updates, and use more of the system you already own. That’s the case for GP optimization, and it’s often the cheapest first step because the answer might be configuration and not a new platform. At Community Summit NA 2026, 40 of the 55 GP sessions sat in the organizer’s “getting more out of GP” path, and 15 in “planning your next move,” per the program page. People are doing both.
Host it. Cloud hosting changes where GP runs and who maintains the servers. It doesn’t change Microsoft’s support dates.
Migrate when you’re ready. Microsoft’s lifecycle page links to a guide for moving GP data to Business Central online, and the path is real. Argus handles GP-to-Business Central migration too, on your timeline and not under pressure.
We sell GP support and Business Central migration, so weigh our view with that in mind. If you’ve already picked a Business Central date and you trust your partner’s plan for it, you don’t need a second opinion from us.
What Wouldn’t an Extension Fix?
Even if Microsoft pushed the date out, several clocks would keep running.
SQL Server 2016 support ended July 14, 2026, according to Dynamics Communities, and Windows Server 2016 extended support ends in January 2027, per Microsoft’s lifecycle page. Those belong to other products. Your add-on vendors and payroll provider set their own timelines too, and each of them will have to decide separately what supporting GP means after December 2029, whatever Microsoft does with its own date. Tax rules change every year no matter whose software you run.
And if one person holds the whole system in their head, that risk doesn’t depend on any Microsoft date. Our version history page is a quick way to place your release, and a GP support partner can cover the knowledge gap.
What Is the Argus 10-Year Commitment?
It’s our pledge to support Dynamics GP through 2036. That’s seven years past Microsoft’s December 2029 date and five years past April 2031. Read more in our post on the Argus 10-Year Commitment.
It doesn’t change Microsoft’s calendar, and we won’t pretend it does. It means that if you choose to stay on GP, you’ll have a partner to call. Plan, don’t panic. We’d rather you decide on your own timeline than ours.
What the commitment covers once Microsoft’s last tax update ships needs a precise answer, and we haven’t published one.
If you’d like a second set of eyes on where you stand, a free assessment lays out stay, optimize, or migrate with honest pros and cons, or call (626) 403-9744.
Questions Finance Teams Ask About the 2029 Date
Will Microsoft extend Dynamics GP support past 2029?
Nothing Microsoft has published says so. The only change on record is the three-month move from September 30 to December 31, 2029, announced January 15, 2025. Treat anything beyond that as unconfirmed until a dated Microsoft page says otherwise.
Does GP stop working on January 1, 2030?
No. Microsoft’s FAQ, as quoted in September 2024, said perpetual license holders may keep using the software past the end of support. Support is what ends, meaning enhancements, tax updates, and technical help from Microsoft.
When is the last Dynamics GP tax update?
December 2029, according to the timeline table in Dynamics Communities’ report on Microsoft’s January 2025 update, which also says Microsoft will provide year-end tax updates for 2029, including payroll taxes needed for January 2030 in the US and Canada. Confirm it on Microsoft’s own page before you plan payroll around it.
Can we keep using GP after April 2031?
Depends on the license. Perpetual holders can keep running the software, per Microsoft’s FAQ as quoted in 2024, but additional perpetual users can’t be added to existing systems after April 30, 2031, and subscription use is expected to end around then. Check your agreement, because the answer lives in the contract and not in this post.
Is Business Central the only place to go?
No. It’s the path Microsoft documents, and its lifecycle page links to a data migration guide for it. Argus works with GP and Business Central, so we won’t advise on other systems.
Should we wait for Microsoft to say more before planning?
No. Microsoft says a full cloud migration takes time, and a plan costs nothing until you act on it. If an extension arrives, you’ll have lost nothing by knowing your add-ons, your payroll provider, and your direction. If it doesn’t, you’ll be glad you started in 2027.