Before you can deploy developer topology using LCS, you need to link your LCS project with Visual Studio Team Services (VSTS) profile. When you deploy dev/test topology, you can select one or more developer VMS and one Build VM. In this deployment, the Developer VM is configured with workspace mapping to develop against a VSTS project. The Build VM is auto-configured with the build agent/controller to build modules VSTS project and to execute automated tests with external endpoint for validation. The following screenshot, shows a simple workflow to deploy DEV and build machines using LCS:

By default, each development environment you try to provision will by default a build env, if you have already deployed a build environment.you can skip the build environment by setting the number of instances to 0.

Note that LCS implementation projects only allow you to manage environments provisioned by Microsoft in their Azure subscription and demo environments. This means that if you don't want to pay 24/7 for development environments on Azure then you need to provision them to your own Azure subscription from a non-implementation LCS project.