Migration

Is it safe to keep running Dynamics AX 2012 after end of support?

Dynamics AX 2012 will keep running after end of support, but it is no longer safe as a permanent state. Microsoft ended extended support for AX 2012 R3 on 10 January 2023, and earlier versions lost it in April 2022, so no security fixes, hotfixes or regulatory updates have been released since. Dynamics AX end of life is not a single event: the risk grows every year as the servers, database and people around AX age with it. In 2026 the realistic answer is that AX can stay in production only as a controlled bridge, with compensating controls and a dated plan to move to Dynamics 365.

The question most finance and IT leaders ask is not whether AX still works, because it usually does. The better question is what the company is now carrying on its own that a vendor used to carry for it: security patching, tax and legal changes, compatibility with new operating systems, and the shrinking pool of consultants who know the platform. Each of those has a price, and the price rises faster than most budgets assume.

Key facts at a glance:

• Support status. AX 2009, AX 2012 and AX 2012 R2 left support in April 2022, and AX 2012 R3 on 10 January 2023.
• Infrastructure. SQL Server 2016, a common AX 2012 database, reached end of extended support on 14 July 2026, and Windows Server 2012 R2 in October 2023.
• Security. Without vendor patches, newly found vulnerabilities in AX or its stack stay open unless the company mitigates them itself.
• Compliance. Tax and statutory changes after 2023 must be built and maintained in house or by a partner, at the company's own risk.
• Safe use. Running AX is defensible only as a time limited bridge with isolation, monitoring and a documented, regularly reviewed risk acceptance.
• Best first step. An assessment of the AX environment shows the real exposure and the cheapest route to Dynamics 365 before any licence is bought.

‍

__wf_reserved_inherit

What does Dynamics AX end of life actually mean in 2026?

End of support removes three things at once. The first is security updates for the AX application itself, so any vulnerability discovered from 2023 onwards in AX code stays unpatched. The second is regulatory and statutory updates: changes to VAT reporting, electronic invoicing, payroll interfaces or audit file formats are no longer delivered by Microsoft and have to be built by the company or its partner. The third is less visible but often decisive: the components AX depends on are reaching their own end of life. Many AX 2012 installations run on SQL Server 2016, which lost extended support in July 2026 and now receives only critical fixes through a paid Extended Security Updates programme, as summarised in this overview of the SQL Server 2016 end of life.

The practical consequence is that the safety of AX is now determined by the weakest supported layer in the stack, not by AX alone. A company can isolate an application server, but it cannot easily isolate a database that every report, integration and month end process depends on. The table below shows where a typical AX 2012 estate stands today and what each status means for the business. Note that the list includes people as well as software, because the availability of AX skills now behaves like a support status of its own: it does not end on a fixed date, but it declines steadily and sets the cost of every change, incident and statutory update the company still has to make.

Component Support status What it means for the business
Dynamics AX 2009, AX 2012, AX 2012 R2 Out of support since April 2022 No security fixes, hotfixes or statutory updates for more than four years
Dynamics AX 2012 R3 Out of support since 10 January 2023 Same position, with the newest AX code base also frozen
Windows Server 2012 and 2012 R2 Out of extended support since 10 October 2023 Operating system vulnerabilities stay open unless paid updates are bought
SQL Server 2014 Out of extended support since July 2024 Database patches only through paid programmes, if at all
SQL Server 2016 Out of extended support since 14 July 2026 Critical fixes only, through paid Extended Security Updates until 2029
AX specialists on the market Shrinking every year Higher day rates and longer lead times for every change or incident

‍

Where does the risk of running AX 2012 really sit?

Security is the risk people name first, and it is real. The UK National Cyber Security Centre is blunt in its guidance on obsolete products: the only fully effective way to remove the risk is to stop using the obsolete product, and anything short of that is mitigation. An ERP system is a high value target because it holds supplier bank details, payment runs and customer data, and it is connected to banks, warehouses and e commerce platforms. A vulnerability that would be a nuisance on a file server can become a payment fraud route on an ERP.

