web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Tracking code deployments from TFS/DevOps to Production for SOX purposes

(0) ShareShare
ReportReport
Posted on by

We're an AX 2012 customer that does a fair amount of code customization and we recently became a publicly traded company so are in need of meeting SOX requirements.  We're walking through our Change Management (CM) control and are having a big issue meeting it because there is no direct link between code check-ins to DevOps and what gets pushed into Production.

Our code development process is the following:

1)  Developers make changes on their dev boxes and code changes are checked into DevOps.

2)  We run a period code-build process on a dedicated AX build server which pulls in all DevOps changes and final output is an AX modelstore file.

3)  Modelstore file is promoted to a Test AX environment where user validation occurs.

4)  Once all validation has occurred, the modelstore file will get promoted into Production.

The issue we're running into with our auditors is that there isn't any kind of hard connection between DevOps and final code promotion into AX.  Wondering what other SOX required companies have done to handle this?

Also, what have you done when needing to push a hotfix (XPO) into Production?

I have the same question (0)
  • Suggested answer
    Dean Stegmiller Profile Picture
    Microsoft Employee on at

    Hi Swallman67,

    From the AX 2012 support perspective, I'm not aware of anything but hopefully someone in the community can assist.  One thought, is this more of a DevOps question vs AX?

    Ex. - https://devblogs.microsoft.com/buckh/using-branching-in-source-control-to-meet-sarbanes-oxley-requirements/ 

  • Martin Dráb Profile Picture
    239,519 Most Valuable Professional on at

    What kind of connection are you looking for? Would assinging a unique build number of the model satisfy your auditors?

    When somebody asks you tu push an .xpo to production, say "no". Kick of a build and deploy a model instead. If you want to use .xpo because you don't want to deploy all current changes, version control systems have a solution for you: branches.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 660

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 655 Super User 2026 Season 1

#3
CP04-islander Profile Picture

CP04-islander 557

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans