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 :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Automated deployment p...
Finance | Project Operations, Human Resources, ...
Unanswered

Automated deployment process

(0) ShareShare
ReportReport
Posted on by CU10121822-0 1,076

Hi team,

I trying to understand the automated deployment process. What I understood…

For example - DEV to UAT deployment 

 

 

1. When the developer checked in the code in VS , it goes to Azure DevOps repository.

 

 

2. Now the developer pushes or merges code into the target branch, So, here the source branch is DEV and the target branch is UAT. Once the merging process completed the CI pipeline runs automatically.

And it will generates a deployable package containing the compiled customizations.

 

3. Now the release pipeline takes the deployable package from CI (Artifacts) and deploys it to the selected environment (UAT).

 

Once deployment is completed in UAT, Then proper validation and testing is required before proceed to PROD.

 

Am I correct?

 

Pls advise thanks 

Categories:
Dynamics 365 Finance
  • Martin Dráb Profile Picture
    Martin Dráb 240,837 Most Valuable Professional on at
    1.  Yes, using Azure DevOps is the usual scenario (but necessary, e.g. some teams use GitHub).
    2. There are different possible branching strategies, but in general developers check-in code to some kind of a development branch. Code gets propagated to a branch used for user-acceptance testing (UAT) only after it was successfully tested internally. A build might start automatically if configured that way, which isn't always the case. You might, for example, build and release UAT code just once a day during the night.
    3. It depends on configuration. It may happen automatically, it may be done manually, it might start automatically but wait for manual approvals etc. You might, for example, use CI for the DEV branch but avoid automated deployments every time, because your internal test environment would become unavailable very often. You might prefer running a deployment on schedule (e.g. during the night), not after every build.

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

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

#1
Martin Dráb Profile Picture

Martin Dráb 515 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 417 Super User 2026 Season 2

#3
CU10121822-0 Profile Picture

CU10121822-0 360

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP
License usage reporting (in-app and PPAC) with Entra dynamic groups

Product updates

Dynamics 365 release plans