Skip to main content

Microsoft Dynamics AX 2012

Microsoft Dynamics AX 2012 at a glance
VendorMicrosoft
HeadquartersRedmond, Washington, USA
OwnershipMicrosoft Corporation (Nasdaq: MSFT)
DeploymentOn-premises (Windows Server/SQL Server, Application Object Server architecture)
Support statusFully end of life: mainstream support for AX 2012 R3 ended October 12, 2021; extended support ended January 10, 2023; no Microsoft patches of any kind since then (earlier AX versions exited support even sooner)
Target marketUpper mid-market and enterprise; remaining installed base only, product fully retired
IndustriesManufacturing, distribution, retail
PricingNo longer licensed or sold; remaining costs are infrastructure, administration, and third-party support
Websitelearn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/get-started/mainstream-support-ax-2009-2012

The short version

Microsoft Dynamics AX 2012 was Microsoft's enterprise ERP for manufacturing, distribution, and retail before the product line was rebuilt as part of Dynamics 365. Today it is fully out of support: extended support for the final R3 release ended on January 10, 2023, and no patches of any kind have shipped since. A substantial installed base keeps running it anyway, which is the reason this profile exists: as a migration source, not as a product anyone can order.

Company and product background

The lineage starts with Axapta, developed by the Danish vendor Damgaard and first released in 1998. Damgaard merged with Navision Software, Microsoft bought the combined company in 2002, and the product became Microsoft Dynamics AX. AX 2012 shipped in 2011; the R2 update followed, then the final R3 release in 2014 with warehouse and transportation management on board. Mainstream support for R3 ended October 12, 2021, extended support on January 10, 2023, and earlier AX versions had left support even sooner. The functional successor is the cloud pairing of Dynamics 365 Finance and Dynamics 365 Supply Chain Management, rebuilt from the AX code line starting in 2016.

Functional scope

Discrete, process, and lean manufacturing with MRP, supply chain and procurement management, warehouse and transportation management, retail and point-of-sale capabilities, and financials with multi-company and intercompany processing. The X++ development layer made deep customization the norm rather than the exception, and most surviving installations carry significant custom code plus third-party ISV modules. That accumulated customization is what turns every replacement into a substantial project.

Target market and industries

Built for upper-mid-market and enterprise organizations, often multi-site or multi-country, in manufacturing, distribution, and retail; in the United States it powered complex operational environments that competed head-on with SAP and Oracle installations. The audience that matters in 2026 is narrower: the remaining installed base planning its exit.

Licensing, hosting, cost

AX 2012 runs on customer-managed Windows Server, SQL Server, and Application Object Server infrastructure. Licenses are no longer sold. The remaining cost side consists of infrastructure, internal administration, and, at some companies, third-party support contracts standing in for the vendor. No published pricing exists because nothing is left to buy.

Our take

AX 2012 earns its place in this directory as a migration source, not as an option anyone can license; Microsoft stopped selling it, and since January 10, 2023 the code has received no patches of any kind. That changes what a profile like this is for. The question is not whether to run it but how long the remaining risk stays acceptable: an unpatched ERP shows up as a finding in security audits and cyber-insurance reviews, the surrounding Windows Server and SQL Server stack ages out alongside it, and the pool of X++ developers shrinks every year. On the exit side there are two well-trodden routes. Microsoft's data-upgrade path carries data and some configuration into Dynamics 365 Finance and Supply Chain Management, while heavily customized estates often choose re-implementation, because old X++ modifications rarely deserve to be rebuilt as extensions. Either way, data migration planning decides the timeline more than licensing questions do. Third-party support contracts can stretch the schedule; what they cannot do is restore security patches, so most companies use them to buy a defined number of months for the migration project.

What the Microsoft Dynamics AX 2012 website looks like

Current view of the vendor homepage, captured by our editorial team.

Screenshot of the Microsoft Dynamics AX 2012 vendor homepage

Comparable products

Related Topics

User reviews for Microsoft Dynamics AX 2012

No published reviews for Microsoft Dynamics AX 2012 on usa.erp-software.org yet.

Write the first review →

Share your experience with Microsoft Dynamics AX 2012

Reviews are checked editorially for plausibility before publication (usually 1–3 business days). Your email address is never published and is stored only as a hash. Fields marked * are required.

Frequently asked questions

Is Microsoft Dynamics AX 2012 still supported, and can we still buy or expand licenses?

Support is over on every front. Mainstream support for AX 2012 R3 ended October 12, 2021; extended support, which covered security fixes only, ended January 10, 2023; nothing has shipped since, for any AX 2012 version. Licenses are no longer sold, so there is no route in for new customers and no standard way to grow an existing estate. Companies holding licenses may keep running the software under their existing agreements, unsupported. License-term specifics belong with the Microsoft partner or licensing specialist managing the account.

How risky is it to keep running AX 2012 without support?

The risk curve bends upward rather than staying flat: every year without patches makes the system a softer target and a bigger finding in security audits, cyber-insurance reviews, and customer due diligence. Meanwhile the market for experienced AX administrators and developers thins out, most ISV vendors have redirected their roadmaps, and the Windows Server and SQL Server versions underneath eventually lose support too.

What are the realistic exit routes from AX 2012?

Three, roughly. Microsoft's data-upgrade path moves data and some configuration into Dynamics 365 Finance and Supply Chain Management. Heavily customized estates often re-implement instead, since X++ modifications must be rewritten as extensions and many are better replaced by standard functionality; custom-code volume, data quality, and how much the business has changed decide between the two. And some companies use the forced move to reopen the market entirely, weighing SAP S/4HANA, Oracle Fusion Cloud ERP, Infor CloudSuite products, or industry-specific systems. Whichever direction, this is a full implementation project, so a structured selection with clear requirements pays for itself.