Compliance is the second exposure, and it often arrives first. Auditors increasingly ask whether financially significant systems are supported, and an unsupported ERP tends to appear in management letters as a control weakness. Schemes such as Cyber Essentials expect in scope software to be licensed and supported, and cyber insurers ask similar questions at renewal. Tax change adds pressure from the other side: every new reporting rule must now be engineered into a frozen code base by people who know it, which is where the third risk appears. The consultants who built and maintained AX are moving to Dynamics 365, so each year the same fix costs more and takes longer. Companies rarely feel this until an urgent change, such as a new invoicing requirement, collides with the lack of available expertise.

‍

__wf_reserved_inherit

Which risks grow each year AX stays in production?

Not every risk grows at the same speed, and that matters for planning. Some exposures are flat once the right controls are in place: an AX environment that is properly segmented, has no direct internet exposure and is closely monitored does not become dramatically more dangerous month by month. Other exposures compound. The data volume in AX keeps growing, which makes the eventual data upgrade longer and more expensive. Every customisation added to cover a new requirement is another object that must later be refactored into the extension model. Every year of delay also narrows the choice of migration path, because older databases and heavily modified systems push companies towards a full reimplementation rather than a technical upgrade. The signals below are the ones we see most often in companies that waited too long:

• Rising change cost. Simple changes to AX take weeks because only one or two people can make them safely.
• Workarounds outside AX. New requirements are handled in spreadsheets or side systems because changing AX feels too risky.
• Audit findings. Management letters mention unsupported financial systems or missing patch evidence.
• Infrastructure lock. Servers cannot be upgraded because AX components would stop working on newer versions.
• Insurance questions. Cyber insurance renewals ask for a migration date or impose exclusions for unsupported systems.

When three or more of these appear together, the cost of staying on AX usually already exceeds the annualised cost of moving, even before a security incident is considered.

‍

What does staying on AX 2012 really cost?

Many business cases compare the cost of a Dynamics 365 project with a cost of zero for staying on AX. That comparison is wrong, because staying has a running cost that grows each year. It includes paid security updates for the database where they are available, the premium for scarce AX skills, hardware that cannot be refreshed without breaking compatibility, the effort of building every new tax or reporting requirement by hand, and the productivity lost in workarounds outside the system. There is also the cost that only appears after an incident: forensic work, downtime during a month end, and the reputational damage of a payment fraud or data breach traced to an unpatched system.

A more useful comparison sets the annual cost of staying against the annualised cost of moving. A midsize company typically finds that keeping AX safe for two more years, with isolation, monitoring, database security updates and in house compliance work, costs a meaningful share of a migration budget, while delivering nothing that lasts. Migration costs, by contrast, buy a supported platform with continuous updates, standard localisation and a wider pool of consultants. The point is not that every company must move tomorrow. It is that the decision should be made on real numbers, with the cost of delay included, rather than on the assumption that a system which still runs is free.

‍

How can a company run AX safely while it plans the move?

If AX must stay in production for another year or two, the goal is to make that period deliberate rather than accidental. The controls are well known: isolate the AX servers in their own network zone, remove direct internet access and email from those machines, restrict administrative access, keep an inventory of every integration that touches AX, and increase logging and monitoring so unusual activity is visible quickly. Where the database runs on SQL Server 2016, buying Extended Security Updates for the bridge period is usually cheaper than accepting unpatched critical vulnerabilities. Just as important is governance: the decision to keep AX should be written down as a risk acceptance, owned by a named executive, with a review date and a target migration date.

The options are not limited to staying or migrating at once. The table compares the realistic paths and when each makes sense. Most companies we speak to choose a stabilised bridge of 12 to 24 months combined with an assessment that settles the migration path early, so the bridge has a defined end. A bridge without an end date tends to become the default, and the controls that were meant to be temporary quietly turn into the operating model. Setting the date early also gives the business time to clean master data, retire unused customisations and close obsolete integrations while AX is still running, which shortens the migration itself and lowers its cost.

Option Typical horizon When it makes sense
Keep AX as is Not recommended Only for a system already being switched off within months
Stabilise and isolate AX as a bridge 12 to 24 months When a migration is planned and budgeted, with a named end date
Technical upgrade to Dynamics 365 6 to 12 months AX 2012 R2 or R3 with moderate customisation and valued history
Reimplementation with data migration 9 to 18 months Older versions, heavy customisation or a changed business model
Phased move by entity or process 12 to 24 months Groups that want to reduce risk by moving one company or area at a time

‍

How ANEGIS helps companies leave AX 2012

ANEGIS is a Microsoft Solutions Partner for Business Applications with 98 Dynamics 365 specialists and more than 170 experts across offices in Poland and the UK, and it has delivered more than five AX migrations. Its Dynamics AX to Dynamics 365 migration service starts with an environment assessment that answers the key question before any licence is bought: a technical upgrade that preserves the full transaction history, or a reimplementation with data migration. The same assessment documents the current exposure of the AX estate, so the bridge period can be secured properly while the project is prepared.

For BUUK Infrastructure, the UK provider of last mile utility networks, ANEGIS acted as AX partner for more than ten years and then moved the company to Dynamics 365 in the cloud before AX support had expired. Analysis started in November 2021, the implementation took 14 months, the system went live on 3 July 2023, and the ANEGIS support team took over after a two month stabilisation phase. BUUK decided to move early precisely because the lack of security updates and new functionality had become a compliance and data protection risk. ANEGIS also knows AX from the inside: it implemented Dynamics AX for the headquarters of WPP, the world's largest marketing communications group, which is why its migration teams understand both the code they are replacing and the platform they are moving to.

Know your AX exposure before it becomes urgent

An honest view of how exposed your AX 2012 environment is today costs far less than an emergency migration. Contact ANEGIS to book a free consultation or an assessment of your Dynamics AX environment.

‍

FAQs

Is Dynamics AX 2012 still supported by Microsoft?

No. AX 2009, AX 2012 and AX 2012 R2 left support in April 2022, and AX 2012 R3 on 10 January 2023. Since then Microsoft has released no security fixes, hotfixes or regulatory updates for any AX version.

Can we buy extended security updates for AX 2012?

Not for AX itself. Paid Extended Security Updates exist for some underlying components, such as SQL Server 2016 until 2029, but they cover only critical database fixes and do nothing for the AX application or its statutory features.

How long can we safely keep AX 2012 running?

Treat it as a bridge of roughly 12 to 24 months with isolation, monitoring and a documented risk acceptance. Beyond that, rising change costs and infrastructure limits usually outweigh the cost of migrating to Dynamics 365.

Is third party support a good alternative to migrating?

It can cover break and fix issues and some tax changes for a period, but it cannot restore vendor security patches or modern platform features. Most companies use it, if at all, only to bridge the time until migration.

Where should we start if AX is still our ERP?

Start with an assessment of the AX environment: version, customisations, integrations, data volume and infrastructure. It shows the real risk today and whether a technical upgrade or a reimplementation is the cheaper route.

See more

Migration

Which company is best at migrating Dynamics AX to Dynamics 365? 8 partners compared

Read article
Text Link
Migration

Dynamics AX to Dynamics 365 migration cost: what drives the price

Read article
Text Link
Dynamics 365 F&O

What is a fit gap analysis in Dynamics 365 Finance and Operations, and do we need one?

Read article
Text Link
Back to all

Looking for a Microsoft partner? Let's talk about your project

Work with a team that has delivered implementations and projects for dozens of companies. Schedule an introductory call and see:

How to tailor Dynamics 365 to your company's processes, rather than the other way around

Which areas are worth automating to save time and reduce costs

Here is the step-by-step implementation process with Anegis: from analysis to post-launch support

Select a meeting time
Thank you for your message!
Oops! Something went wrong while submitting the form.
Microsoft AI Builder
No items found.
No items found.
No items found.