How to use a recurring Integration Endpoint for importing data
You are here
Create LCS Hosted Build VM
Create LCS Hosted Build VM
Let's walk through creating a standard Build VM
EDIT: Please see this article
Before we can get started, we must have the following complete:
Create a generic servicing account for environment creation like DynamicsServicing@Contoso.comAdd the generic servicing account to Azure DevOps (AZDO)Generate a personal access tocket for the generic servicing account in AZDO (and securely record it)Setup the connection to Visual Studio Team Services (aka Azure DevOps) in your LCS project. (Hamburger > Project Settings > Visual Studio Team Services and follow the wizard)
Once we have completed those tasks, from your LCS project homepage, you should see 3 environment slots; Production, Sandbox: Standard Acceptance Test and Sandbox: Develop and Test. Click Configure on Sandbox: Develop and Test.
Select the version you want. Should use defaults here. click next.
Select "Finance and Operations - Build and Test".
In the General section, give the environment a name. This will be used in the address for the environment. Something like AAX-BUILD or similar will work.
In the Visual Studio Team Services Section, give it a build agent name and the branch that you want this to place the artifacts required to execute a build. The DNS name selected earlier can be used for the Build Agent Name. Once complete, these will need to be merged to all other branches. Highlighting added to image to call out section.
In the Visual Studio Customization section, select the Visual Studio version. Chances are high Pro is just fine. Highlighting added to image to call out section.
In the Supported Version section, take the defaults. Highlighting added to image to call out section.
In the Customize SQL Database configuration, set the AX database (Build BM) to none. We don't want any data in this environment in the beginning. We can restore a GOLD database later for automated testing if we would like. Highlighting added to image to call out section.
In the Dynamics 365 for Finance and Operations section, take the defaults. Highlighting added to image to call out section.
In the Environment Notifications second, you will need to enter 2 email addresses. Highlighting added to image to call out section.
In the Environment Administrator section, select the generic servicing account you are using to create the environment. Highlighting added to image to call out section.
In the Summary section, review all selections prior to proceeding. Highlighting added to image to call out section.
In the Customer sign off section, Type in the name for the account you are using. This should be a generic service account not tied to a person. Highlighting added to image to call out section.
You will get a confirmation confirming that you would like to proceed.
Click yes and that's it. The environment will be queued for creation.