As part of the Microsoft Dynamics 365 application life cycle, every implementation should include separate Microsoft Dynamics AX environments. So that you can reliably manage changes and customizations, and control what code ends up running on the production system.
The Microsoft Dynamics 365 application life cycle relies on the following environments:
Development environments – Microsoft Dynamics 365 development environments typically consist of multiple developers and multiple computers. Development environments are typical of independent software vendors (ISV) and Microsoft partners working on large implementations.
Test environment – A test environment is an environment where Microsoft Dynamics 365 customizations and solutions, possibly from different vendors, are deployed, integrated, and tested.
Staging or pre-production environment – A staging environment is an environment that is built based on the production environment and typically contains business data from the production system. Microsoft Dynamics 365 models and customizations are moved to a staging environment after they have been integrated and tested on a test environment. Typically, end users test and RnD on staging environment.
Production environment – A production environment is the final environment that customers are using to run their business.
No comments:
Post a Comment