How to Build a Deployment Package for Dynamics 365 Finance & Operations — Part 1: The Build Pipeline

Welcome to Part 1 of this two-part series on building a deployment package for Dynamics 365 Finance and Operations. Presented by Mahmut Bulbul from Veriland Consulting, this hands-on walkthrough covers every task required to set up a continuous integration build pipeline for your F&O codebase in Azure DevOps. By the end of this tutorial, you will have a working build pipeline that produces a reproducible deployable package—the exact .zip file you will take into your release pipeline in Part 2 to deploy to a UDE or PPAC environment. What is Covered in this Tutorial: Source Control Setup: A side-by-side comparison of Team Foundation Version Control (TFVC) and Git. Pipeline Configuration: Bypassing the YAML wizard to create a new pipeline using the classic editor. F&O-Specific Build Tasks: Executing the custom NuGet restore command , stamping the model version with the build number for full traceability , and compiling the X++ solution via MSBuild. Artifact Generation: Capturing xppc, labelc, and reportsc compile logs , bundling the deployable package , and publishing the build artifact. Automation Triggers: Centralising NuGet package variables and configuring the continuous integration trigger with batching enabled to prevent agent exhaustion. Scaling beyond a single developer packaging code locally requires a reproducible, predictable process. This pipeline provides a comprehensive audit trail and resolves the merge problems inherent in local builds, acting as the foundation for your release pipeline. #Dynamics365FO #AzureDevOps #BuildPipelines #XppDevelopment #ALM #TFVC #Git #UDE #DeveloperTools