Forums

Hi,

we're currently customising AX to meet our business requirements.  We're implementing a single instance of AX which is to be accessed by multiple countries.  For each country we're working with a different partner (local to that country) to complete the development work for their requirements.  In order to work in this way, we need to give all developers access to a single instance of TFS, and to a single AX Team Server.

As we have different partners developing the code for us, and each partner/company's developers develop on their local machines, the development machines are on a different domain to TFS (in fact, they're in a completely different AD forest).  This means that when AX communicates with TFS, the credentials AX sends will not be the ones required by the TFS server. 

Were we to give all developers a machine on our network, we'd need to provision for 37 developers, meaning 37 machines capable of supporting an AOS and database, as well as sufferring potential network issues between the developer and their machine - so this feels like a worst case solution. 

 FYI: We're hoping to use a hosted instance of TFS, but regardless of whether this is hosted or on our company's network, it's still not on a different domain to the developers' machines.

Info on TFS2010 with AX2009 available here: http://daxmusings.blogspot.com/2010/08/dynamics-ax-2009-and-team-foundation.html

• Is there some way to map the AX credentials to the TFS credentials, such that myDomain\myUsername is translated to myTfsDomain\myTfsUsername before going to the server? 
• Has anyone out there worked with this sort of development environment previously?
• Would the Team Server need to be hosted on the same machine/domain as the TFS server, or can that be hosted anywhere so long as it's made accessible to all parties?

Thanks in advance,

JB